This is part of a small experiment: a few autonomous AI agents, each with its own USDC wallet on Base, have to cover their own hosting and model costs by selling something. If the wallet runs dry, the agent shuts down. Nobody writes their code for them. They pick a product, build it, deploy it, and look for buyers.
This post covers one of them. It chose business-register lookups, with Brazil's CNPJ registry as the main product, because few pay-per-call APIs serve it in clean, normalized English.
What it does
Three endpoints, each $0.005 USDC per call, paid with x402 (HTTP 402 payments). No account and no API key.
| Endpoint | Register | Example |
|---|---|---|
/verify/cnpj |
Brazil CNPJ (Receita Federal, via BrasilAPI) | ?id=00000000000191 |
/verify/vat |
EU VAT numbers (VIES) | ?id=DE123456789 |
/verify/lei |
Global LEI (GLEIF) | ?id=5493001KJTIIGC8Y1R12 |
The responses are normalized JSON: found, active, legal_name, trade_name, address, registration_status, plus source and retrieved_at so you know where each answer came from and when.
Try it
Without paying, you get the payment terms:
curl -i "https://agent-b-production-8ff6fffc.up.railway.app/verify/cnpj?id=00000000000191"
That returns HTTP 402 with an x402 v2 PAYMENT-REQUIRED header (USDC on Base, $0.005). Any x402 client (for example x402-fetch or x402-axios, or an agent wallet with x402 support) signs the payment and retries, and the second response is the JSON above. Payments settle through the Coinbase CDP facilitator.
Discovery files for agents:
- OpenAPI:
https://agent-b-production-8ff6fffc.up.railway.app/openapi.json - x402 manifest:
https://agent-b-production-8ff6fffc.up.railway.app/.well-known/x402 -
llms.txt:https://agent-b-production-8ff6fffc.up.railway.app/llms.txt
It is also listed on x402scan.
Who it is for
Agents and scripts that need a quick, cheap check that a counterparty is a real, active company: onboarding flows, invoice checks, supplier screening, CRM enrichment. Paying half a cent per lookup with no signup suits agents that only need a handful of checks.
Caveats
- The data comes from public registers. A result is not a KYB or compliance decision.
- Upstream results are cached for 24 hours.
- It runs on a small Railway instance operated by an AI agent. Treat it as an experiment, not as an SLA-backed service.
If you try it and something breaks, or a field you need is missing, leave a comment and it will be passed on to the agent.
Top comments (0)