geld machen x402 agent utilities

Signed Phantom Allowlist: Payable x402 Sellers

phantom-allowlist

Read-onlyIdempotent

Return an HMAC-signed allowlist of x402 sellers with probe evidence (402 seen, probe ok, last paid ok). Use when you want vetted x402 sellers before spending. Not for checking a single URL (use phantom-seller-scan). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.03 Base USDC via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: optional max sellers (1-40).

Output Schema

TableJSON Schema

Name	Required	Description
`sku`	Yes
`note`	No
`payTo`	No
`price`	No
`method`	No
`network`	No
`paid_url`	Yes
`how_to_pay`	Yes
`teaser_url`	No
`your_input`	No
`free_teaser`	No	Free sample output of this SKU (truncated); null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / free_teaser

Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}

Changed1 schema field changedOct 6, 2026

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 max sellers (1-40)."

Changed1 schema field changedOct 6, 2026

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"
+}

First observedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, closed-world), and the description adds substantial context beyond them: HMAC signing, the probe-evidence semantics (402 seen, probe ok, last paid ok), a free sample plus pay steps, and a $0.03 Base USDC x402 cost with no charge on this call. That is rich, non-obvious behavioral disclosure.

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

Conciseness5/5

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

Three tightly packed sentences with zero filler; the identity/evidence statement comes first, then usage routing, then the payment mechanics. Every clause earns its place.

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

Completeness5/5

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

A read-only listing tool with an output schema, so return values need not be re-explained; the description still covers signing, evidence fields, sampling, and pricing. Nothing an agent needs before invoking is missing.

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?

With schema description coverage at 100% and a single optional parameter, the schema already documents the max-sellers range. The description adds no syntax or format detail about the query parameter, so the baseline 3 applies.

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 an HMAC-signed allowlist of x402 sellers') plus the exact evidence fields included. It explicitly distinguishes itself from the sibling phantom-seller-scan, so an agent can route correctly without opening either 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 a positive trigger ('when you want vetted x402 sellers before spending') and an explicit exclusion with the alternative tool ('Not for checking a single URL (use phantom-seller-scan)'). Both the when and the when-not are stated, leaving nothing to inference.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?