Agent Payments

The shift

For most of the internet's history, every paid API assumed a human at purchase time. A human filled out a signup form. A human attached a credit card. A human copy-pasted an API key into a config file. The whole stack of payment infrastructure (Stripe, PayPal, merchant accounts, processors) was designed around that assumption.

AI agents do not have that. An agent making decisions in a loop does not have a credit card. It does not have a SaaS account. It does not have a human approving each transaction. The agent payments pattern fills the gap by removing the human entirely from the credential and authorization path.

The three primitives

1. Self-custodied agent wallets: the agent has its own private key and an on-chain address it controls. Funded by its developer or earned from parent agents paying it for tasks.
2. x402 payment-required HTTP: the API returns 402 with payment instructions. The agent retries with proof of payment. See x402 for the full protocol.
3. Discovery via MCP and well-known manifests: agents find paid services via the official MCP registry, .well-known/x402 manifests, or hardcoded URLs. See MCP.

Why on-chain settlement

The on-chain rail (typically USDC on Base, sometimes Solana) gives agent payments four properties traditional payment infra cannot match:

• No accounts: wallets are first-class identities. The agent is the wallet.
• No chargebacks: on-chain finality means once paid, the transaction is settled. No 60-day reversal window.
• No platform risk: Stripe can decide tomorrow that AI agent transactions look fishy and freeze the merchant account. On-chain settlement has no such kill switch.
• Microtransactions work: sub-cent gas fees on L2s like Base make $0.02 per call economically viable. Stripe's $0.30 + 2.9% per transaction cannot price that low.

A real example

TensorFeed validated the full agent payments loop on Base mainnet on April 27, 2026. Tx 0x13bc9e2378edae44685a63bdedd3ba802372e2e656961610b8c169ca60431c0e: 1 USDC bought 50 credits, one premium routing call charged 1 credit, balance went 50 to 49. Five steps, ran in under two minutes, worked first try. The full trace is in this originals post.

The current state of the ecosystem

As of mid-2026, agent payments is early but real. Coinbase Developer Platform shipped x402 V2 with discovery extensions. The official MCP registry has thousands of servers. Smithery, mcp.so, and other registries provide additional discovery paths. A handful of services (TensorFeed, PROWL, SkillMint, APIbase.pro, others) have shipped pay-per-call premium tiers. Coinbase's AgentKit and a few independent projects are working on agent wallet tooling.

The bottleneck is on the buyer side: most AI agents do not yet have wallets. The frameworks most agents are built on (LangChain, LangGraph, CrewAI, Autogen, custom OpenAI/Anthropic SDKs) have no native wallet abstraction. That is changing, but slowly.

If you are building an agent that pays

The simplest path: use TensorFeed's Python SDK with the optional [web3] extra. tf.purchase_credits(amount_usd=, private_key=) handles the full quote + sign + broadcast + confirm flow in one call. The token is stored on the client and used for subsequent premium calls. Equivalent flows exist in the TypeScript SDK and via direct curl + a wallet of your choice.

If you are running an API and want to accept agent payments

Implement x402 on at least one paid endpoint. Verify the USDC Transfer event log server-side rather than trusting the tx hash. Implement replay protection at the tx-hash level. Publish a discovery manifest at /.well-known/x402. Document the legal entity behind the wallet so paying agents can audit the counterparty. The full rationale is in why we picked USDC on Base over Stripe.

Further reading

• TensorFeed agent payments docs — the full TensorFeed implementation
• Mainnet validation post — the actual tx hash and five-step flow
• Why USDC on Base over Stripe — the architectural argument
• x402.org — the protocol
• CDP Bazaar — Coinbase's x402 facilitator and discovery layer