x402 · HTTP 402 · before an agent pays

Is this x402 API legit? Checks before an agent pays.

An x402 offer tells an agent exactly what it is about to pay: the amount, the asset, the network, the address that receives the money and the resource the payment unlocks. It does not tell the agent who the seller is or whether the seller will deliver. Read the offer first with the free x402 endpoint checker, which only sends GET requests and pays nothing. Then compare the receiving address with something the seller publishes on its own domain.

Read before signing

What the offer tells you

A server that wants payment answers 402 Payment Required. In x402 version 2 the offer is base64 JSON in the PAYMENT-REQUIRED header. Each entry in its accepts list carries:

Scroll the table horizontally to see all fields.

Fields in an x402 offer
FieldWhat it tells you
schemeHow the payment works. exact means one transfer of exactly the amount.
networkThe chain, as a CAIP-2 identifier. eip155:8453 is Base mainnet.
assetThe token contract. On Base, USDC is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Compare it character for character: a look-alike token is a known trick.
amountThe price in the token's smallest unit. USDC has six decimal places, so 1,000,000 is one USDC.
payToThe address that receives the money.
maxTimeoutSecondsHow long the seller allows for the payment to complete.

Outside that list, the offer names the resource being paid for: its URL, with a description and a media type written by the seller. Before signing, check that the amount is what you expected and that the resource is the URL you asked for.

The gap

What the offer does not tell you

  • Who operates the site or the address.
  • Whether the seller will deliver what the description says.
  • Complaints or reviews, and whether the seller is on a sanctions list.
  • The history of the receiving address on the chain.
  • Whether the price is fair.

None of PageVerified's checks establish these either. They report what public endpoints return, and say so.

In this order

Checks before an agent pays

  1. Read the offer without paying. The x402 endpoint checker decodes the offer and shows the network, the asset, the amount in tokens (and in dollars for recognized USD stablecoins), and the payTo address. It also reads a Machine Payments Protocol challenge if the server sends one.
  2. Check the format. A malformed offer is flagged with the problems found. A seller that cannot get the format right is a reason to stop.
  3. Compare payTo out of band. Find the address on a page of the seller's own domain or in its documentation. If you cannot find it anywhere the seller controls, treat that as a missing fact.
  4. Set limits before you sign. Decide the highest amount, the asset and the network you accept, and refuse anything else. prepay_check (5 credits) compares every offer with those expectations for you.
  5. Look at the domain. Its age, whether HTTPS works, and whether it publishes terms and a refund policy are weak signals, but cheap ones.
  6. Start small. Pay for one call before you buy a large bundle.

Sellers that quote only on POST

The free checker sends GET and nothing else. Some sellers answer a GET with instructions and send the offer only in answer to a POST. When the site's own /openapi.json declares a paid POST at that path, the result says the offer is declared instead of failing. The x402_inspect tool can then send one empty POST to read that offer. It still pays nothing.

The same checks as tools for agents

Scroll the table horizontally to see all fields.

Pre-payment tools an agent can call
ToolWhat it does
x402_inspect (1 credit)Reads the x402 offer behind a URL. It sends one empty POST only when a GET already returned a payment challenge or the site's /openapi.json declares a paid POST there. Nothing is paid.
mpp_inspect (1 credit)Reads a Machine Payments Protocol challenge the same way.
seller_check (3 credits)Signals about the seller's domain: age, HTTPS, DNS and email authentication, whether a payTo address is well formed, and whether terms and a refund policy are published.
prepay_check (5 credits)Compares each offer with what you expected (payTo, highest amount, asset, network) and reports changes in the recipient and price since earlier checks. No payment is sent.

Each tool costs the credits shown. A free key holds 25 credits and needs no email or card: POST /api/v1/keys. Every result is a set of observations at the time of the call, not a verdict on the seller.

Common questions

Does the free check pay or sign anything?

No. It sends one GET to the URL and reads the answer. If the URL does not answer 402, it may also read the site's own /openapi.json with a GET. No payment is made or signed, and no wallet is involved.

Can a well-formed offer still be a scam?

Yes. A correct offer only shows that the seller can write the format. It does not show who the seller is or that the resource will be delivered.

Why compare the payTo address out of band?

Anyone who controls the response can put any address in it. An address that matches one the seller publishes on its own domain, or in its own documentation, is harder to fake.

What if the URL answers 200 instead of 402?

Then there is no offer to read at that URL with a GET. Some sellers quote only in answer to a POST. The check says so when the site's own OpenAPI description declares a paid POST there.

Next steps

  • Free checks: test an MCP server, read an x402 payment offer or score a domain's agent readiness. No key needed.
  • Evidence Capture: capture one public page as a screenshot and its HTML, with the SHA-256 of each file and a signed record, for US$9 once by card. No account and no API key.
  • Pricing: credit packs and what every tool costs.
  • Documentation: quickstart, MCP setup and every tool's reference page.
  • x402 endpoint checker: reads the offer an HTTP 402 endpoint returns. Nothing is paid.

Related answers: Is an MCP server safe to connect? · Agent-ready website checklist. Guides: x402 screenshot API.