EnfinitOS is the operating layer for governed screen and spatial execution, proof, and rollout. This is the developer documentation — the public-facing reference for every SDK, the full OpenAPI 3.1 spec, and the open-source auditor that verifies every proof pack the platform issues.Documentation Index
Fetch the complete documentation index at: https://enfinitos.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
The six-layer architecture
Control
Define who can run what, under which rules, with which explicit
rollout and promotion permissions.
Runtime
Operate execution across screen estates through a disciplined
runtime instead of ad hoc orchestration.
Spatial
23 substrates from DOOH to drones — first-class in the type
system, governed by the same runtime.
Proof
Every delivery, activity, and operating action is inspectable —
signed, chained, and verifiable offline.
Metering
The usage and operational signals required for accountable
commercial, operational, and customer review decisions.
Settlement
A path from verified activity into finance, invoicing, and
settlement discipline without bolting it on later.
The two pillars of trust
Signed and chained
Every proof pack is signed by EnfinitOS with a long-lived Ed25519
key whose public half is published. Each pack references the
SHA-256 hash of the previous pack for the same tenant.
Open-source verifier
The auditor / verifier trio is open source under MIT. Fork it,
audit it, fuzz it. No operator has to trust EnfinitOS as a
vendor to verify what the platform issues.
Where to next
Quickstart
Send your first signed event to the EnfinitOS sandbox in under
five minutes.
API reference
The full OpenAPI 3.1 reference — try every endpoint against a
sandboxed tenant.
SDK catalog
Twenty-eight SDKs across 23 substrates — TypeScript, Python, Go,
Java, Ruby, Rust, Swift, Kotlin, and more.
Substrate model
Why “substrate” rather than “channel” — and how composing
Renderer Core lets a single rights handshake govern every
screen you ship.