x402 mentions (35)

• 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 / 10 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 / 11 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 1 month 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 / about 2 months ago

Trendscoded mentions (0)