geld machen x402 agent utilities

Payment Receipt Auditor: Is This 402 Settle Real?

payment-receipt-auditor

Read-onlyIdempotent

Verify an x402 PAYMENT-RESPONSE or settle tx hash on Base before retrying a paid call. Use when a paid call failed or looks unsettled and you need proof. Not for pre-launch payload checks (use facilitator-dry-run). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.02 Base USDC via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: settle tx hash 0x… or PAYMENT-RESPONSE JSON.

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: settle tx hash 0x… or PAYMENT-RESPONSE JSON."

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.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the pricing model ($0.02 Base USDC), that the call itself is free with a free sample plus paid URL and pay steps, and the x402 payment path. It stops short of describing error/timeout behavior for an invalid hash, so not a full 5.

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?

Three front-loaded sentences: purpose first, then when/when-not, then cost and return shape. Every sentence carries signal, though the pricing and pay-steps detail is dense and slightly extends length beyond the core selection need.

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?

With an output schema present, return values need no explanation, and the description still adds the payment/cost context an agent needs before invoking. Purpose, trigger, alternative, and cost model are all covered for a single-param verification tool.

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% with a single optional 'query' param, so the schema already documents the accepted input ('settle tx hash 0x… or PAYMENT-RESPONSE JSON'). The description restates this format rather than adding new syntax or constraints, matching the baseline 3 when the schema does the heavy lifting.

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?

The description states a specific verb (Verify) and resource (x402 PAYMENT-RESPONSE or settle tx hash on Base) and explicitly scopes the trigger to retrying a paid call. It also names the sibling it is not for (facilitator-dry-run), so an agent can distinguish it from alternatives without opening schemas.

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?

It gives an explicit when ('a paid call failed or looks unsettled and you need proof') and an explicit when-not with the alternative named ('Not for pre-launch payload checks (use facilitator-dry-run)'). Nothing is left 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?