AI agents now pay for their own tools: Apify puts 20,000+ on x402

What Apify actually shipped on June 30

On June 30, 2026, Apify — the marketplace where developers publish "Actors," ready-made scraping and automation tools — announced it had expanded x402 support from roughly 2,000 tools to more than 20,000 Actors. Every one of them can now be called and paid by an autonomous AI agent over the open x402 standard: the agent hits the tool, receives an HTTP 402 Payment Required with a price, pays in USDC on Base, and gets the result. No account, no API key, no card on file, no human clicking "approve."

The pricing mechanics are worth noticing, because they show how machine commerce actually behaves. Apify supports an exact scheme (a fixed prepaid amount with refunds for the unused portion) and an upto scheme for variable-cost jobs, where the agent authorizes a ceiling and gets charged actual usage after execution. And the amounts are tiny by card standards: one dollar buys an agent roughly 380 Instagram profiles, 250 Google Maps locations, or 2,500 X posts. These are transactions no card network could carry profitably — and they're exactly the sizes agents want to spend.

Apify's framing of the goal is the part that should make every API and tool provider sit up: agents should be able to "discover and pay for the tools that they need on their own, without human-in-the-loop approvals." Not "developers integrate our billing." Not "users add a payment method." The buyer is the software itself.

Why this is bigger than one marketplace update

A catalog of payable tools only matters if something can pay for them. That's why the quieter half of the announcement is arguably the bigger one: mcpc, a universal command-line client for the Model Context Protocol (MCP), added native x402 support — making it one of the first MCP clients that can settle a payment automatically when a priced tool asks for one. Pair that with Coinbase's Agentic Wallet CLI, which drops a wallet into any agent runtime that can run shell commands, and the loop is closed: an agent can find a tool, get quoted, pay, and use it — end to end, unattended.

That means both sides of a new market switched on in the same week. Supply: 20,000+ tools with machine-readable prices. Demand: agent clients and wallets that pay those prices without a human. This is the textbook shape of a marketplace reaching critical mass — and the on-chain data says it's already happening. Chainalysis has documented x402 crossing 100 million transactions on Base, and daily activity surged roughly 321% in three months — from about 159,600 transactions in mid-March to 672,800 by June 10, 2026.

Zoom out and the sequence of the past month reads like an industry deciding in unison: Ripple shipped x402 tooling for the XRP Ledger on June 9, Apify 10×'d the paid tool supply on June 30, and Cloudflare opened the waitlist for its own x402 Monetization Gateway on July 1. The standard at the center of all of it is the same one Coinbase introduced to make the dormant HTTP 402 status code do what it was always meant to do: let the web charge per request.

The analysis: distribution is moving to agent-native channels

For twenty years, selling an API meant the same funnel: a developer finds your docs, signs up, verifies an email, adds a card, gets an API key, and integrates. Every step of that funnel assumes a human on the other end. An autonomous agent completing a task at 3 a.m. can't do any of it — it won't fill in a sign-up form, won't pass a card check, and won't wait for a sales call. If your service can't quote a price and take a payment in-band, per request, the agent doesn't negotiate. It routes around you to a tool that can.

That's the real meaning of Apify's move. The 20,000 tools that became x402-payable on June 30 didn't get better overnight — they got buyable by a new class of customer that the rest of the market still can't serve. When agents pick tools by "can I pay for this right now, programmatically," being payable is distribution. The long tail of paid agent tools is being built in months, not years, and the earliest listed services accumulate the usage, the reputation signals, and the revenue.

There's a second-order effect for anyone running an MCP server or public API today: the moment agent clients pay natively, the free tier stops being your only option for anonymous machine traffic. Today most providers face a bad choice — eat the cost of bot traffic or block it. Per-request stablecoin pricing creates the third option: let the machines pay their way.

Where Payzum fits: your API, agent-payable, without re-platforming

Listing on a marketplace is one route into this economy — if your product fits that marketplace's format. But most companies with a valuable API aren't going to repackage it as somebody's platform component. What they need is the ability to sell their own endpoint to agents, over the same open standard, from wherever it already runs.

That's exactly what Payzum does. Payzum is the middleware/proxy that sits in front of your existing API and makes it payable over x402. You configure three things in a dashboard: your existing endpoint, your existing API key or bearer token, and a price per call. Payzum then publishes an x402 URL. When an agent calls it, Payzum returns the 402 Payment Required with your price, settles the payment through an external facilitator (currently Coinbase's), and proxies the paid request to your real endpoint with your key. To be precise: Payzum is the middleware, not the facilitator — settlement runs through an external facilitator today.

The part that matters for your treasury: the USDC on Base lands directly in a wallet you control. Payzum is non-custodial — it never holds, pools, or touches your funds. No protocol to implement, no settlement code to write, no waitlist, no marketplace revenue share. You can be serving paying agents the same day.

How it works, step by step

1. Connect your endpoint. In the Payzum dashboard, point to the API you already run — any host, any cloud — and paste your existing API key or bearer token. Your service doesn't change.
2. Set a price per call. Fractions of a cent or dollars per request — whatever your data or compute is worth to a machine buyer. Payzum publishes a public x402 URL for it.
3. Agents pay in USDC on Base. A calling agent gets the 402, pays via the external facilitator, and the funds settle straight to your wallet — final, no chargebacks, no card network in the middle.
4. Payzum proxies the call. Once paid, the request is forwarded to your real endpoint with your key and the response returned to the agent. Track every event with signed webhooks and the dashboard.

Who should act on this now

• MCP server operators — clients like mcpc can now pay your tools natively. Put a price on the expensive ones and let usage fund itself instead of running a free cost center.
• Data & enrichment APIs — agents doing research buy per query. Sell to anonymous machine callers without issuing or policing API keys.
• Scraping, search & RAG endpoints — the Apify numbers show the demand curve: micro-purchases at $0.001–$0.01 per unit, at volumes no card rail can carry.
• Inference & specialized model endpoints — meter a fine-tuned model by the call in stablecoins instead of building subscription billing for bots that come and go.

Listing on a tool marketplace vs. fronting your own API

These aren't competing bets — both run on the same open x402 standard. The question is where your product lives and who owns the customer relationship:

Common objections

"My API already has customers on API keys. Why add this?"

Keep them — nothing changes for existing integrations. x402 adds a second front door for a buyer your key-based funnel can't onboard: an autonomous agent with a wallet and no patience for sign-up forms. Payzum proxies paid calls to the same endpoint, with your same key, so both audiences coexist on one backend.

"I don't want to hold crypto or run a wallet."

Payzum is non-custodial: funds settle directly to a wallet you control, and you can opt into auto-conversion to a stablecoin (USDC/USDT) so a dollar of revenue stays a dollar. You set an endpoint and a price — you're not becoming a payments operator or a treasury desk.