Server-side keys
Production callers use scoped x-api-key calls from backend systems, not browser-visible workflow steps.
Platform
Runtime + control plane for production decisions.
Keep execution inside your product, pricing, routing, eligibility, or operator workflow. Decide handles the verdict API contract, API keys, limits, usage, audit exports, and rollout visibility.
Production control-plane packet
This page explains what production access adds around the Decision API: key custody, quota visibility, runtime readiness, and exportable lifecycle evidence that reviewers can inspect without adopting a new workflow UI.
Plan and usage envelope
Monthly record tiers, quota headers, and default rate limits make rollout behavior predictable.
Decision Packet v1
Export records, execution receipts, Outcome Records, policy intelligence, and verification hints for buyer review.
Status and readiness
Public status, readiness export, and smoke checks give launch owners a concrete operations packet.
API referenceEndpoints, auth, limits, response views, and idempotency.
Verification docsHosted, API, CLI, packet, registry, and fixture checks.
Status packetRuntime readiness, monitor view, and compliance export.
Security packetData handling, responsibilities, provider notes, and review checklist.
API access termsCommercial scope, billing, support, and written-agreement precedence.
Trust packetReview sequence for product, security, legal, engineering, and launch owners.
What ships now
The production surface is a thin control plane. Teams do not need another daily dashboard; they need predictable runtime behavior and evidence when procurement, QA, or operators ask for it.
Integration runtime
Decision routing stays in your existing workflow.
/api/decidefor yes/no/review routing plus Decision Record v1 fields.- Action Execution Receipt and Outcome Record calls for the lifecycle after authorization.
- Reference application checks through refund/cancel/return/trial endpoints when source-backed evidence is needed.
- Deterministic output fields mapped into Decision Records, Decision Packet v1, automations, agents, or internal actions.
Control plane essentials
Visibility and governance for paid rollout and production operations.
- API keys, plan limits, and usage metering.
- Audit search by
request_id,decision_id,record_hash, andreceipt_hashwith exportable evidence. - KPI baseline vs current snapshot for rollout readouts.
- Status and readiness surfaces for buyer review before launch.
Reference application flow in production
| Workflow stage | System action | Stored evidence |
|---|---|---|
| Route decision | Workflow posts decision context to /api/decide. |
Decision Record v1: verdict, IDs, action binding, policy version, evidence, record_hash, receipt_hash, verify URL, and replay URL. |
| Run reference check | Workflow calls the matching reference endpoint with vendor + source args. | Verdict, evidence code, latency, req/resp hashes. |
| Apply action | Application, agent, or automation applies the approved next step and records an execution receipt. | Action Execution Receipt: target system, mutation, executor, state hashes, action binding hash, and execution hash. |
| Report outcome | Workflow records the observed result after the action succeeds, fails, or routes to review. | Outcome Record: outcome status, action taken, target system, observed metrics, and outcome hash. |
| Review + export | Ops lead exports Decision Packet v1 for QA, security review, launch review, or disputes. | Lifecycle history linked by request_id, decision_id, record_hash, receipt_hash, and packet hash. |
Production lifecycle surfaces
The platform surface is intentionally narrow: it helps teams operate the protocol, not replace the systems where actions happen.
| Surface | Production question | Reviewer artifact |
|---|---|---|
| Decision Record | Was the action authorized, blocked, or routed to review? | Decision Record v1 with verdict, evidence, policy version, hashes, replay URL, and verify URL. |
| Action Execution Receipt | Was the authorized mutation actually attempted? | Execution receipt with target object, mutation, executor, state hashes, and execution hash. |
| Outcome Record | What business result happened after the action? | Outcome status, observed metrics, action taken, target system, and outcome hash. |
| Decision Packet v1 | Can a reviewer inspect the lifecycle outside the control plane? | Portable packet with record, execution receipts, outcomes, policy intelligence, audit-chain metadata, and verification hints. |
Access model by tier
| Tier | Access | Primary use |
|---|---|---|
| Evaluate ($0) | Public playground and docs, no production key or contractual uptime terms. | Validate payload shape and deterministic behavior before spend. |
| API Starter | Keyed /api/decide, 10k records/month, default rate limits. |
One production boundary owned by one team. |
| API Team | 50k records/month, larger throughput envelope, launch support. | Growing production traffic across multiple action boundaries. |
| API Enterprise | 200k+ records/month, custom uptime/security terms, and procurement package. | Multi-team governance, stricter controls, and procurement review. |
Public docs and marketing stay on decide.fyi. Authenticated controls expand during rollout and production onboarding.
Operational handoff
Use this sequence when moving from evaluation to the first production action boundary.
Access
Create the production API key, keep it server-side, and scope the first rollout to one action boundary.
Quotas
Confirm the record tier, rate limits, and quota behavior that the workflow should treat as non-approval states.
Monitoring
Review status, readiness export, and smoke-check outputs before launch owners send live traffic.
Evidence
Export a Decision Packet v1 from the first live run and verify it before forwarding the proof packet.
Expansion
Add the next action boundary only after the first one has stored records, execution receipts, outcomes, and a stable review path.