Agent Checkouts

One API to start from any URL and buy with any payment method the merchant accepts, under a spending cap you set

Agent Checkouts lets your agent buy from any merchant with a single API. Start a run from any URL, optionally describe what to buy in natural language, and set a spending cap. 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 starting 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. Start a run

   Send any starting URL and the maximum the checkout may spend. Add an optional task when the URL alone does not identify the product, variant, quantity, or other purchase preferences.

2. Follow and steer the agent

   Follow the run for its next required action, and read or stream its messages for the complete conversation. Your app can answer forms, authorize a secure card credential, answer protected fields, or send a text message to steer the agent at any time.

3. Read the result

   The run ends with a receipt, a safe blocked outcome, or a clear failure reason. Cancel at any point before completion.

Get Started

Quickstart

Start a checkout and handle its requests

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

Follow a Run

Observe updates, recover after disconnects, and steer the agent

Handle Buyer Inputs

Render ordinary and protected fields and submit complete answers

Authorize Payments

Answer a payment request with a verified order intent

Reuse Merchant Sessions

Save a signed-in session and reuse it on later checkouts

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

Which payment methods can a checkout use?

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 Authorize Payments.

How does my app follow the checkout?

Follow the run to read its current status and requiredAction. Read or stream /messages when your UI needs the complete conversation, progress, activity, input requests, or result. See Follow a Run for both views and recovery.

Can I pass card details when I create the checkout?

No. When the run asks for payment, create an order intent for the same buyer and amount, then send only its orderIntentId in an input response. Raw card details never belong in the run request or message history. See Authorize Payments.

Does the checkout stop to ask the user questions?

It moves to awaiting_input whenever it needs information or authorization. Form requests list typed fields. Ordinary answers contain values; protected field answers contain collected references. Payment requests take an order intent ID. You can pre-answer many ordinary questions with a buyer profile and task.

Can the user change the request after the run starts?

Yes. Send a text part to /messages at any time before the run finishes. Use it to change preferences, answer a conversational question, or redirect the agent without starting over.

Can the agent buy inside the user's account at a merchant?

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.

Can I call the API from the browser?

Yes. Every endpoint accepts a server-side key, or a client-side key plus the signed-in user’s JWT from your auth provider. See Follow a Run for both authentication methods.