Skip to main content
EnfinitOS publishes 28 SDKs across 23 substrates. Every SDK is a thin client over the same governed HTTP API documented in the API reference. They differ in language, in the substrate they target, and in whether they wrap a native UI surface or just sit alongside one.

Auditor / Verifier

The cryptographic verification library. Open source under MIT. TypeScript, Python, Rust — byte-compatible.

Operator Web

React component library — embed the EnfinitOS operator surfaces in your own admin UI.

Brand SDK

Read-only REST client. TypeScript, Python, Go, Java, Ruby.

CLI

Operator-facing terminal — rights, offers, challenges, proof packs, consent, drills, audit export.

Renderer Core

The substrate-agnostic foundation. Every render SDK composes it.

Render SDKs

DOOH, streaming, CTV, mobile, AR / glasses / hologram, gaming, automotive, smart home, wearables, audio, messaging.

Robotics & drone

Robotics (TS, Python) — geofencing, kinematic envelopes, e-stop. Drone adds Remote ID, NOTAM, BVLOS waivers.

Transit & broadcast

Adapter-mostly SDKs: satellite, aviation, maritime.

​
Status taxonomy

We label every SDK with its real shipping status: Substrate readiness is tracked separately from per-SDK status, in the substrate readiness matrix on the public developer hub.

​
Versioning

All SDKs follow semantic versioning. A 1.0.0 release is the commitment that public types and method signatures are stable until the next major bump. Until then we’re on 0.x and expect minor breaking changes within the same 0.x line — captured in each SDK’s CHANGELOG.md.

​
Source of truth

The HTTP API is the single source of truth. Every SDK is generated or hand-written to mirror it. If an SDK appears to disagree with the API reference on the shape of a request or response, the API reference is correct — the SDK is the bug. Please report it.