Skip to main content
Once an agent has a secure card, a second problem appears: it still cannot buy much. Almost every merchant built its checkout for a human with a mouse.

​
Problems

An agent holding an Agent Card has spending power, but no place to use it programmatically:
  • Most merchants have no purchase API. There is nothing to call. The only path to a purchase is the same web checkout a human uses.
  • Checkouts are built to keep bots out. CAPTCHAs, bot detection, and multi-factor prompts are aimed precisely at automated buyers.
  • Every merchant is different. Carts, guest checkout, account login, shipping forms, coupon fields, and payment pages all vary. A hand-rolled integration works for one store and breaks on the next.
  • Browser automation is slow and expensive even when it works. A general-purpose browser agent has to look at every page, decide what to click, and recover from every surprise. One checkout can take minutes and cost several dollars in tokens.
  • Generic automation is not a checkout solution. A browser agent built for any task treats a purchase like any other web page. A checkout needs things it does not provide: a spending cap enforced outside the model, a way to enter card details without exposing them to the model, a structured way to ask the buyer a question mid-run, and a structured result at the end. It also starts from scratch at each merchant instead of reusing what worked there before.
Three approaches to closing that gap emerged, and each covers only part of the market: To buy anywhere, an agent developer would have to build and maintain all three, choose between them per merchant, and keep up as protocols change. That is the effort most teams cannot afford, and the reason many “shopping agents” stop at a product link.

​
Solutions

​
Agent Checkouts

Agent Checkouts puts all three approaches behind one API. Hand it a product URL, a natural-language request, and a hard spending cap, and Crossmint completes the purchase on your user’s behalf:
  • The right rail for each merchant. Crossmint uses an agentic commerce protocol where the merchant supports one, and runs an optimized browser session as the universal fallback everywhere else. You integrate once and get every rail, including new ones as merchants adopt them.
  • A complete purchase, not a cart. The checkout runs end to end and returns a receipt with the merchant order id, not a link for the user to finish.
  • Any payment method the merchant accepts. A Crossmint Agent Card, an agent card from another provider such as Ramp or Link, a card already on file in the user’s merchant account, Apple Pay, Google Pay, PayPal, or a local method such as Shop Pay, bank transfer, or Bizum.
  • Bounded and observable. The checkout never spends above the cap you set. You can embed the live browser session so the user watches the purchase happen, and the agent asks the user only for what you did not provide up front.
  • Crossmint runs the browser side. The browser infrastructure, the models, the prompts, and the per-merchant behavior live in Crossmint’s service rather than in your integration. Improvements to them apply to every checkout without a change on your side.

​
x402 and MPP

Not every purchase has a checkout page. When the counterparty is an API or another agent, the payment is a protocol exchange settled in stablecoins: Both are paid from an Agent Wallet, with the same scoped, revocable permissions described in How Agents Pay.
One integration covers both kinds of counterparty: Agent Checkouts for merchants, x402 and MPP for machines. The per-merchant work lives in Crossmint’s service, not in your codebase.

​
See Also

How Agents Pay

Scoped cards and wallets the user controls

Agent Checkouts

The product, its features, and where to start

Checkouts Quickstart

Create your first checkout from a product URL