Write — free
$0
- Start
npm i tersign· API key by DNS domain check, no card (how)- Counter-signed records
- 10,000 per month, at most 1,000 per UTC day, with a verified domain whose public suffix (the list's longest matching rule) is in the ICANN section of the Public Suffix List; 100 per month, at most 50 per UTC day, otherwise, a verified host under a private suffix included
- Receipts and action records, one ledger
- x402 receipts · agent action records (a payment on any rail can be recorded as an action of kind payment), counter-signed into per-party chains and anchored under a chain commitment: a six-hourly cron submits changed commitments for Bitcoin anchoring (a busy or degraded run can defer one), so anchors follow activity rather than the clock (anchor log)
- Support
- community
- Public verification (no account needed)
- Full data-escape export API (
format=full, on demand) and export packs (beta) - Dispute triage (deterministic R1/R2) and evidence envelopes formatted for a supported venue
- Data Processing Addendum
The 10,000-a-month allowance is for a domain whose public suffix (the list's longest matching rule) is in the ICANN section of the Public Suffix List, as the ledger's copy of the list holds it; any other verified name gets its own account with the limits of an account without a verified domain (100 a month, at most 50 per UTC day): a host under a suffix in the list's private section, such as vercel.app, workers.dev, github.io or uk.com, and a name under a top-level label the copy does not list.
Free accounts share one capacity on the ledger: free writing pauses (HTTP 503) for every free account while the ledger's shared free capacity is full, and Records plan writes go on. While it is full the ledger also creates no new free account. Disputes are not part of it: on every plan alike, a dispute opens only with room reserved in the ledger's dispute capacity for its claim, its triage and each party's first evidence item, and while that capacity is full no new dispute opens and no further evidence item is accepted (HTTP 503); each party's first item and triage still run. Records already written stay verifiable and exportable.