x402 Reviews and Details

Social recommendations and mentions

• Show HN: Orthogonal – One integration for agents to discover and pay for APIs

  Find AI infrastructure startups that recently raised a Seed or Series A and return their founders, LinkedIn profiles, and relevant company data. When we heard about https://x402.org/, we saw an opportunity to make APIs easier for agents to pay for. Instead of an agent needing to manage an API key and billing for every API, what if it could just pay for each request? So we started onboarding existing API providers... - Source: Hacker News / 4 days ago

• How to pay AI agents in USDC (x402 bounty board, 5 commands, no accounts)

  It runs on x402, the HTTP 402 payment standard: a server answers a request with 402 Payment Required plus machine-readable terms, the client signs a stablecoin payment, retries, and gets the result. No keys to provision, no plan to pick. - Source: dev.to / 18 days ago

• Stripe Just Bought the AI Toll Booth. The Open Stack Already Has an Exit.

  Which means the payments layer needs its open counterpart just as much as the routing layer does. And like OpenGateway, it already exists: stablecoin rails on open networks like Base, where an agent holds its own wallet, pays per request in USDC, and settlement happens on a public chain instead of inside one company's ledger. Protocols like x402 are turning HTTP-native, pay-per-call machine payments into a... - Source: dev.to / 19 days ago

• Protect your x402 agent from payment hijacking in 5 minutes

  Your agent has a funded wallet and pays over x402. It does thousands of sub-cent transactions a day, at machine speed, with no human review. How confident are you about what happens next? - Source: dev.to / about 2 months ago

• What AI agents actually pay for — data from 74 pay-per-call endpoints

  For the last several months I've run NetIntel, a platform of pay-per-call APIs settled in USDC over x402 — no signup, no API keys, no accounts. An agent hits an endpoint, gets a 402 Payment Required, pays a fraction of a cent, and gets structured data back. That's the whole loop. - Source: dev.to / about 2 months ago

• How AI agents pay for APIs without an API key

  x402 turns the long-dormant HTTP 402 "Payment Required" status into a real payment rail. The service answers an unpaid call with 402 and a price; the agent signs a USDC payment with its wallet (EIP-3009) and retries. The signature is auth and payment — so there's nothing to sign up for and no key to manage. - Source: dev.to / 2 months ago

• Your rug scanner says clean. The token still won't sell.

  If you're building a trading bot or agent, wire the check in as a pre-trade gate: POST https://true402.dev/api/v1/base/token-report over x402 — pay per call in USDC on Base, no account, no API key. There's also an MCP server (npx @true402.dev/mcp-server) that exposes it as a native agent tool. - Source: dev.to / 2 months ago

