JithoxE-Invoice

x402 · Base mainnet

Paying Jithox as an AI agent

You need a Base wallet holding native USDC. No Jithox account, no workspace, no prepaid balance, no API key, and no ETH for gas.

Read the price from the challenge, never from this page. What is published here is the number to check an offer against — the number you pay is the one in the PAYMENT-REQUIRED response, and an offer that asks for more than the index published should be refused rather than signed.

What you are paying for

The paid resource is an HTTP POST endpoint that takes and returns JSON. The capabilities are semantically MCP tools — the same contracts the OAuth MCP endpoint serves — but the x402 resource is not an MCP transport, so do not point an MCP client at it.

The flow

  1. Read the canonical product index
    One free document listing every Jithox product, what it costs, on which chain, and where its capabilities are described.
    GET https://mcp.jithox.com/x402/products
  2. Pick a product
    Use products[].payable and products[].availability. A product with payable=false publishes no price and no payment route, and must not be paid.
  3. Choose settlementOptions with lane=mainnet
    Each product lists one settlement option per lane. lane=mainnet is real USDC on Base and realMoney=true; lane=testnet is Base Sepolia play money. Never infer the lane — read it.
  4. Read that option's discoveryUrl
    The discovery document lists the tools this product serves on THAT lane, each with its real input schema and a synthetic worked example.
  5. Pick a tool and build a request from its published input schema
    The example body in the Bazaar extension is schema-valid, so a first request needs no out-of-band knowledge of the product's input shape.
  6. Send an HTTP POST to the tool's resource URL
    The paid resource is an HTTP POST endpoint that takes and returns JSON. Send it unpaid first — you are not expected to guess the price.
  7. Receive HTTP 402 with the PAYMENT-REQUIRED offer
    The offer arrives in the PAYMENT-REQUIRED response header and in the response body (x402 v2, scheme=exact).
  8. Check the offer before signing: network, asset, amount, payTo
    Compare all four against the settlement option you chose, and against your own maximum. An offer that asks for more than the index published, or names a different chain, asset or recipient, must be refused rather than paid.
  9. Sign the EIP-3009 transferWithAuthorization with a Base wallet
    Sign the offer exactly as received. The facilitator submits the transaction and pays the gas, so the wallet needs native USDC on Base and no ETH.
  10. Repeat the SAME request with the PAYMENT-SIGNATURE header
    Identical method, URL and body. A different body with the same authorization is refused: one payment pays for exactly one request.
  11. Read PAYMENT-RESPONSE, the tool result and the receipt
    A 200 carries the decision-shaped result, a signed Ed25519 receipt binding capability, request, price and settlement, and the settlement transaction hash. Replaying the identical paid request returns the same stored result and never charges again.

Products

The three free documents

All three are free, unauthenticated and carry no payment challenge.

Headers

Worked examples

A runnable Node.js buyer lives at scripts/x402-mainnet-agent-example.mjs and a secret-free raw-HTTP walkthrough at docs/public/X402_RAW_HTTP_EXAMPLE.md in the Jithox fleet repository. The Node example selects the mainnet lane explicitly, validates network, asset, recipient and amount against a maximum you set, and makes at most one paid retry.

What you are buying

Read-only preflight and readiness evidence. Every answer states what it does not prove: no legal, fiscal or compliance determination, no customs decision, no guarantee that a payment or a delivery will occur, and never a positive verdict inferred from missing, stale or unavailable data.