Stratum Developer Docs
Bilateral reconciliation is a structural failure, not an integration inconvenience. Every multi-party operation still asks the same questions (who owns what, when it settled, and which rules apply) while each party keeps its own answer.
Stratum is the multi-party system of record for those answers. The unit of record is shared ledger state that no single participant controls: ownership, settlement, and applicable rules. Partners and operators interoperate through a stable HTTP contract—token and ingest gateways, auth, errors, envelopes, and upgrade expectations—while ledger applications evolve behind that contract. These pages publish the contract. They do not publish how on-ledger applications decide validity. See Disclosure Boundary.
Who this is for
When counterparties disagree about ownership, settlement, or which rules applied, you need one shared answer. Use this table to see if Stratum is your path.
| You are… | The problem you feel | What Stratum gives you |
|---|---|---|
| Integrator / SaaS builder | Fragile bilateral sync; reverse-engineering a ledger to ship product | Predictable HTTP gateways (token + ingest) with dashboard-minted keys and a published OpenAPI |
| Wallet / token client | Admin-heavy or opaque value movement | Partner wallet ops—issue, transfer, redeem, quote, balance, history—without admin routes |
| Platform operator | Readiness and liveness collapsed into one probe; no shared SLIs | Separate /health/ready and /health/live, plus Prometheus /metrics |
| Host / partner operator | Day-2 create / join / lifecycle lives in tribal knowledge | Network Ops overview in public docs; samples and node admin stay signed-in |
| Technical evaluator | Build-vs-buy without a clear interoperability contract | Public maturity matrix and a technical briefing before you mint a key |
Start here. Dashboard access already? Mint a key under API Keys and follow Authentication. No key yet? Book a technical briefing, then return to Integration Surfaces to confirm what is Live.
This documentation set is Early Access (v0): pages state what is live today versus roadmap. It answers how do I interoperate with Stratum?, not how on-ledger applications reach shared state or decide validity. Stratum is not a public chain, a scoring engine, or a bilateral sync product — it is the multi-party system of record; the HTTP gateways are the stable interoperability surface. See Disclosure Boundary.
Explore by topic
| Topic | Start here |
|---|---|
| What Stratum is and which surfaces exist | Integration Surfaces |
| How to authenticate | Authentication |
| Wallet issue, transfer, redeem, quote, balance, history | Tokens |
| Write JSON to a network | Webhook ingest |
Networks and networkId | Networks |
| Machine-readable REST contract | API reference |
Use the matrix above to pick a starting page. The sections below expand what Stratum delivers and how the HTTP contract relates to shared ledger state.
What Stratum gives you
| Capability | What it gives you |
|---|---|
| Shared sealed state | One answer across parties without bilateral reconciliation |
| Token gateway | Issue, transfer, redeem, quote, balance, and history under partner scopes |
| Webhook ingest | POST JSON to a network via the ingest gateway (Marketplace Addon) |
| Published OpenAPI | Typed clients from the contract — no first-party SDK required |
| Health / SLIs | Readiness vs liveness probes and Prometheus /metrics |
| Day-2 Network Ops | Shared-space create / join / lifecycle (overview public; samples signed-in) |
| Product Concierge MCP | Public product Q&A for agents within the disclosure boundary |
Confirm maturity on Integration Surfaces before you assume more.
How the system fits
Three layers. Do not collapse them into a single claim.
- HTTP contract (Live). Public token and ingest gateways, auth headers, error envelopes, health probes, and OpenAPI. What integrators build against today.
- Shared ledger state (Live). Multi-party sealed record behind that contract: ownership, settlement, and applicable rules. Ledger applications upgrade without changing the published HTTP surface.
- Day-2 Network Ops (Live, gated). Create / join / lifecycle for host and partner operators. Overview is public; node-admin samples stay signed-in—not on the public OpenAPI.
Beyond these boundaries, how on-ledger applications decide validity is not part of this contract.
Reading order
Product vocabulary
| To answer | Read |
|---|---|
| Which surfaces are Live vs roadmap | Integration Surfaces |
How networks and networkId work | Networks |
| What an error looks like | Errors |
| Will my client break on upgrade | Upgrade & compatibility |
| What stays public vs private | Disclosure Boundary |
Integrator path
| To answer | Read |
|---|---|
| Which surface can I build against today | Integration Surfaces |
| Auth and key lifecycle | Authentication |
| Wallet ops | Tokens |
| Write JSON to a network | Webhook ingest |
| Machine-readable REST contract | API reference |
| Readiness, liveness, SLIs | Observability |
Mint API keys under Dashboard → Developer →
API Keys (token and/or ingest scopes). Copy the
exact token-gateway or ingest base URL shown for that key. Send
X-Api-Key on every request. Live try-it is off on this portal—use curl or your
own client; do not paste keys into the docs origin. Signed-in operators: mint keys and read
operator auth under Dashboard → Account →
Developer API docs.
Resources
Networks
networkId vocabulary and day-2 Network Ops overview.
Integration Surfaces
Maturity matrix for gateways, OpenAPI, MCP, SDK, and CLI.
API reference
Browse the OpenAPI 3.1 contract for token and ingest gateways.
Disclosure Boundary
What is published for interoperability — and what stays private.