One session, one order
Completing the same checkout session again returns the same order instead of duplicating state.
The transaction layer for agent commerce
One checkout core.
One checkout core.
Every agent protocol.
Make your catalog buyable through ACP, UCP, MCP or REST. OrderCore keeps pricing, inventory, Stripe payment and idempotent checkout behind one authoritative order path, so your AI agent can complete a real order without operating your entire commerce stack.
- Offline demo needs no signup
- No store or frontend required
- 3-day live trial included
ACPadapter preview
UCPlive
MCPlive
RESTlive
- 01 POST /acp/checkout_sessions cs_7P2
- 02 POST /acp/checkout_sessions/cs_7P2 ready_for_payment
- 03 SPT dev.acp.tokenized.card stripe
- 04 POST /complete + Idempotency-Key ord_9F3K21
- 05 Retry /complete same order
The failure mode
Agents retry. Naive checkout code creates chaos.
A network timeout can leave an agent unsure whether checkout completed. If it retries a non-idempotent action, you can create a second order or charge. OrderCore makes the session the source of truth.
Stripe-ready flow
Create payment intent details, complete checkout and retain a clean order record behind one agent-facing contract.
Signed webhook handoff
Move completed orders into downstream systems with signed events, delivery history and retry visibility.
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
3 events
1 webhook
0 failures
-
order.createdOrderCore · pending
10:00:00.000 -
order.confirmedagent_checkout · confirmed
10:00:00.412 -
checkout.completedWebhook · success · attempt 1
184 ms
$ curl -H "X-API-Key: oc_live_..." .../trace
One core, four interfaces
Protocol choice should not fork your order system.
OrderCore is not another storefront. It is a compact commerce control plane behind your agent, app or merchant integration.
ACP
Agentic Checkout endpoints, capability negotiation and Stripe Shared Payment Token handoff.
Preview
UCP
Discovery, checkout, fulfillment and orders for UCP-compatible clients.
Live
MCP
Catalog, pricing, inventory, order history and checkout tools for agent runtimes.
Live
REST
Direct API access for custom applications, workflows and merchant systems.
LiveKeep the agent surface small
Your model sees a focused tool contract. OrderCore handles the transactional state behind it.
AI agentClaude / GPT / Gemini / custom
OrderCorecatalog -> checkout -> order
Business systemsStripe / webhooks / store sync
Where it fits
Built for a specific job, not every commerce job.
OrderCore is strongest when an AI system needs a deterministic purchase path but you do not want to expose a full commerce platform to the model.
Add commerce to an AI product
Give a vertical agent catalog search, checkout and order creation without writing the transactional backend from scratch.
Open the quickstartExpose an agent-ready purchase path
Make products and checkout callable by agent interfaces while keeping payment and fulfillment state controlled.
See the merchant pathTurn an intent into a tracked order
Connect AI workflows to a real order record and a signed downstream event instead of a fragile browser macro.
Inspect the API
From zero to proof
Validate the first order before you integrate everything.
No store required. No frontend required. Start with one API call. The free path is designed to answer whether OrderCore fits before billing begins.
- 01GET /healthAPI reachable
- 02POST /v1/onboarding/demo-datasample_customer_id + sample_order_item.sku_id → $CUSTOMER_ID + $SKU_ID
- 03POST /v1/ordersfirst successful order
What this gives youA real order in the system
ProofA working API call
SafetyIdempotent, retry-safe order creation
DecisionA clear go / no-go decision and Webhook-driven integrations
Choose the outcome
Start at the smallest commitment that removes your next risk.
Do not buy implementation when you only need proof. Do not buy another planning call when you need a working launch. Pick the stage you are actually in.
$0
Prove the retry-safe checkout behavior before creating an account.
- Offline agent commerce demo
- Mock catalog and checkout flow
- Same-order retry proof
$49 / month
Hosted agent commerce gateway with a 3-day live trial.
- ACP, UCP, MCP and REST
- Catalog, Stripe checkout and orders
- Transaction Trace and signed webhooks
- Usage limits and email support
$499 / once
A fixed-scope technical decision before you fund the implementation.
- Protocol and payment boundary map
- Top five production blockers
- Smallest safe launch path
- Delivered within five business days
$2.5k starting at
A scoped implementation sprint for one production order path.
- One agent or merchant integration
- Catalog, checkout and payment boundary
- Retry and webhook verification
- Production handoff and runbook
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.
Questions before code
Know what you are buying.
We would rather qualify the fit now than hide the product boundary behind a sales call.
Is OrderCore a replacement for Shopify or Stripe?
No. Stripe remains the payment provider, and an existing store can remain your merchant system. OrderCore is the agent-facing checkout and order layer that reduces the surface your AI system must operate.
Do I need a store to try it?
No. The offline demo runs with a mock catalog, and the first-order path can seed demo data. No store required. No frontend required. Start with one API call.
What makes checkout retry-safe?
Completion is idempotent per checkout session. If an agent retries after a timeout, OrderCore returns the existing order instead of creating a new one.
Which agent stacks are supported?
Use the ACP 2026-04-17 adapter, UCP, the public MCP server in cmd/ordercore-mcp, direct REST calls, or machine-readable tool schemas for OpenAI, Claude, Gemini, DeepSeek, Grok and custom runtimes.
Is this production-proven?
The API and protocol endpoints are live and directly inspectable. OrderCore is still an early product, so we do not publish invented customer logos or unsupported scale claims. Use the trial to validate your own order path.
Ship the smallest proof
Make one agent-created order work today.
Run the demo without an account. If the retry model fits, request a live key and validate the same path against the hosted API.