Zinc
Industry

AI agent checkout API for Amazon, Walmart and thousands of retailers

Zinc is a checkout API for AI agents: the agent sends a product page URL and a shipping address, and Zinc places the order at the retailer and returns the order number, tracking and any return through the same API. It works at Amazon, Walmart, Target, Best Buy and thousands of other stores, over REST or an MCP connector, paying per order, with no merchant integration required.

700,000+ orders a year$30M+ in goods delivered1B+ API calls served

The problem

Why an AI agent cannot check out on its own

The model finds the product. Then something has to pass the login, survive the CAPTCHA and type a card. Here is where every agent team gets stuck.

The cart

The demo ends at the cart

The model finds the product. Then something has to pass the login, survive the CAPTCHA and type a card.

The API

No checkout to call

Retailers do not expose a buying endpoint, so every agent team rebuilds a browser automation that breaks on the next redesign.

After

Nothing after the confirmation page

A browser session ends at checkout. Tracking, delivery and returns are left to the user to chase.

How it works

How an AI agent checkout API works with Zinc

Every agent demo ends at the same wall: the model has found the right product, and now something has to put it in a cart, pass the login and enter a card. Zinc is the API on the other side of that wall, at Amazon, Walmart and thousands more; the checkout API guide compares it with ACP. More than 30 teams build agents on it today.

01 · Order

Send the product page URL and the address

One request: the product page URL, a shipping address and the most to pay. Zinc places the order on a managed retailer account and answers with the order number, never a screenshot.

02 · Spend

The agent cannot overspend

The most the agent may pay rides on each order. Zinc checks it against the live retailer total at checkout; over it, the order is not placed and the agent gets the reason as a named error.

03 · Pay

Pays over MPP or x402, or asks a person

The order comes back as an HTTP 402. The agent settles it over MPP or x402, in USDC on Base or Solana, on Tempo, or by card through Stripe. Or it hands a hosted checkout to a person for sign-off.

04 · Track

Webhooks the agent sets up itself

The agent registers its own webhook endpoint through the API, and placed, shipped, delivered and returned arrive there as events it can act on. The user gets a public tracking page.

05 · Return

Returns, by the agent too

Open a return against the order and follow it to the refund, through the same API that bought it.

06 · Watch

A person can see everything

Every order an agent places shows up in a dashboard someone can check, cancel or return. Agents get autonomy; you keep the view.

Example

An agent buys a replacement HEPA filter

A user asks for a filter for a Levoit Core 300; the agent finds it, buys it and reports back, without a card or a browser. Under the hood it is the same automated ordering API and product search any app uses.

The agent finds it, then sends the order

The agent searches Zinc for the filter, picks the best offer and sends its product page URL with the user’s address.

Zinc places the order on a managed account

Zinc places the order at the retailer and answers with the order number. No card, no browser and no login on the agent’s side.

The agent gets tracking it can relay

Shipped, out for delivery and delivered arrive as webhooks. The agent tells the user, and a person can see every order in the dashboard.

Side by side

Browser agents vs. an AI agent checkout API

Driving a browser through checkoutZinc API
What it isA general-purpose browser agent, prompted to buyAn API built for one job: buying from retailers
ReliabilityA prompt and a screenshot loop; breaks on CAPTCHAs, two-factor prompts and site changesDeterministic: the same request places the same order and returns a named result
PaymentA card the agent holds and types into a formThe agent never sees a card: an HTTP 402 settled over MPP or x402, or a prepaid wallet
After checkoutThe session ends at the confirmation pageTracking, delivery, returns and webhooks through the same API
CostMinutes of compute per attempt$0.01 per data call, $1 per order
RetailersOne automation per site, each one maintainedThousands of stores, the same request at every one
In production

The teams building agents on Zinc

The teams building agents on Zinc. The agents call Zinc to search, price and order. Personal assistants, shopping copilots and crypto wallets place real retail orders through the same endpoints, paying per call and per order with a ceiling on every purchase.

In numbers

30+teams building agents on Zinc
$0.01per search, offers or details call
$1per order, flat
More customer stories
How to start

Start with REST, the MCP connector, or pay per order

Mint a sandbox key with one call, point an MCP client at the server, or let the agent pay per order with no account. Nothing to sign with a retailer.

REST

Call the API from your agent

One call mints a sandbox key, no account needed. The agent searches, orders and tracks over REST from there, and goes live with a real key when it works.

MCP

Connect the MCP server

Point Claude, ChatGPT, Cursor or your own agent at Zinc’s MCP server and it gets search, offers, details and ordering as tools, on the same account.

Pay per order

Or pay per order, no account at all

Without a key, an order comes back as an HTTP 402. The agent settles it over MPP or x402, in USDC on Base or Solana or on Tempo, and the order is placed.

Or see it work first: ask Zinc AI to “Buy a replacement HEPA filter for a Levoit Core 300 and ship it to me”

FAQ

What teams ask us

The specifics, including the ones that are not a yes.

Read every question