Skip to main content
Glama

geld machen x402 agent utilities

by dev.fly.geld-machen-x402
OverviewDiscussionsAdmin

Agent Lead Pack: Live x402 Discovery Feed

agent-lead-pack
Read-onlyIdempotent

Return a fresh timestamped list of live x402 endpoints scraped from public catalogs (PayAI, CDP), optionally 402-probed. Use when you need fresh, broad discovery leads of payable agent APIs. Not for a vetted/signed seller list (use phantom-allowlist) or checking one URL (use phantom-seller-scan). Pick this when the question is 'what x402 APIs exist right now?'. Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.025 Base USDC via x402.

Input Schema

NameRequiredDescriptionDefault
queryNoInput for the paid endpoint: optional count n (10-80).

Output Schema

NameRequiredDescriptionDefault
skuYes
noteNo
payToNo
priceNo
methodNo
networkNo
paid_urlYes
how_to_payYes
teaser_urlNo
your_inputNo
free_teaserNoFree sample output of this SKU (truncated); null if unavailable.
ready_requestNoExact paid HTTP request (method, url with your input, optional json_body) to send with an x402 client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / ready_request
      Added value: +{
+  "description": "Exact paid HTTP request (method, url with your input, optional json_body) to send with an x402 client."
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / free_teaser
      Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional input (e.g. url / address / text) to pass to the paid endpoint as ?q= or JSON body."New value: +"Input for the paid endpoint: optional count n (10-80)."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_pay": {
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "paid_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payTo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sku": {
+      "type": "string"
+    },
+    "teaser_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "your_input": {}
+  },
+  "required": [
+    "sku",
+    "paid_url",
+    "how_to_pay"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-structured behavior: a free sample is returned, the full result costs $0.025 Base USDC via x402, and payment steps are surfaced rather than charged here. The one soft spot is 'optionally 402-probed', which never says who controls that option or what probing changes; openWorldHint=false against 'scraped from public catalogs' is arguably in tension but defensible for a fixed catalog set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb+resource, then routing, then the pricing caveat. Every sentence carries routing or cost information, though the 'Pick this when...' sentence partially restates the usage guidance already given two sentences earlier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-shape explanation is not required, and annotations already carry safety. The description supplies the payment model and alternatives, which is what an agent needs to decide to call it; only the 402-probe behavior and the count-vs-sample interaction remain underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter's schema text ('optional count n (10-80)') already documents the range. The description adds nothing about the query format, and the relationship between the 'query' count and the free-sample/paid-full split is left ambiguous. Baseline 3 for a fully-covered single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return a fresh timestamped list of live x402 endpoints scraped from public catalogs (PayAI, CDP)'), including the data source and an optional 402-probe step. It explicitly separates itself from phantom-allowlist (vetted/signed sellers) and phantom-seller-scan (single URL), so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('fresh, broad discovery leads of payable agent APIs'), explicit when-not ('not for a vetted/signed seller list', 'not for checking one URL'), and names the two alternative siblings for those cases. It even supplies a framing question ('what x402 APIs exist right now?') that maps directly to the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All geld machen x402 agent utilities toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources