Decision Record Pricing

Price the record, not the use case.

Every production call creates a Decision Record v1 object your software can store before it acts: verdict, request_id, decision_id, policy version, evidence, record_hash, replay URL, and action. Start with a pricing-exception gate for CRM or billing, then expand by monthly records, live action boundaries, and operating envelope.

Start with one action boundary.

A boundary is the moment software asks Decide before it acts. The default first boundary is pricing exceptions before CRM or billing changes; the same lifecycle can expand to product, agent, queue, and internal-tool actions after that proof works.

EvaluateRun the sandboxNo key, no spend, just payload and response-shape validation.
IntegrateAttach the recordStore the full Decision Record v1 object next to the downstream action.
ReportReceipt and outcomeRecord attempted execution, then report the observed result.
ScaleBuy production recordsUse policy intelligence when real traffic starts.

What you pay for

Do not buy a platform rollout first. Prove one boundary, then pay for the records and operating envelope that boundary will generate in production.

Decision lifecycle

One request creates the pre-action record; execution and outcome receipts prove what happened after.

Action boundaries

A boundary is a production moment that requires a Decide verdict before software changes state.

Policy intelligence

Effectiveness, confidence, explainable anomalies, benchmarks, packets, and audit chains expand as traffic grows.

What compounds by tier

Every paid tier captures the lifecycle. Higher tiers turn the first pricing-exception boundary into operating reviews, anomaly triage, and packet-ready governance across more systems.

Starter

Capture the lifecycle

Decision Records, execution receipts, Outcome Records, and self-serve packet export for one pricing-exception boundary.

Team

Operate the feedback loop

Policy effectiveness, confidence, and explainable anomaly reports help expand from CRM/billing into support or agent gates.

Enterprise

Govern proof at scale

Benchmarks, packet review, audit-chain governance, and the security packet support multi-system rollout and procurement review. Read docs.

Choose records first, boundaries second

Records set the base tier. Boundaries decide whether you need a self-serve launch, assisted rollout, or enterprise controls.

Recommended tier: API Team for 50,000 decision records/month.

Annual prepay is discounted and shows exact yearly savings per tier.

Book workflow review
Tier 0

Evaluate

$0 / validate

Use this lane before production purchase. No production API key or commercial contract required.

Validation only (no production)

Production boundaries: N/A

Operating envelope: Shared sandbox lane

Best for: Payload QA and API-fit checks before spend.

  • Reference docs and payload QA
  • No production key issuance
  • Docs-first validation

Validate the response API contract before committing to runtime.

Starter

API Starter

$299 / month

Save $720/yr on annual

Annual prepay: $239/mo billed yearly ($2,868/yr, save $720/yr).

Up to 10,000 decision records/month

Production boundaries: 1 live action boundary

Operating envelope: 20 req/min per API key baseline

Best for: First pricing-exception boundary before CRM or billing changes.

  • 20 req/min default per API key
  • Pricing-exception gate for CRM or billing
  • Decision record API contract + evidence fields
  • Execution receipts and Outcome Records
  • Self-serve production runtime for one boundary

Pilot one fail-closed pricing boundary before expanding.

Enterprise

API Enterprise

$3,999 / month

Save $9,600/yr on annual

Annual prepay: $3,199/mo billed yearly ($38,388/yr, save $9,600/yr).

Up to 200,000 decision records/month

Production boundaries: Custom boundary scope

Operating envelope: 150+ req/min commercial contract envelope

Best for: Multi-system governance, verification, and procurement review.

  • Custom throughput/uptime envelope
  • Procurement/security package
  • Custom evidence review and boundary scope
  • Decision Packet exports, benchmark governance, and audit-chain review
  • Implementation support included
  • Multi-team boundary governance

Govern multiple systems with verification and packet review.

Evaluate -> Starter

Unlock production API keys, deterministic records, execution receipts, and one measured pricing-exception boundary.

Starter -> Team

Expand from the first CRM/billing gate into refunds, support, agent, or queue boundaries with policy intelligence reports.

Team -> Enterprise

Governance controls, procurement package, benchmark review, verification, and custom multi-system boundary scope.

Plan summary
API Team Up to 50,000 decision records/month · Monthly billing
Request Team

Feature matrix

Pick a category tab to reduce scanning. Use “Show all categories” if you want the full table at once.

Capability Evaluate API Starter API Team API Enterprise
Production API access No Yes Yes Yes
Included monthly decision records N/A Up to 10,000 Up to 50,000 Up to 200,000
Production boundaries included N/A 1 live boundary Up to 3 live boundaries Custom boundary scope
Throughput envelope Shared demo lane 20 req/min per API key baseline 60 req/min baseline, commercial expansion available 150+ req/min commercial contract envelope
Default /api/decide guardrail N/A 20 req/min per API key Higher commercial contract envelope Custom
Execution receipts and Outcome Records No Included Included Included
Policy intelligence reports Docs examples only Lifecycle capture and effectiveness basics Effectiveness, confidence, anomalies Benchmarks, packets, and custom review
Launch support No Self-serve only Included Included
Post-checkout onboarding N/A Docs + email handoff Kickoff + implementation support Rollout planning + governance setup
Volume expansion path N/A Burst packs (+10k / +25k / +50k records) Burst packs or move to Enterprise Custom commercial expansion
Security/procurement package No Limited Standard package Full custom package
Decision Packet exports and audit chains Public examples Self-serve packet export Packet export and chain review Contracted audit-chain governance
Best fit Technical validation First production boundary Multiple action boundaries Multi-team or strict enterprise controls

Swipe horizontally to compare all columns.

Need help choosing? Email support@decide.fyi or review Live proof, Decision API docs, Status, and Security.

Need procurement or fit help? Use whichever channel is fastest for your team.

Burst packs

No surprise overage invoices. Prepay additional monthly record capacity when a boundary spikes.

+10,000 records

$399 one-time

Fast top-up for short peaks in Starter or Team.

One-time purchase · valid current billing month · non-recurring.

+25,000 records

$899 one-time

Balanced pack for launch-month and seasonal lift.

One-time purchase · valid current billing month · non-recurring.

+50,000 records

$1,599 one-time

Large pack before moving to a larger custom tier.

One-time purchase · valid current billing month · non-recurring.

Burst packs add current-month decision-record capacity to your active API key. They do not change your base plan tier.

Quick FAQ

How does annual billing work?

Annual mode shows discounted monthly equivalent pricing and the full yearly total. Savings are shown per tier on-card.

When do API keys get provisioned?

After successful payment and webhook mapping, API key provisioning starts automatically. Team and Enterprise can include assisted onboarding.

Are outcomes and policy intelligence included?

Production tiers include the lifecycle endpoints for execution receipts and Outcome Records. Team and Enterprise are the better fit when policy effectiveness, confidence, explainable anomaly reports, benchmarks, and packet review are part of the rollout.

How do burst packs behave?

Burst packs are one-time, non-recurring top-ups for the current billing month and do not change your base tier.

Can we cancel or change plan later?

Yes. You can switch billing mode and tier path as your volume evolves; Enterprise changes are handled via commercial scope updates.