Commercial Terms
API access terms + cancellation policy.
Concise commercial terms for API access kickoff, production API plans, and guided implementation. Use this page as the shared baseline before checkout or procurement review.
Last updated: May 23, 2026 (UTC)
API access kickoff scope
- One scoped decision boundary; reference applications can be used when source-backed refund, cancel, return, or trial evidence is needed.
- Fit check, integration checklist, KPI baseline/target, and first production boundary plan.
- Readiness review for Decision Records, execution receipts, Outcome Records, verification, and packet export.
- Production access recommendation at the close of the scoped kickoff window.
Payment, cancellation, and refunds
- API access kickoff fees are billed up front as a one-time payment unless a signed order states otherwise.
- If customer moves to a paid production plan within 30 days, decide may apply a one-time access kickoff credit to the first production invoice when stated in the checkout or written order.
- Full refund is available if canceled within 48 hours of payment and before kickoff starts.
- No refund after kickoff begins or access deliverables are sent.
- If decide cannot start kickoff within 5 business days after completed request, customer may request a full refund.
Production billing terms
- API Starter: $299/month or $2,868/year (annual prepay), up to 10,000 decision records/month for one live boundary.
- API Team: $1,199/month or $11,508/year (annual prepay), up to 50,000 decision records/month across multiple boundaries.
- API Enterprise: from $3,999/month (or contract), up to 200,000 decision records/month baseline with custom boundary scope.
- Guided implementation and burst packs can be purchased separately (checkout or scoped quote).
- Cancellation applies to the next billing cycle (cancel before renewal date).
- No prorated refunds for partial month after a cycle starts.
- Commercial plans include the agreed operating envelope, launch support, and audit export controls per scope.
Plan review matrix
| Path | Best fit | Commercial review note |
|---|---|---|
| API Starter | One production decision boundary and one team owner. | Use checkout terms, API docs, and status page before provisioning. |
| API Team | Multiple boundaries, higher record limits, and shared engineering ownership. | Review trust, security, packet verification, and support boundaries before launch. |
| API Enterprise | Custom operating envelope, procurement review, or written security addendum. | Requires scoped agreement for custom retention, support, uptime commitments, or security terms. |
| Guided implementation | Teams that want help selecting the first state-changing workflow. | Customer still owns final deployment, data quality, and downstream system permissions. |
Security and data boundaries
- Production API keys are server-side credentials and should not be exposed in browsers, client apps, or public repositories.
- Customers should avoid unnecessary personal data in prompts, context fields, or evidence payloads.
- Security review uses the public Security page plus scoped questionnaire responses when requested.
- Status and readiness exports are operational snapshots, not certification reports or contractual uptime guarantees.
Support and launch boundaries
- Starter and Team support is async through support@decide.fyi unless a signed order states otherwise.
- Enterprise support, uptime commitments, custom retention, and security addenda require a written agreement.
- Guided implementation covers integration planning and launch review; customer systems, data quality, and final deployment remain customer responsibilities.
Written agreement precedence
- These API access terms supplement the public Terms and Privacy pages for checkout and implementation review.
- If a signed order, security addendum, data processing addendum, or enterprise agreement conflicts with this page, the signed agreement controls for that customer.
- Certification, uptime, custom retention, and dedicated support commitments only apply when written into an executed agreement.
Procurement review links
Use these public artifacts to review the commercial, security, operational, and technical parts of API access.
TermsPublic service terms and written-agreement precedence.
PrivacyData handling and privacy baseline.
SecurityControls, boundaries, and review checklist.
StatusRuntime readiness, monitors, and readiness export.
Trust packetBuyer review sequence and procurement bundle.
VerificationRecord, packet, receipt, and key checks.
Questions or custom procurement terms: support@decide.fyi.