Changelog
v1 changes additively: fields and endpoints may be added, and the version rises with them. Nothing is removed or renamed inside v1, so an integration written against today’s contract keeps working. Every response tells you which version answered it, in Rivet-Api-Version.
Deployed here: v1.5.0
1.5.0The provenance family (provenance:read): GET /v1/documents/{id}/history (verified on every read), /lineage (sealed counterparty steps), and /export — a byte-deterministic proof bundle verified OFFLINE with a published script; Rivet-Bundle-Digest is the sha256 of the exact bytes. Document-anchored payments gain POST /v1/documents/{id}/pay (full balance, idempotent across the async settlement gap) and per-key payment_limits set at mint (payment_limit_exceeded names the limit). Webhooks gain payment.settled / payment.failed, and sandbox deliveries are marked sandbox:true.1.4.0The fiat payment rail over the API. Moving a document into its payment states (payment_scheduled, paid) now executes its payment, gated on the new payments:write scope: simulated in the sandbox, and live once the organization's payment processor is connected (capability_unavailable until then). The transition body gains optional payment_method, source_account_id and scheduled_for.1.3.0Webhooks — register signed endpoints and receive document.created / document.status_changed / document.edited, each projected for your organization; at-least-once with retries, replay and rotation. Documents gain an updated_since polling filter and a cross-type phase filter, plus a signed-download attachments endpoint. And an MCP server (@rivet/mcp) exposes every operation as Model Context Protocol tools, generated from this spec.1.2.0Document writes (create drafts, edit them, issue, transition — Idempotency-Key required on every write, per-line tax, conflicts answer with the legal set) and the sandbox (a provisioned practice pair with a demo counterparty). Key prefixes now follow the organization — sandbox keys are rk_test_, live keys rk_live_, hard-isolated; keys minted before this rule need re-minting. New error codes: conflict, idempotency_conflict, sandbox_isolation, sandbox_quota. Upcoming event names are reserved in the spec for future delivery.1.1.0Added GET /v1/enablement — an unauthenticated read of which families this deployment can serve, so a consumer never keeps its own copy of the switch.1.0.0First release. Read-only documents and payments, org-scoped keys with scopes, cursor pagination, one error envelope, per-key rate limits.