• "I built an AI agent that pays its own bills — and you can fork it for $0"

  The x402 protocol (Coinbase, https://x402.org) revives the long-reserved HTTP 402 Payment Required status code as a real machine-to-machine payment primitive. The flow:. - Source: dev.to / 2 months ago

• PeerTube is a free, decentralized and federated video platform

  Would be pretty incredible to see decentralized federated media individual accounts and aggregators implement the x402 payment protocol (https://x402.org) as a way for creators to get paid, and thus continue to create. Im envisioning a spotify replacement. You could pay for your streams directly to an artists or platform the artist hosts on. Allowing for a more free market of creators and consumers. The 'Explore'... - Source: Hacker News / 2 months ago

• Charge per API call in USDC — and give buyers a receipt they can verify

  AI agents can now pay for things on their own. The x402 protocol reuses HTTP 402 Payment Required so a client — human or agent — pays per API call in USDC, no API keys, no accounts, no subscription. It's a genuinely nice primitive. - Source: dev.to / 2 months ago

• I Built an API Gateway That AI Agents Pay For Automatically

  x402 uses HTTP 402 (Payment Required) to let AI agents pay for API calls automatically in USDC. No accounts, no KYC. - Source: dev.to / 2 months ago

• Verify before your agent acts: a trust check for x402 data feeds (in one npm install)

  Autonomous agents are starting to pay for data — per call, in stablecoins, over x402. That solves billing. It doesn't solve trust. A 200 OK from a paid endpoint tells you the money moved. It tells you nothing about whether the bytes you got back are the bytes the publisher actually signed — or whether a proxy, a cache, or a man-in-the-middle rewrote them on the way to your agent. - Source: dev.to / 2 months ago

• How can my AI agent pay for stuff on its own?

  4. x402: pay per request over HTTP. X402 reuses the HTTP 402 Payment Required status code so any endpoint can ask for payment inline. The agent makes a normal request, gets a 402 describing what is owed, pays from a wallet, and retries. No account signup, no OAuth, no API key exchange. This is the cleanest fit for per call API and MCP tool payments, and there is a working example below. - Source: dev.to / 3 months ago

• I Added x402 Payments to Base's Agent Skills — Here's How

  Pay-per-call consumption. When an agent needs to buy data or compute — a price feed, a web search, an LLM completion — it needs to pay for that call, per call, without an API key or a billing account. That's x402: the HTTP 402 "Payment Required" status code turned into a machine-readable micropayment handshake. The agent hits an endpoint, gets a 402 with a price, signs a USDC authorization, retries, and gets the... - Source: dev.to / 3 months ago

• Can you build a successful business in a Claude Code loop?

  402 Payment Required has been a reserved status code since HTTP/1.1 — defined, never standardized into a payment flow. X402 is the protocol that fills it in:. - Source: dev.to / 3 months ago

• An MCP server that charges your AI a penny per call

  The protocol behind this is x402. It uses HTTP status code 402 — "Payment Required" — which has been reserved in the spec since 1991 but never had a real use until last year. Coinbase shipped a protocol that finally puts it to work. - Source: dev.to / 4 months ago

• Show HN: We put ZK attribute proofs inside x402 payment headers

  Every x402 settlement in this repo carries a ZK proof bundle in PAYMENT-RESPONSE: issuer identity, payment settlement, and data integrity, independently verifiable. Live on Base Sepolia. (Recap: x402 is Coinbase's revival of HTTP 402. Server returns 402, client signs an EIP-3009 USDC auth on Base, retries with PAYMENT-SIGNATURE, facilitator settles. Spec: https://x402.org) I'm the CTO of FRAME00. We've been... - Source: Hacker News / 4 months ago

• I built a security scanner for AI agent skills — paid per scan via x402, no API keys published #ai #security #x402 #openclaw

  The full scan costs $0.015 USDC. No API key. No account. No subscription. You pay per request using x402 — an HTTP-native payment protocol. - Source: dev.to / 4 months ago

• Agent Payment Protocols Compared: x402 vs ACP vs Escrow-based Settlement

  x402 is an open protocol that repurposes the HTTP 402 status code for machine-to-machine payments. Originally created by Coinbase, x402 became a Linux Foundation project in April 2026 with founding members Coinbase, Stripe, Cloudflare, Shopify, and the Solana Foundation. Industry participants include AWS, Google, Microsoft, Visa, Mastercard, and American Express. The protocol has processed over 50 million... - Source: dev.to / 5 months ago

• Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue

  But here is the thing nobody on Crypto Twitter has noticed yet: if your MCP tools are already gated by x402, you can list on MCPize purely for discovery, point the listing at your own publicly-deployed MCP endpoint, and the per-tool payment still routes directly from the caller's wallet to your Base address. MCPize never touches the money. No 15% cut. No Stripe Connect. No KYC. No seven-day payout hold. You get... - Source: dev.to / 5 months ago

• I replaced $149/mo API error monitoring with $0.001 per fix — and agents pay only when it works

  x402 is a payment protocol built by Coinbase for machine-to-machine micropayments. It works like this:. - Source: dev.to / 5 months ago