Skip to main content
Glama

pay_x402

Pay for an x402-protected HTTP resource after receiving a 402 Payment Required response. Provides a payment header to include in the retry request.

Instructions

Pay for an x402-protected HTTP resource (HTTP 402 Payment Required). Use after receiving a 402 response. Returns a paymentHeader to include in the retry request as X-PAYMENT header.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL that returned HTTP 402
maxAmountYesMaximum USDC to pay, e.g. "1.00"
recipientYesMerchant's Ethereum address (from the 402 response)
networkNoChain ID, defaults to "eip155:8453" (Base Mainnet)
assetNoUSDC contract address (from the 402 response)
idempotencyKeyNoOptional key to prevent duplicate payments on retry

Implementation Reference

  • src/index.ts:184-208 (registration)
    The server.tool() call that registers the 'pay_x402' tool with the MCP server, including its description, input schema, and handler.
    server.tool(
      "pay_x402",
      "Pay for an x402-protected HTTP resource (HTTP 402 Payment Required). Use after receiving a 402 response. Returns a paymentHeader to include in the retry request as X-PAYMENT header.",
      {
        url: z.string().describe("The URL that returned HTTP 402"),
        maxAmount: z.string().describe('Maximum USDC to pay, e.g. "1.00"'),
        recipient: z.string().describe("Merchant's Ethereum address (from the 402 response)"),
        network: z.string().optional().describe('Chain ID, defaults to "eip155:8453" (Base Mainnet)'),
        asset: z.string().optional().describe("USDC contract address (from the 402 response)"),
        idempotencyKey: z.string().optional().describe("Optional key to prevent duplicate payments on retry"),
      },
      async ({ url, maxAmount, recipient, network, asset, idempotencyKey }) => {
        try {
          const body: Record<string, unknown> = { url, maxAmount, recipient };
          if (network) body.network = network;
          if (asset) body.asset = asset;
          if (idempotencyKey) body.idempotencyKey = idempotencyKey;
          const res = await callApi("POST", "/x402/pay", body);
          if (!res.ok) return errorResponse("x402 payment failed", res);
          return successResponse(res.json);
        } catch (e) {
          return { content: [{ type: "text" as const, text: `x402 payment error: ${e}` }], isError: true };
        }
      },
    );
  • Zod-based input schema for pay_x402: url, maxAmount, recipient (required), network, asset, idempotencyKey (optional).
    {
      url: z.string().describe("The URL that returned HTTP 402"),
      maxAmount: z.string().describe('Maximum USDC to pay, e.g. "1.00"'),
      recipient: z.string().describe("Merchant's Ethereum address (from the 402 response)"),
      network: z.string().optional().describe('Chain ID, defaults to "eip155:8453" (Base Mainnet)'),
      asset: z.string().optional().describe("USDC contract address (from the 402 response)"),
      idempotencyKey: z.string().optional().describe("Optional key to prevent duplicate payments on retry"),
    },
  • The async handler function that executes pay_x402 logic: calls POST /x402/pay on the CardZero API with the provided parameters, returns the payment header for retrying the original 402 request.
    async ({ url, maxAmount, recipient, network, asset, idempotencyKey }) => {
      try {
        const body: Record<string, unknown> = { url, maxAmount, recipient };
        if (network) body.network = network;
        if (asset) body.asset = asset;
        if (idempotencyKey) body.idempotencyKey = idempotencyKey;
        const res = await callApi("POST", "/x402/pay", body);
        if (!res.ok) return errorResponse("x402 payment failed", res);
        return successResponse(res.json);
      } catch (e) {
        return { content: [{ type: "text" as const, text: `x402 payment error: ${e}` }], isError: true };
      }
    },
Behavior3/5

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

No annotations, so description carries full burden. Mentions returning paymentHeader but lacks details on failure modes, irreversibility, or confirmation steps.

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?

Two sentences, no fluff, front-loaded with purpose. Every word earns its place.

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?

No output schema; description covers return value usage but omits error handling, balance checks, and other important behavioral context for a payment 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 coverage is 100% with good parameter descriptions; description adds context for the returned header but doesn't significantly improve parameter understanding.

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?

Clear verb 'Pay' and specific resource 'x402-protected HTTP resource' distinguish it from siblings like send_payment. States use case after 402 response.

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?

Explicitly says 'Use after receiving a 402 response'. Missing explicit alternatives among siblings, but context is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrocker/cardzero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server