Disclosure Boundary

Forward this page in security or vendor-risk reviews without edits.

These docs answer how do I call Stratum’s public token and ingest gateways? They do not answer how on-ledger logic decides shared state. For what is Live vs roadmap, see Integration Surfaces.

Purpose

Integrators need a stable contract: auth headers, error envelopes, wallet routes, health probes, and upgrade expectations.

What stays private: ledger judgment, validation policy design, and proprietary adapter transforms.

Published

• Dashboard-minted X-Api-Key on the public token gateway and public ingest gateway
• Webhook ingest (Marketplace Addon): POST /{networkId} on the ingest gateway — Webhook ingest
• Token gateway wallet ops (issue, transfer, redeem, balance, history) — Tokens
• Operator capability overview for day-2 Network Ops — Networks → Network Ops
• Error envelope { error: { code, message } } and common codes — Errors
• Health probes (/health/live, /health/ready) and SLI names (RPS, error%, p95)
• Upgrade posture: HTTP routes are the stable contract — Upgrade & compatibility
• Synthetic request/response examples only
• Surface maturity — what is Live vs not yet public — Integration Surfaces

Never published

• Production API keys, node hostnames/IPs, or tenant network diagrams with real addresses
• Instructions to dial node hosts for partner wallet or ingest traffic (use the public gateways)
• Ledger application source, validation policy internals, or private data schemas
• Proprietary adapter transformation logic or customer payload samples
• Future runtime migration internals ahead of a public playbook
• Real wallet IDs, balances, or transaction IDs from customer networks
• Underlying ledger platform stack or vendor identifiers
• Day-2 shared-space / lifecycle node admin HTTP, join-material storage paths, and full operator code samples (signed-in Network admin only)
• A public list/get-networks HTTP API (operators list networks in the dashboard)

Three-line test

Before shipping any page:

1. Describes the interface an actor calls, not how the ledger decides validity.
2. Names routes and signals, not internal upgrade tooling beyond the public playbook.
3. Explains verification of readiness/metrics, not how to bypass gateway or key controls.

Pages that fail this test are not shipped.