checkout-registry v0.1
registry/Zinc API
Zinc

Zinc API

Buy-side checkout infrastructure from Zinc. Each capability below is sourced from Zinc’s own docs (or marked not documented) and carries a status. Everything is claimed until independently verified — see the methodology for how a row becomes verified.

status claimed last reviewed 2026-07-02 website www.zinc.com docs www.zinc.com/docs

Capabilities

12 dimensions · sourced from docs
DimensionValue · source · evidenceStatus
coverage 10+ named retailers (Amazon, Walmart, Target, Best Buy, Home Depot, Lowe's, Costco, eBay, Wayfair, Macy's) + more“GET /search returns a single ranked list of buyable products across every supported retailer — Amazon, Walmart, Target, Best Buy, Home Depot, Lowe's, Costco, eBay, Wayfair, Macy's, and more — in one call.”source: www.zinc.com/docs/v2/api-reference/search/cross-retailer.mdevidence: none yet — not independently verified claimed
execution Managed async service — Zinc places the order with the retailer; queued + processed“Create a new order for processing. Orders are queued and processed asynchronously.”source: www.zinc.com/docs/v2/api-reference/orders/create-order.mdevidence: none yet — not independently verified claimed
payment 3 modes — prepaid Wallet (default), Stripe Connect (charge end-customer), MPP (per-request); Zinc fronts & reimburses“Pre-fund a balance and let Zinc draw each order's cost and fee from it.”source: www.zinc.com/docs/v2/wallet.mdevidence: none yet — not independently verified claimed
auth Bearer token (API key); MPP path needs none“Authentication is performed using Bearer token authentication.”source: www.zinc.com/docs/v2/api-reference/introduction/authentication.mdevidence: none yet — not independently verified claimed
access Self-serve — test keys (zn_test_ prefix); dashboard at app.zinc.com“Use an API key with the zn_test_ prefix”source: www.zinc.com/docs/v2/api-reference/introduction/sandbox.mdevidence: none yet — not independently verified claimed
protocols REST + MPP (Machine Payments Protocol, HTTP 402, by Tempo/Stripe); no MCP/ACP/AP2/UCP“Zinc supports MPP on the /agent/orders endpoint, allowing AI agents to place orders and pay in a single request flow — no Zinc account or API key required.”source: www.zinc.com/docs/v2/mpp.mdevidence: none yet — not independently verified claimed
discovery Direct retailer URL — "the URL is the contract"; no SKU/ASIN field“There is no opaque sku id and no separate ASIN / item-id field — the URL is the contract.”source: www.zinc.com/docs/v2/api-reference/orders/create-order.mdevidence: none yet — not independently verified claimed
returns Yes — POST create-return against a prior order; async, return labels provided“Submit a return request for a previously placed order.”source: www.zinc.com/docs/v2/api-reference/returns/create-return.mdevidence: none yet — not independently verified claimed
regions International supported; ISO 3166-1 alpha-2 destination, defaults US“International shipping is supported. Provide the destination country as an ISO 3166-1 alpha-2 code.”source: www.zinc.com/docs/v2/api-reference/orders/create-order.mdevidence: none yet — not independently verified claimed
pricing Flat $1 API fee/order + funding fees (card 2.9%+$0.30; ACH 0.8% cap $5; wire $15); no subscription/markup“each order draws its cost plus a flat $1 API fee from that balance”source: www.zinc.com/docs/v2/wallet.mdevidence: none yet — not independently verified claimed
sandbox Yes — test mode via zn_test_ key prefix; isolated sandbox DB; same host“Test mode uses a separate sandbox database. Orders created in test mode are completely isolated from production data.”source: www.zinc.com/docs/v2/api-reference/introduction/sandbox.mdevidence: none yet — not independently verified claimed
status v2 in active development (not GA); v1 in production; some endpoints beta“Zinc 2.0 is in active development. We're rebuilding from the ground up with AI to support dramatically more retailers and flexibility.”source: www.zinc.com/docs/what-is-zinc.mdevidence: none yet — not independently verified claimed

Status per capability: claimed (from the vendor’s docs) · verified (we ran it) · failed (we ran it; it did not do the claim) · unverifiable (no way for us to test). How we test: methodology.