Disclosure Boundary

These docs define the interoperability contract for Stratum’s HTTP surface. They answer how do I call token / ingest APIs? They do not answer how on-ledger logic reaches shared state?

Link this page from security reviews without edits. For what we mark Live vs roadmap (MCP, SDK, CLI), see Integration Surfaces.

Purpose

Integrators need stable vocabulary: auth headers, error envelopes, wallet and asset routes, health probes, and upgrade expectations. Judgment about ledger correctness, validation policy design, and proprietary adapter transforms stays private.

Published

• X-Api-Key on public token and ingest gateways (dashboard-minted keys)
• Public webhook ingest (Marketplace Addon): POST /{networkId} on the ingest gateway — Webhook ingest
• Public REST paths for tokens (wallet ops) and asset contract shapes
• Operator capability overview for day-2 Network Ops — Networks → Network Ops
• Error envelope { error: { code, message } } and common codes
• Health: /health/live vs /health/ready and SLI names (RPS, error%, p95)
• Upgrade posture: HTTP routes are the stable contract — see Upgrade & compatibility
• Synthetic request/response examples only
• Surface maturity on Integration Surfaces — what is Live vs not yet public

Never published

• Production API keys, node hostnames/IPs, or tenant network diagrams with real addresses
• 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.