Skip to main content
Agent Checkouts lets your agent shop on any website for your user. It can search for products, build and manage a cart, find the total with shipping and tax, manage a subscription, and check out when your user wants to buy. You send a link, the task, and the maximum amount to spend. Crossmint picks the best way to buy at each merchant: an agentic commerce protocol such as UCP, the merchant’s API, or a browser that Crossmint runs. For the problem this solves, read How Agents Buy. When the merchant needs something from your user, such as a size, an address, or the payment approval, the checkout stops and asks your app. Your app shows the question and sends the answer. At the end, you get the result, such as the receipt or the items in the cart. Your user is the buyer, and the merchant is the seller and merchant of record: it sends the receipt and handles returns. To pay, the checkout uses any method that the merchant accepts: an order intent on a card that the user saved in your app, a card saved in the user’s merchant account, Shop Pay, and more. Agent Checkouts works on its own, so you do not need Agent Cards. Agent Cards is the way to pay with a card that the user saved in your app.
Test Agent Checkouts on real merchants from the first call. The first 1,000 checkouts each month are free, and you can test it without buying anything. See Test Agent Checkouts.

​
What You Can Do

Buy a product

From a product link, with the user’s approval at the payment step

Buy several items

One cart and one payment for a list of products

Manage a store cart

Add, remove, and list items, and check out later

Check a price

Get the exact total with shipping and tax, without buying

Buy when the price drops

Check on a schedule, and buy under the user’s limit

Manage subscriptions

Subscribe, change a plan, or cancel in the user’s account

​
Key Features

Any merchant

Any website where a person can buy online, with no list of merchants to set up

Any payment method

Your users’ saved cards, cards saved at the merchant, Klarna, Shop Pay, Pix, and more

Right path per merchant

The merchant’s agentic commerce protocol or API when it has one, a browser on every other website

Hard spending cap

No purchase goes above the cap you set

Live browser view

Embed the session so your user watches the purchase happen

Ask only when needed

Give the user’s details up front, and the checkout asks only for what is missing

​
How It Works

1

Start a checkout

Send a link, the task, and the maximum amount to spend. The task says what to do, for example “Buy one in size M with standard delivery” or “Add this to my cart, and do not pay”.
2

Answer the questions (optional)

When the checkout needs something, such as “Which size?”, it sends a question to your app. Show the question to your user, then send the answer. When you send all the details up front, the checkout does not need to ask. You can also send a message at any time to change the order, for example “Use standard shipping”.
3

Pay

At the payment step, the checkout asks your app to pay, for example “Approve a payment of 42.50 USD”. Send the ID of an order intent that your user approved, or pay with another method, such as Shop Pay. See Pay for a Checkout.
4

Read the result

The checkout ends with a receipt, a safe stop with a code that says why, or a failure reason. You can cancel it at any time before it ends.
See How Agent Checkouts Works for the parts and the statuses.

​
Get Started

Quickstart

Test a merchant with OCA, call the API, or add it to your app with one prompt

Try the live demo

Explore the full checkout experience in the sample app

View the sample app

See how the API and UI components fit together

​
Guides

Configure a Checkout

Set the task, buyer details, browser country, and merchant guidance

Answer Questions

Show the checkout’s questions and send the answers

Pay for a Checkout

Pay with an order intent, Klarna, Shop Pay, or another method

Sign In to Stores

Keep the user signed in at a merchant

Stream Updates

Stream the conversation and recover after disconnects

Test Agent Checkouts

Test it on real merchants at low cost

​
API Reference

Agent Checkouts

Create, read, respond to, and cancel checkouts

Buyer Profiles

Reusable name, contact, and shipping details

Browser Profiles

Saved merchant logins for later checkouts

​
FAQs

Any merchant website where a person can buy online. There is no list of supported merchants, and you do not set up merchants. Some merchants block automated browsers. Then the checkout ends as blocked, with a code that says why. See Common Questions.
Any method the merchant accepts: an order intent on your user’s saved card, an agent card from another provider such as Ramp or Link, a card already saved in the user’s account at the merchant, Klarna, Shop Pay, or a local method such as bank transfer, Bizum, or Pix. See Pay for a Checkout.
No. When the checkout asks for a card payment, create an order intent for the same user and amount, then send only its orderIntentId. Card details never belong in the request or in the messages. See Pay for a Checkout.
No. A page that starts the checkout and shows its questions is enough. When you have an agent, it can start checkouts as a tool and pass the questions to the user in its own conversation.
The Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP) are protocols. Your agent can buy with a protocol only at the merchants that implement it, and adoption is early. Agent Checkouts is an API that buys at any merchant:
  • It uses the protocols. When a merchant supports UCP, ACP, or WebMCP, or has an API, the checkout uses it. At every other merchant, it uses a browser session that Crossmint runs and tunes for checkouts. You integrate once.
  • No merchant setup. With ACP, each merchant must allow your agent before your agent can buy. Agent Checkouts needs no setup at the merchant.
  • Any payment method that the merchant accepts. Not only cards: Klarna, Shop Pay, a card saved in the user’s merchant account, bank transfers, and local methods such as Bizum and Pix.
  • The user’s merchant account. The checkout can sign in to the user’s account at the merchant and keep the session for later checkouts. See Sign In to Stores.
  • More than a purchase. The checkout can also manage a cart, check a price, or manage a subscription.
For more, read How Agents Buy.
With a vault and a browser proxy, you run the browser and the agent, and you maintain the proxy and a list of merchant hostnames. The proxy does not work at merchants that protect card details end to end, for example by encrypting the card in the browser. With Agent Checkouts, Crossmint runs the checkout and enters the card in the merchant’s own payment form, and every purchase stays within an order intent that the user approved. See Common Questions.
Each project gets 1,000 checkouts free each month. After that, each checkout costs 0.05 USD. See Common Questions.
Yes. Every endpoint accepts a server key, or a client key with the signed-in user’s JWT from your auth provider. See Stream Updates.