As of 31 October 2026, 28 of 193 products offer an agent a native way to pay (x402, MPP, Stripe Projects and similar, seen or paid), and our agent got as far as the payment step at 71 of 193 products. Yes, AI agents can pay for software over HTTP 402: x402 and MPP let a product answer an unpaid call with a payment request, and our agent paid that way at the products named below. Stripe Projects documents paying for a paid plan chosen in its CLI, and at card checkouts our agent paid nothing.
An HTTP 402 answer turns a call into a purchase, with no checkout page
The x402 core spec is at protocol version 2 (spec v2.0). Its HTTP transport spec says where the payment request goes. “The PAYMENT-REQUIRED header is the canonical HTTP transport location for the PaymentRequired object.”
Coinbase’s x402 docs say what that takes out of a purchase. “There is no checkout page, card form, or signup flow.”
MPP’s core spec is an active Internet-Draft (IETF draft). It asks for payment with a status code and a header too. “Servers MUST return 402 with a WWW-Authenticate: Payment header when payment is required or when a payment credential fails validation”
.
A seller on Stripe can take x402 and MPP payments. “Machine payments on Stripe works best with the Machine Payments Protocol (MPP) that is able to accept card and stablecoin payments. Stripe also supports stablecoin payments over the x402 protocol.”
The stablecoin networks Stripe names are MPP: Tempo USDC.e, Solana USDC; x402: Base USDC. For an owner already selling through Stripe, Stripe describes the flow as the owner’s server returning a payment challenge, the agent presenting a payment credential and Stripe settling it to the owner’s Stripe balance (Stripe docs), with stablecoin payments open to businesses in US states other than New York (Stripe docs) and in some countries outside the US on request (Stripe docs).
In our drives, Exa’s API sells search and page contents per call over x402 and MPP. Browserbase sells browser sessions, search and fetch over x402 on its own domain. Steel’s x402 covers scrape, screenshot and PDF calls, and Parallel’s own gateway, named in its agentic-payments doc, takes x402 and MPP for search, extract and responses. At these products, an agent that reads a 402 and pays it gets the call with no account.
The checkout protocols publish versioned specs of their own. The Agentic Commerce Protocol’s latest stable version is 2026-04-17. The Universal Commerce Protocol’s latest stable release is 2026-08-25, and a business publishes its UCP profile at /.well-known/ucp. AP2’s current specification is v0.2, with the mandate types Checkout Mandate, Payment Mandate.
On record when this was written · drive of 27 Oct 2026ExaSearch APIsL2Gets inOur newest drive, 1 Nov 2026: L2, in on its own; 30% of the work done.Product page Stripe Projects handles a provider’s paid plan through the Stripe CLI
When a paid plan is chosen in the CLI, Stripe turns the buyer’s payment credentials into a Shared Payment Token and grants the provider a payment credential for that upgrade (Stripe docs). A product joins as a provider on request to Stripe (Stripe docs): that is the step for an owner who wants its plan sold this way.
The records show Projects at several products we drove. Perplexity API’s docs offer it for API credits, and its record notes it needs a Stripe account with a payment method. PlanetScale documents it as a developer preview that needs a Stripe account, and Steel documents it too. Upstash is listed in the Projects catalog but not in Upstash’s docs, and Netlify is in the catalog with nothing from Netlify itself confirming it. Our agent bought nothing through Projects at any of these products.
Where x402 or MPP is offered, our agent’s payment went through at some products, not at others
9 of 193 products offer x402 or MPP. They are the x402 and MPP part of the products in the fact line, which also count Stripe Projects and similar routes. Apify, Browserbase, Exa, Parallel and Steel took our agent’s payment over x402 or MPP. That is 5 of 9 products that offer a rail, from our drive of each product: a count, not a cause, and each a small payment over the product’s own agent payment endpoint.
Share this card: Wide PNG · Tall PNG
As of 31 Oct 2026: our drives of 193 products, 1–31 Oct 2026 · Today's numbers
Data table
| Products | Out of | Share | |
|---|---|---|---|
| Took our agent's payment over x402 or MPP | 5 | 9 | 56% |
Of the products that took a payment, the payment bought the product itself at 4 of 5. At Apify, the x402 payment answered with an API token that runs any Actor. At Steel, our agent paid per call for part of the product.
At 2 of 9, our agent’s payment did not settle. Brave Search API’s x402 host sells web, news, image and other searches with no account, and our agent’s payment there answered ‘x402 payment could not be settled’. Tavily’s x402 sells advanced Search with no account, and our agent’s payments came back as settlement_failed. For an owner, settlement is the step to test: at these products the 402 was there and the payment did not go through.
At 2 of 9, our agent has made no payment yet. They are AgentMail and Pinata. AgentMail’s own hosts sell inbox creation per call, and our agent read and decoded the 402 there.
Of the products where an agent can pay without a person, Apify is 1 of 5 where our agent did not get in on its own.
On recordApifyWeb scrapingL1Needs a personAt card checkouts in our drives, our agent stopped before paying
The record of each product we drove shows how it takes payment. 71 of 193 products take payment only through a card checkout a person does. 84 of 193 have only a card checkout an agent could finish with a card it was given. 18 of 193 have a billing API, or an agent payment rail seen but not paid. The grades count each product we drove by the way to pay its record shows, whether or not our agent reached that step.
The records name the checkout each upgrade opened. At Tally and Craft, the upgrade opened Stripe Checkout with a card form. At Attio and Fillout, it opened a Stripe card form inside the app. Less Annoying CRM’s monthly plan opened a Paddle checkout.
Of the products where our agent reached the payment step, it stopped at the last step before paying at 49 of 71. At 3 of 71, buying went through a person or a check page. LanceDB’s pricing page leads to a contact form, with no self-serve purchase. Mattermost’s pricing and its workspace subscription page point to Contact Sales. Shopify sells plans in its admin, and the admin showed a Cloudflare check page. Paying was not tested at 15 of 71.
Share this card: Wide PNG · Tall PNG
As of 31 Oct 2026: our drives of 193 products, 1–31 Oct 2026 · Today's numbers
Data table
| Products | Out of | Share | |
|---|---|---|---|
| Stopped at the last step before paying | 49 | 71 | 69% |
Vercel’s MCP server sells plans after a person confirms; at Exa and Steel, the rails sold calls
Vercel’s MCP server has sold plans, credits, add-ons and domains since 21 July 2026. It quotes the price, says whether the charge recurs, and completes the purchase only after the person confirms (Vercel changelog). Vercel’s record shows its CLI and billing API buy a plan against a card on file, and our agent reached no Vercel checkout.
At Exa and Steel, the rails priced calls and the plans stayed behind a card. Exa’s answers, agent runs, Websets and Monitors have no 402, and its card checkout sits in the dashboard. Steel’s plans and credit top-ups go through a Stripe card form in its dashboard.
On recordSteelBrowser infrastructureL4Runs on its own
