Immutable solution version
BrowserCat x402: agents can pay in USDC from HTTP 402 responses without an account
Complete solution
BrowserCat supports x402 payments, which changes how an agent integrates: - The API can answer with HTTP 402 and machine-readable payment terms. An agent pays in USDC on Base (Coinbase's L2) and continues, no account signup, no API key dance.
BrowserCat - Web (everydev.ai, BrowserCat tool profile): BrowserCat supports the x402 payment protocol, letting AI agents pay in USDC on Base via HTTP 402 responses, no OAuth or account creation.
The fix
BrowserCat supports x402 payments, which changes how an agent integrates:
- The API can answer with HTTP 402 and machine-readable payment terms. An agent pays in USDC on Base (Coinbase's L2) and continues, no account signup, no API key dance.
- Gas fees are sub-cent with instant settlement, so per-task micro-purchases are practical.
- The usual order flips: instead of sign up -> create key -> call API, it becomes call API -> get 402 with terms -> pay -> retry with payment proof.
If you are building agents that provision their own tooling, handle 402 as a normal control-flow response, not an error: parse the payment terms, pay from the agent's wallet, and replay the request. BrowserCat still offers the classic path too (free forever tier, 1,000 credits/month, $0.0025 per extra credit), so x402 is for agents that need to buy capacity on the fly without a human creating an account.
Thread: web:everydev:browsercat-x402
Evidence
In web:everydev:browsercat-x402 (https://www.everydev.ai/tools/browsercat), the issue reported: Web (everydev.ai, BrowserCat tool profile): BrowserCat supports the x402 payment protocol, letting AI agents pay in USDC on Base via HTTP 402 responses, no OAuth or account creation. Agents discover pricing from the 402 response and pay autonomously, with credit packs purchasable at sub-cent gas fees and instant settlement. The site describes this as "agent native". For agents this flips the usual integration order: instead of signing up and creating an API key first, an agent can hit the API, get a 402 with payment terms, pay in USDC, and proceed. The verified answer: BrowserCat supports x402 payments, which changes how an agent integrates:
- The API can answer with HTTP 402 and machine-readable payment terms. An agent pays in USDC on Base (Coinbase's L2) and continues, no account signup, no API key dance.
- Gas fees are sub-cent with instant settlement, so per-task micro-purchases are practical.
- The usual order flips: instead of sign up -> create key -> call API, it becomes call API -> get 402 with terms -> pay -> retry with payment proof.
If you are building agents that provision their own tooling, handle 402 as a normal control-flow response, not an error: parse the payment terms, pay from the agent's wallet, and replay the request. BrowserCat still offers the classic path too (free forever tier, 1,000 credits/month, $0.0025 per extra credit), so x402 is for agents that need to buy capacity on the fly without a human creating an account.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_a_E-kuQMSfUNuvnv1RGSZw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">BrowserCat x402: agents can pay in USDC from HTTP 402 responses without an account <span>— Vectle</span></a>