curl and the open-source
auditor. You will:
- Authenticate to your sandbox tenant.
- Find an active right to deliver against.
- Observe a delivery event.
- Seal and fetch the signed proof pack.
- Verify the pack offline with the open-source auditor.
The hosted sandbox is available now. Request access at
enfinitos.com/apply; once your application is
approved you receive an activation email, and you exchange that for a
/v1
sandbox key in the integration playground.
Self-service key issuance from the developer dashboard lands at the April 2027
production launch.https://sandbox.api.enfinitos.com/v1/*, and every response uses the same
envelope:
"ok": false, a machine-readable error
code, and a human-readable message:
1. Authenticate
Set your key and read your tenant.GET /v1/tenant returns your tenant
snapshot, your developer profile, and the scopes on your key.
cURL
Response
2. Find an active right
You deliver against an active right (rgh_...). List your rights and
pick one whose status is ACTIVE:
cURL
{ "ok": true, "data": { "rights": [...], "nextCursor": null, "total": N } }.
Grab a rightId from the list. (No active rights yet? Issue one from a
rights base with POST /v1/rights/issue — see the API reference.)
3. Observe a delivery event
POST /v1/delivery records that content rendered against a right. The
substrate constraint gate runs first; a violation comes back as
412 PRECONDITION_FAILED.
The hosted sandbox collapses the Resolve step into
POST /v1/delivery —
the constraint gate runs server-side at delivery time, so there is no
separate /v1/world-model or /v1/resolve call to make today. Those
ship as first-class primitives at the April 2027 production launch.cURL
receipt and the substrate it landed on:
Response
4. Seal and fetch the proof pack
POST /v1/proof-packs/seal folds every delivery since the last seal into
one signed, hash-chained pack. Then fetch it by id.
cURL
GET /v1/proof-packs/{packId} returns
{ "ok": true, "data": { "proofPack": { ... } } } — the full signed pack
(receipts plus the Ed25519 signature), ready to hand to the auditor. List
every pack with GET /v1/proof-packs.
5. Verify the pack offline
The auditor is the open-source library that checks the signature, walks the hash chain, re-projects metering, and re-runs settlement reconciliation. It never calls home — and it’s the one SDK published today.The full client SDKs (renderer-core, brand, operator-web, and the substrate
SDKs) ship at the April 2027 production launch. Until then the
/v1 HTTP API
above works against your sandbox credentials today, and the auditor verifies
every pack the platform issues.Next steps
Guided-demo API reference
The cookie-authed sandbox demo surface, with request and response
shapes. The key-authed
/v1 families are documented on the
concept pages and SDK integration map.Proof-pack format
The canonical-JSON shape, signing scheme, and chain semantics.
SDK catalogue
The full SDK catalogue across every substrate the platform governs.
Substrate model
Why a single rights handshake governs 23 substrates.