ACP 2026-04-17 adapter in preview — one checkout core now speaks MCP, ACP, UCP and REST.
AI-native commerce infrastructure
The retry-safe checkout engine for AI agents.
One engineered core — catalog, prices, inventory and idempotent checkout — reachable over MCP, ACP, UCP and REST. No commerce backend to build, no signup to try. A retried request never charges twice.
Not a mockup — the demo's own output. complete_checkout_session is called, then called again with the same session.
The demo runs offline with no key and exits 0 only if one order came back. Run it yourself →
See it run — no signup
A real authenticated request, right here.
Press run: your browser issues a read-only sandbox key and reads the live demo catalog from api.ordercore.ai. No account, no credentials — the same API your agent will call.
Want to prove the retry guarantee itself? Ask the same endpoint for {"mode":"write"} and you get your own isolated tenant: create an order with an idempotency_key, send it again, and the same order comes back — a changed payload is refused with 409. Three curl calls, still no account. Worked example →
agent → api.ordercore.ai
# Press "Run" — this makes a REAL call to the live API.POST /bootstrap/sandbox-key # no signup, no key of your ownGET /v1/products # read the live demo catalog
Real response, executed in your browser. Read-only. Rate-limited.
The part most agent-commerce gets wrong
An agent retries. Your checkout must not.
Agents retry on a timeout, a rate limit, or a restarted loop. With naive checkout code, a retry is a second order and a second charge on a real card. OrderCore returns the same order on replay — and 409 conflict if the same key arrives with a different payload.
POST /complete key=abc payload=Awaiting…—
POST /complete key=abc payload=A(retry)waiting…—
POST /complete key=abc payload=Bwaiting…—
One interface
One core. Every agent standard.
The same idempotent checkout core answers MCP, the ACP 2026-04-17 adapter, UCP and plain REST. Write it once — your agent talks to OrderCore however it already speaks. Same request, same guarantee.
MCP · tools/call → checkout.complete
// Any MCP client — Claude, Cursor, your agent loopawait mcp.callTool("checkout.complete", {
session: "cs_7P2",
idempotency_key: "order-abc-001"// retry-safe
});
// → 200 { order: "OC-2026-0001", status: "paid" } (same on replay)
New / Transaction Trace
When an agent says “done,” see exactly what happened.
Inspect one purchase from order creation through status changes and every webhook attempt. Transaction Trace gives support and engineering one tenant-safe timeline without exposing raw webhook payloads.
Answer whether an order exists without searching three systems
See failed, retried and abandoned webhook deliveries
Correlate by order UUID or human-readable order number
Health, UCP discovery, the direct-AI tool manifest at /direct-ai/tooling and an independently-probed conformance report — inspect them yourself, anytime.
Builder cancels through Stripe and access is suspended if renewal remains unpaid. Review and sprint begin only after written scope acceptance and payment.
Unsure whether to buy software, a review or implementation?
Scan your current public surface first. If discovery is missing, the free report shows the first gaps. If the transaction model fits and your team can integrate an API, buy Builder. The USD 499 Agent Commerce Readiness Review is for the authenticated risks a public scan cannot prove.