nano-pay

x402_pay

Request a URL and automatically pay its Nano x402 quote. Refuses quotes above max_xno, returns the paid response body and settlement receipt.

Instructions

Request a URL and automatically pay its Nano x402 quote (feeless, sub-second). Refuses quotes above max_xno. Returns the paid response body and the settlement receipt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "x402_pay"
  }
}

Input Schema

Name	Required	Default
`url`	Yes
`method`	No	GET
`max_xno`	No	0.05
`json_body`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds meaningful context: 'feeless, sub-second' (cost/performance), 'Refuses quotes above max_xno' (safety cap), and 'Returns the paid response body and the settlement receipt' (outcome). It does not cover failure modes or prerequisites (e.g., wallet funding), so it is not exhaustive but still transparent.

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?

The description is two sentences, front-loaded with the main purpose, and every sentence contributes meaning. It avoids filler and is highly efficient.

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

Completeness3/5

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

The tool has 4 parameters and an output schema, but the description does not cover prerequisites like wallet funding or error behavior when a quote is unavailable. It does mention the return receipt and spending cap, but given the complexity of a payment operation, more contextual detail is needed for full completeness.

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 0%, so the description must compensate. It explains the 'url' (target to request) and 'max_xno' (spending cap) directly. However, 'method' and 'json_body' are not described, leaving their formats and usage ambiguous. This is partial compensation, making it adequate but not thorough.

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 clearly states the tool's function: it requests a URL and automatically pays its Nano x402 quote. It also specifies key behaviors (feeless, sub-second, refusal above max_xno) and outputs, which distinguishes it from siblings like x402_quote and x402_compare.

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

Usage Guidelines4/5

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

The description provides clear context that this tool is for executing a payment for an x402 quote, as opposed to just retrieving or comparing quotes. However, it does not explicitly state when not to use it or name alternative tools as exclusions, so it falls short of a 5.

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

Deploy Server