GET /health → POST /v1/onboarding/demo-data → POST /v1/orders and prove retry-safe order creation.
OrderCore is API-first checkout infrastructure and the API that lets AI agents complete purchases, without forcing a storefront replatform.
Built for developers shipping AI apps: start a 3-day trial, validate one production-safe order path, and decide go-live with evidence instead of guesswork.
GET /health → POST /v1/onboarding/demo-data → POST /v1/orders and prove retry-safe order creation.
oc_live_... key.
/v1/orders with idempotency for safe retries.
Security, reliability, and commercial trust points visible before a buyer commits to trial.
Scoped API keys, read/write separation, and release gates that block unhealthy rollout states.
Public health visibility + scripted smoke checks for auth/readiness/billing and direct AI tooling paths.
Stripe-managed billing, explicit cancellation path, and direct support contact for onboarding.
OrderCore is a developer-first API checkout layer. It lets teams ship AI-driven purchases without rebuilding billing, idempotency, and webhook delivery behavior.
OrderCore provides the backend path for AI-assisted commerce: product retrieval, pricing, inventory, idempotent ordering, and webhook delivery with production-safe behavior.
Simple, predictable, and fast. Just how AI agents like it.
# List products curl "https://api.ordercore.ai/v1/products" \ -H "X-API-Key: oc_live_abc123..."
No storefront replatform required. Trial first, validate one order path, then scale.
Run GET /health to verify endpoint reachability before integration.
Run POST /v1/onboarding/demo-data so first order does not depend on guessed SKU IDs.
Call POST /v1/orders with Idempotency-Key for safe retries.
Start trial first to get your oc_live_... key, then run the same first-success sequence shown here and in docs.
Need direct AI checkout help? Email support@cloudpeakify.com or review the direct AI checkout page.
# 0) Set API key from trial checkout export API_KEY="oc_live_..." # 1) Health preflight curl -sS "https://api.ordercore.ai/health" # 2) Seed tenant demo data (idempotent) SEED_JSON=$(curl -X POST "https://api.ordercore.ai/v1/onboarding/demo-data" \ -H "X-API-Key: $API_KEY" \ -H "Content-Type: application/json" \ -d '{}') # 3) Resolve sample identifiers from onboarding response CUSTOMER_ID=$(printf '%s' "$SEED_JSON" | jq -r '.sample_customer_id // empty') SKU_ID=$(printf '%s' "$SEED_JSON" | jq -r '.sample_order_item.sku_id // empty') test -n "$CUSTOMER_ID" && test -n "$SKU_ID" # 4) Create first order (idempotent) curl -X POST "https://api.ordercore.ai/v1/orders" \ -H "X-API-Key: $API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: first-order-001" \ -d "{\"customer_id\":\"$CUSTOMER_ID\",\"items\":[{\"sku_id\":\"$SKU_ID\",\"quantity\":1}]}"
Quick overview first. Full 6-minute walkthrough is linked below.
Commerce primitives designed for programmatic access
Native UCP checkout endpoints. Use OrderCore as the commerce layer for GPT, Gemini, Claude, Grok, and any UCP-compatible agent.
SKUs, variants, categories, and media. Structured data for machine consumption.
Stock levels across locations. Reserve, adjust, and track with atomic operations.
Price lists, customer tiers, quantity breaks, and multi-currency support.
Safe retry logic built-in. State machine with full audit trail.
Real-time notifications. Pub/Sub ready. Automatic retry with exponential backoff.
Yes. OrderCore is API-first. Start direct AI checkout first, then connect a store only if your merchant flow requires it.
You get pilot onboarding, demo data seed path, and assisted validation of a first successful idempotent order flow.
Yes. Billing runs through Stripe and you can cancel from the customer portal before the paid cycle starts.
Most teams can reach first success quickly using /health, /v1/onboarding/demo-data, and /v1/orders, then harden with webhooks.
Buy only after technical fit is proven: 3-day trial first, then monthly or yearly billing.
Start trial now, or send your stack context and we will route you into the right direct AI checkout or connector onboarding path.