Dev console — coming soon
DEV CONSOLE
The dev console is the self-serve app for the DEV CONSOLE access tier defined in SPEC.md §7: API-key signup (Auth0 OIDC), asset registration, envelope/telemetry endpoints keyed to your asset's cert, and a play-money device ledger. It is a separate app on a separate origin from this docs site and from the SP DASHBOARD (corporate SSO, operator-only) — dev-console credentials never reach SP-dashboard surfaces, and every capability the dashboard has is available through the same documented DEV CONSOLE / PUBLIC APIs any zone participant can use. No privileged backdoors.
Self-serve signup isn't live yet — the dev console is coming soon. Until then, everything on this docs site works without it:
- Use each SDK's in-process
MockSandbox, which exposes the exact same method surface as a live zone — see the Python and TypeScript quickstarts. - The API reference documents the HTTP/WS wire surface a hosted sandbox zone exposes.
When the real dev console ships, GripClient("https://sandbox.protocol.standardpower.co")
(or the production zone origin) replaces MockSandbox() with no other code
changes — both expose the identical method surface.
What you'll get here later
| Capability | Tier | Auth (planned) |
|---|---|---|
| API key issuance | DEV CONSOLE | Self-serve OIDC (Auth0) |
| Asset registration + cert lifecycle | DEV CONSOLE | API key |
| Envelope request/read | DEV CONSOLE | Cert key |
| Per-node signal subscription | DEV CONSOLE | Cert key |
| Telemetry ingest | DEV CONSOLE | Cert key |
| Device registry, compliance score, play-money ledger | DEV CONSOLE | Self-serve login |
Exchange order entry, cancels, and campus-ops surfaces are SP DASHBOARD tier (corporate SSO) — out of scope for the dev console and for this public docs site. See SPEC.md §7 for the full surface map.