OrderCore Direct AI
Pilot-ready direct AI checkout

API Checkout for AI Agents, Built for Developers.

Start with a 3-day trial, send an order through the API, and leave with proof: production-safe checkout behavior without rebuilding idempotency and webhook delivery internals.

Create your first order View docs
Get API key

Start with your live oc_live_... key.

Create your first order

Run GET /health, seed demo data, and resolve one seeded SKU.

Confirm order → trigger webhook

Call the order endpoint with Idempotency-Key and verify delivery.

Understand the value in seconds

Who this direct AI checkout path is for

Choose this path when you want AI-driven selling with API control. OrderCore handles checkout reliability so your team can focus on product flow, not rebuilding payment-session and delivery guarantees.

Who It's For

  • Developers shipping AI assistants or custom agents into a buyer flow.
  • Products embedding checkout into existing app UX.
  • Merchants validating AI channel demand before connector expansion.

What It Removes

  • Hand-built idempotency and duplicate-order safeguards.
  • Fragile token and session logic for public checkout surfaces.
  • Manual webhook retry and failure-triage code.

What Gets Simpler

  • A clear path from pilot to production, backed by readiness checks.
  • One API path across assistants and custom frontends.
  • Fulfillment handoff via signed webhook delivery flow.

Not Ideal For

  • Teams that need a no-code storefront instead of API checkout.
  • Projects without developer time for the first setup pass.
  • Teams that do not know who owns checkout and webhook ops.
Get API key Start with your live oc_live_... key.
→
Create your first order Run GET /health and POST /v1/onboarding/demo-data to resolve sample IDs.
→
Confirm order → trigger webhook Call POST /v1/orders with an idempotency key and verify delivery.

Operational Proof Surface

Evidence-ready proof before ad scale: security controls, runtime reliability, and clear commercial trust paths.

Security Controls

  • Scoped API keys with separate read/write behavior and readiness checks.
  • Signed webhook delivery and retry visibility for fulfillment handoff.
  • Public legal posture: Terms and Privacy.

Reliability Evidence

  • Live checks visible in System Dashboard.
  • Order runtime readiness and billing health surfaced in operator flows.
  • Release and smoke gates protect against unhealthy rollouts.

Commercial Trust

  • Stripe-managed billing with explicit self-serve cancellation support.
  • Support escalation through /support.html.
  • Pilot starts quickly but stays guardrailed by operational checks.

Where to focus your rollout

This page is for teams that want assistant-first selling. It keeps the current capability line honest while directing traffic into the direct AI path.

Use cases

  • Loading direct AI checkout use cases...

Operational notes

  • Loading operational notes...

Current constraints

  • Loading current constraints...
Commercial path

Monthly pilot now, yearly if the direct flow proves out.

Start Monthly Trial Start Yearly Trial

Technical references

Reference buyer flow

  • Issue short-lived checkout token from /v1/account/checkout-access-tokens
  • Or mint a ready-made branded link from /v1/account/buyer-checkout-links
  • Use merchant_reference_id to correlate lead, buyer link, checkout, and final order
  • Pass email when you want the buyer link locked to one recipient
  • Attach success_url and cancel_url so the buyer page can return to the merchant flow
  • Create public session and update buyer + fulfillment
  • Create payment-intent and confirm client_secret client-side
  • Complete checkout with payment_intent_id
  • Reopening the same branded buyer link resumes the original scoped session until completion; after that it returns 410 buyer_link_consumed
  • If the link is consumed, regenerate it from /v1/account/buyer-checkout-links/regenerate
  • Use /v1/orders/lookup?merchant_reference_id=... to trace the latest checkout session and order state

Reference flows in repo: scripts/public_checkout_flow.sh, scripts/ordercore_quick_setup.sh, scripts/ordercore_connector_quick_setup.sh, scripts/ordercore_merchant_helper.py, scripts/ordercore_merchant_helper.mjs, and scripts/ordercore_merchant_sdk.mjs for create/batch/regenerate/lookup/import/webhook/smoke operations.

What comes next

  • Guided catalog import is available via POST /v1/onboarding/catalog-csv during pilot onboarding
  • Outbound delivery logs, retries, and lookup are available for ops and fulfillment routing
  • Merchant helpers now ship in repo as scripts/ordercore_quick_setup.sh, scripts/ordercore_connector_quick_setup.sh, scripts/ordercore_merchant_helper.py, scripts/ordercore_merchant_helper.mjs, and scripts/ordercore_merchant_sdk.mjs, including webhook delivery metrics, smoke trigger, connector package bootstrap, batch CSV-row buyer link creation, importable Node operations, and machine-readable CLI help

Support path

For direct AI pilots, include your API base URL, current checkout surface, and monthly order volume in the first message.