Curated models for your best work

Join the waitlist
Log inGet API key

Know where every boundary sits.

Fleet capture and Router traffic are different data paths. This page states what TokenSpend stores, what downstream providers control, and which facts are pinned to each receipt.

Capture and Router data

Token counts, timestamps, model names, repository names, branches, and git refs.

Fleet capture

Token counts, timestamps, model names, repository names, branches, and git refs. Never prompts, responses, source code, diffs, transcripts, or tool output.

Router traffic

TokenSpend does not store prompts or responses. Requests pass through in memory; receipts keep metadata only. If a workspace admin turns on work labels, requests are also read in memory after the reply to label the kind of work, and only that label is kept.

Before production

Availability, support and coding agent setup.

Review availability and support. The status page reports sampled checks, not a contractual uptime guarantee.

Read the coding agent setup. Each guide shows the exact config and how to check the receipt.

Route boundary

TokenSpend stores no content. Provider retention is separate.

TokenSpend stores no prompts or responses. Downstream retention follows the applicable provider account, configuration, policy, and contract.

TokenSpend does not currently offer provider ZDR. Any existing downstream handling requirement remains enforced across retries and fallback. Missing or stale evidence blocks the attempt. Enforcement details

Boundary 2026-10-02.1, reviewed 10/2/2026. Open machine-readable route record

BYOK

Credential owner
Customer workspace
Recipient
Selected model provider or contracted inference processor
TokenSpend retention
No prompt or response content is stored
Downstream data use
Governed by the customer's provider account, policy, and agreement
Provider retention
Set by the customer's provider account, configuration, policy, and agreement
Training boundary
Set by the customer's provider terms and configuration. TokenSpend makes no training-use claim.
Region
Customer provider configuration for direct APIs; US or EU default for open-weight routing
Retention scope
TokenSpend does not store content. Downstream retention follows the customer's provider agreement.
Contractual ZDR
No downstream ZDR guarantee unless a signed Enterprise order expressly provides one

Managed credits

Credential owner
TokenSpend
Recipient
Selected model provider or contracted inference processor
TokenSpend retention
No prompt or response content is stored
Downstream data use
Governed by TokenSpend's provider agreement and service configuration
Provider retention
Provider-specific; set by TokenSpend's provider account and agreement
Training boundary
Governed by the applicable provider agreement and configuration. TokenSpend makes no training-use claim.
Region
Provider-controlled for direct APIs; managed Muse Spark excludes Meta-restricted territories; managed Grok excludes sanctions-restricted territories; US or EU default for open-weight routing
Retention scope
TokenSpend does not store content. Downstream retention follows TokenSpend's provider agreement.
Contractual ZDR
No downstream ZDR guarantee unless a signed Enterprise order expressly provides one

Every successful response names the provider that served it, and the receipt records it; model pages list the providers behind each model. The processor list is on the subprocessors page. Workspace admins can request applicable downstream terms, retention details, and deletion escalation through privacy@tokenspend.dev.

Pricing provenance

Registry 2026-11-09.1

Registry 2026-11-09.1

Observed 9/17/2026. New receipts carry this version, their token basis, and six-decimal USD rounding.

Open machine-readable registry

Policies and requests

Current public versions

Current public versions

Read the dated privacy notice and terms. Security reports, deletion requests, DPA requests, and processor questions go to the contacts on those pages.

Changelog

  • Registry 2026-11-09.1

    New receipts carry this version, their token basis, and six-decimal USD rounding.

  • Boundary 2026-10-02.1

    TokenSpend stores no prompts or responses. Downstream retention follows the applicable provider account, configuration, policy, and contract.