Skip to main content
Agent Checkouts lets your agent buy from any merchant with a single API. Hand it a product URL, a natural-language request, and a spending cap, and Crossmint completes the purchase on your user’s behalf and returns the receipt. Behind that API, Crossmint picks the right rail for each merchant: an agentic commerce protocol where the merchant supports one, and an optimized browser session everywhere else. You integrate once and get every merchant. For the problem this solves and how it compares to building it yourself, read How Agents Buy.
Agent Checkouts runs in production only. There is no staging environment, so use a production API key and live auth credentials.

​
Key Features

Any merchant

Any product URL, with or without a purchase API or protocol support

Any payment method

Crossmint Agent Cards, other agent cards, cards on file, Apple Pay, Google Pay, PayPal, Shop Pay, and more

Right rail per merchant

Agentic commerce protocols where supported, an optimized browser everywhere else

Hard spending cap

The checkout never spends above the cap you set

Live browser view

Embed the session so your user watches the purchase happen

Ask only when needed

Prefill identity, shipping, and intent; the agent asks the user only for what is missing

​
How It Works

1

Point the agent at a product

Send a product URL, what to buy in plain language, and the maximum the checkout may spend. Attach a saved buyer profile so the agent already knows who is buying and where to ship.
2

Crossmint completes the checkout

Crossmint picks the rail for that merchant and works through the purchase. If the merchant needs something you did not provide, such as a size or the payment card, the agent raises a question your app answers mid-run.
3

You receive the receipt

The checkout ends with a receipt carrying the total and the merchant order id, or a clear failure reason. Cancel at any point before completion.

​
Get Started

Quickstart

Save a buyer profile, create a checkout, answer each action, and read the receipt

Try the live demo

See the full flow without setting anything up locally

​
Guides

Provide Purchase Context

Prefill identity, shipping, and intent with buyer profiles and the request

Choose a Payment Method

Supported methods, and how to pass a card safely

Improve Merchant Success Rate

Tell the agent what you already know about a merchant’s checkout

Buy from Authenticated Stores

Check out inside the user’s merchant account and reuse the login

​
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 method the merchant accepts: a Crossmint Agent Card, an agent card from another provider such as Ramp or Link, a card already saved in the user’s account at the merchant, Apple Pay, Google Pay, PayPal, or a local method such as Shop Pay, bank transfer, or Bizum. See Choose a Payment Method.
You poll the checkout until it reaches a terminal state, and answer each pending user action along the way. Each action carries a JSON Schema you can render as a form. The quickstart walks through the full lifecycle.
No. Card details are always collected through a user action when the checkout reaches the payment step. Submit only an agent card or a single-use virtual card number, never a real, reusable card number.
By default it raises a user action for every decision the merchant’s checkout involves. You can pre-answer most of them with a buyer profile and request. Card details are the one thing you cannot pre-supply.
Yes. A browser profile keeps the browser state from a login so later checkouts start signed in, with access to saved addresses, payment methods, and member pricing.
Yes. Every endpoint accepts a server-side key, or a client-side key plus the signed-in user’s JWT from your auth provider. The quickstart compares the two.