Developers

Use the API Kingdom Nexus actually exposes

The old page documented a nonexistent api.kingdomcore.app domain, per-guild bearer keys and signed webhooks. Those have been removed; the developer surface now matches the current authenticated Nexus server.

Add to Discord Open production Nexus Current docs

Current developer surface

HTTP API, OpenAPI and SDK

OpenAPI document

Authenticated Nexus users can request the current API document at /api/openapi.

JavaScript SDK

The repository ships a zero-dependency browser/Node-compatible client for the Nexus API and live stream.

Live stream

GET /api/live/stream provides a Server-Sent Events stream, with GET /api/live available as a snapshot fallback.

Operational reads

Authenticated reads include products, status, live operations, intelligence, Sentinel, network, Companion and creators.

Operator reads

Identity, applications, Vault, Studio layouts and audit records apply the operator authorization layer.

Protected mutations

Current Nexus writes are permission-checked and require CSRF validation on protected write methods.

Current read routes

With the exception of health and session discovery, Nexus API access requires its validated Discord session or configured recovery authorization.

nexus-routes

GET  /health                 public Nexus health
GET  /api/me                 Discord session discovery
GET  /api/products           authenticated product catalog
GET  /api/openapi            authenticated OpenAPI document
GET  /api/status             authenticated system status
GET  /api/live               authenticated live snapshot
GET  /api/live/stream        authenticated SSE stream
GET  /api/intelligence       authenticated analytics
GET  /api/sentinel           authenticated security snapshot
GET  /api/network/summary    authenticated network state
GET  /api/companion          authenticated Companion data
GET  /api/creators           authenticated creator campaigns

No public API keys are advertised

The current production contract does not expose the fictional per-guild API-key flow previously described on this page. Browser sessions use Nexus authentication instead.

No signed webhook contract is advertised

This page no longer claims an HMAC webhook product because that external webhook API is not part of the current native Nexus route contract.

Open the current Kingdom Core stack

Add the Discord application, preview the current /setup3 layout before applying it, and use the production Nexus for authenticated web operations.

Add Kingdom Core Current setup Download Nexus