Stablecoin Payment APIs for AI Agents: What Developers Should Check
· updated · 4 min read
Looking for a stablecoin payment API for an AI agent? The x402 standard lets an agent pay an API per call in USDC, with no account or API key. Before your agent pays, check that the API will really deliver. This guide covers how these payments work and how to check an API first.
Lumière PayCheck is not a payment API. It does not process, route or hold payments. It is the check you run before your agent pays an x402 API: it looks at the endpoint, its price and its payout wallet, and gives a verdict.
How Stablecoin Payments Work for Agents
With x402, an API that wants payment answers a request with a 402 status code and a quote. The quote lists the price, the network, the token (usually USDC) and the wallet that gets paid, called payTo. Your agent's x402 client signs a payment for exactly that amount and sends it in a header when it calls the API again. The API checks the payment and returns the data.
That makes it a good fit for agents. There's no account to create, no API key to store and no invoice to wait for. An agent with a USDC wallet can pay for data the moment it needs it.
What to Check Before Your Agent Pays
Stablecoin payments can't be charged back. A 402 quote only shows that a seller is asking for money. A payment receipt only shows that money moved. Neither proves you got the data you paid for. So before your agent pays, it helps to know:
- Does the endpoint answer? An API that's often down wastes your agent's time and money.
- Is the price stable? A sudden price increase is worth noticing before you pay it.
- Is the payout wallet the usual one? A payout wallet that changes without warning can be a sign the seller was hijacked.
- Has anyone paid it and gotten real data back? Only a real paid test shows that.
How to Check an Endpoint for Free
Lumière PayCheck monitors more than 138,000 x402 endpoints, including those listed in the x402 Bazaar. It checks whether each quote is valid, whether the price and payout wallet stay stable, and whether the endpoint answers. It also flags lookalike sellers and screens wallets against the OFAC sanctions list.
When your agent has a quote, send its url, amount and payTo to the free check-payment endpoint. It answers allow true or false, with reasons. If allow is false, your agent shouldn't pay.
curl -X POST https://lumierepaycheck.org/v1/check-payment \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com/api", "amount": "10000", "payTo": "0xSellerWallet"}'For a quick grade without a quote, call GET /v1/score?url=<endpoint>. It returns a score from 0 to 100 and a verdict:
- Proceed: a real paid test delivered, and the endpoint is reliable in monitoring.
- Caution: something isn't confirmed yet, often because it hasn't been paid-tested. It doesn't mean "don't pay".
- Avoid: don't pay it.
Using the MCP Server
Agents can run these checks themselves through the free PayCheck MCP server at https://lumierepaycheck.org/mcp, or with the npm package lumiere-paycheck-mcp. Your agent calls check_payment with the quote before it pays. Afterward, it can call report_outcome to say whether it got what it paid for. Those reports help everyone see how each seller treats real buyers.
{
"method": "tools/call",
"params": {
"name": "check_payment",
"arguments": { "url": "https://example.com/api", "amount": "10000", "payTo": "0xSellerWallet" }
}
}Proof That an Endpoint Delivers
PayCheck makes small real test payments to confirm an endpoint delivers what it advertises. An endpoint that passes shows "Paid and delivered". Every paid test comes with a receipt signed with our Ed25519 key, holding the payment terms, a hash of the response, the amount, the result and the time. You can look up an endpoint's receipts at GET /v1/test-receipts?url=<endpoint> and check the signature yourself.
PayCheck also reads real USDC settlements on Base and Solana into each endpoint's payout wallet: its 30-day volume and how many independent buyers it has.
To browse sellers and their grades, see https://lumierepaycheck.org/sellers. For grades in bulk, GET /v1/catalog returns 1,000 endpoints per call, so you don't have to crawl the pages one by one.
What It Costs
The checks above are free, and a free API key at https://lumierepaycheck.org/free-key raises the limits. Some calls are paid per use in USDC with x402: a full report is $0.005, batch scoring is $0.01, and bulk catalog data is $0.10 per 1,000 endpoints. For teams, the Builder plan ($9/month) adds 3 agent keys with spend limits, and the Business plan ($49/month) adds 25 agent keys and human review for anomalies.
FAQ
Is Lumière PayCheck a stablecoin payment API? No. It doesn't process, route or hold payments. Your agent pays the seller directly with x402, and PayCheck is the check it runs first.
What does a caution verdict mean? Something about the endpoint isn't confirmed yet, often that no paid test has run. Only an avoid verdict means your agent shouldn't pay.
How do I see proof that an endpoint was tested? Call GET /v1/test-receipts?url=<endpoint>. Each receipt is signed with our Ed25519 key, so anyone can check it.
Check any x402 endpoint for free before your agent pays it: https://lumierepaycheck.org/
Related reading
More from the blog
How to Add x402 Payment Checks to Your MCP Server
If your AI agent pays x402 APIs through an MCP server, you can add a safety check before every payment with Lumière PayCheck's free MCP tools. The agent…
How AI Agents Pay for APIs with USDC
AI agents pay for APIs with USDC using x402: the API answers with a price, and the agent signs a USDC payment for exactly that amount and sends it with its…
x402 Seller Checklist: Verify Your Endpoint Before Buyers Pay
Before AI agents pay your x402 endpoint, many of them check it first. This checklist covers what they look at and how to get your endpoint to a proceed…