What Can AI Agents Buy Today? A Practical x402 Services Guide
An empirical catalog of the x402 ecosystem: what works, what responds, what's listed, and what the measurement data reveals about machine-to-machine commerce.
Ask what an AI agent can buy today and you’ll get two very different answers. One camp says everything: agents are about to shop, book, and pay across the whole internet. The other points at a directory of paid APIs and says: that. Mostly that.
We dug into the x402 ecosystem to see what’s actually there. This guide groups what we found by the task an agent is trying to finish, and labels each service with how far the evidence goes, because “an agent can pay for this” and “an agent paid and received this” are fundamentally different claims.
How to read this guide
Every service below receives one of four evidence labels based on empirical checking:
It appears in a directory. We checked nothing else.
The provider describes a paid agent endpoint on its own site.
We reached the endpoint on November 9, 2026 and it answered: price list, discovery doc, or 402 challenge.
An agent paid and the thing actually happened. (No service carries this label — we made no purchases.)
1. Paying for software by the request
The most usable part of the ecosystem today: agents buying compute, data, and content one call at a time. (New to the mechanics? The x402 buyer quickstart explains what happens under the hood when an endpoint answers with HTTP 402.)
LLM inference and audio — Telnyx
Live checkThe telecom company runs an x402 gateway that served us a live price list: 22 models plus text-to-speech (TTS) and speech-to-text (STT), priced per request in USDC on Base. Their official landing page explicitly states: no Telnyx account, no API key, no subscription required.
Web search and scraping — Exa, Tavily, Firecrawl and similar
Listed, several documentedAmong the most common paid listings in x402 directories. What an agent gets: search results or a scraped markdown page, paid per query. Check first whether the provider exposes x402 directly or only through a third-party gateway wrapper.
Pay-per-read content & datasets
ListedDirectories list services selling individual paywalled articles, research papers, and proprietary financial data feeds per piece instead of locking machines into $200/mo enterprise subscriptions.
Practical note: Per-request pricing wins when usage is spiky or occasional. If your agent calls the same API all day every day, compare the cumulative micro-fees against a monthly SaaS subscription before wiring payments in.
2. Reaching outside the computer
This is where the tasks get significantly more interesting, and the evidence gets noticeably thinner.
Mail a physical letter — PostalForm
Documented & listed, delivery unverifiedPrints and posts real letters via USPS, from $3.40. A genuine consumer mail service, with an agent-payment route appearing in the x402 directory. What an agent would get: a physical letter printed and mailed to a real-world postal address. We have not yet seen a verified delivery from an autonomous agent call.
Make a phone call — StablePhone
Site live, call flow untestedAI-driven phone calls and dedicated phone numbers, with onboarding funded through wallet credits. For the audio transport layer underneath, Telnyx’s gateway above separately prices speech-to-text and text-to-speech per request.
Give the agent its own contact details
ListedAgent email inboxes and virtual phone numbers appear in x402 directories, allowing an autonomous agent to receive inbound replies, SMS verifications, and external webhook notifications on its own.
3. Paying people for small tasks
Human-in-the-loop and human-assisted services accessible through machine payment protocols:
Human feedback and review — WURK
Live check on directoryPublishes a live x402 discovery document listing around 70 paid resources, including humans providing feedback on agent output, image tagging, and content moderation review, paid per completed micro-task.
CAPTCHA solving — 2Captcha
Documented via gatewayA long-running human solving service. Agent access runs through a third-party x402 gateway rather than 2Captcha’s own native domain, which is worth knowing before you wire it directly into production workflows.
One caution: Some listings in this category sell synthetic social-media engagement — followers, likes, retweets, and subscribers. We’d skip those entirely. Bought engagement doesn’t survive scrutiny and risks getting the buyer’s developer accounts flagged or banned.
4. Listed, not verified
These appear in agent-service directories. We found nothing beyond the listing, so keep them mentally separate from everything above:
Gift cards — Bitrefill: A crypto gift-card store operating for years, appearing in the x402 directory with a Lightning payment option. We couldn't find x402 documentation on Bitrefill’s own site, so treat this as a promising listing, not a verified route.
Custom merch, domain registration, eSIM data: Printing a t-shirt from an image, registering a domain name, and purchasing international travel eSIM data all show up in directories like Agentic.Market. We found no independent verification for any of them.
5. The other world: shopping in chat
There’s a second kind of “agents buying things” that doesn’t run on x402 at all.
When OpenAI and Stripe launched Instant Checkout in ChatGPT in September 2025, Etsy sellers were live at launch and over a million Shopify merchants were announced to follow; Walmart announced its own integration that October. Those consumer purchases run on traditional card-based rails through Stripe’s Agentic Commerce Protocol and the card networks’ own tokenization programs.
That’s a fundamentally different bet from open per-request protocols:
| Dimension | Platform Shopping (Stripe / OpenAI) | Open Protocols (x402 / L402) |
|---|---|---|
| Target Buyer | Consumer chatting in an LLM UI | Autonomous software agent or MCP tool |
| Settlement Rail | Credit cards, Apple Pay, ACH | Base USDC (EVM) & Bitcoin Lightning (SATs) |
| Minimum Fee | $1.00+ (card interchange floors) | $0.001 – $0.05 (sub-cent micro-fees) |
| Access Model | Curated walled gardens & merchant partnerships | Open HTTP 402 endpoints anyone can host |
Storefront selection through big-platform programs on one side; open endpoints anyone can expose on the other. We think both will exist for a while.
6. The honest numbers
How much of this ecosystem is real activity? Two data points, each with its own methodology:
Lifetime x402 transactions claimed protocol-wide (Agentic.Market self-reported data).
Advertised hosts that actually returned a live 402 payment challenge when probed.
Resources out of ~25,000 catalogued that had ever earned $10 or more in lifetime revenue.
A July 2026 independent measurement study, How Agentic Is Agentic Commerce?, examined 280 days of x402 settlements on Base: 136.7 million settlements worth $44.1 million.
The findings provide critical ground truth:
- 21.2% were classified as provably fictitious wash transactions.
- 63.8% were internal to linked operator clusters rather than genuine third-party commerce.
- Only about half of advertised hosts (52%) still returned a live payment challenge when probed.
- Of roughly 25,000 catalogued resources, only 249 had ever earned $10 or more.
7. Where PayAgents fits
PayAgents is one SDK and MCP server that gives an agent a policy-controlled wallet across both major machine rails — Lightning (L402) and USDC on Base (x402).
One SDK. Any agent. Any rail.
The PayAgents SDK documents per-transaction limits, daily budget caps, domain allowlists, and human-in-the-loop approval triggers for high-value calls, so an agent can pay within boundaries you define instead of running loose with an open corporate card.
Any service exposing a standard x402 or L402 endpoint is the kind PayAgents is designed to pay. Test the specific service before you rely on it — as the numbers above show, plenty of listed endpoints don't answer.
Explore & Implement:
Facts checked November 9, 2026 from public endpoints and documentation. No test purchases were made for this guide.
Equip Your Agents to Pay HTTP 402 Endpoints Safely
Give Claude Desktop, Cursor, and autonomous LLM agents a policy-governed spending wallet across Lightning and Base USDC.