every capability of https://api.cognitum.one, from simple to esoteric
> boot cognitum.explorer
[ ok ]  nitro proxy .......... online  (bring-your-own key — server holds none; forwarded per-request)
[ ok ]  target ............... https://api.cognitum.one
[warn]  browser cors ......... none upstream → bypassed via same-origin proxy
[warn]  api key .............. none on server → paste your cog_ key below
[ ok ]  surface .............. 116 endpoints across 4 tiers
active keynone — paste your cog_ key to begin
▓ featured— the capabilities worth showing off
routing
streaming
tool use
embeddings
multi-protocol
bake-off
spec bake-off
human-in-loop
usage
spaces / digital twin
routing— difficulty-aware tier selection + semantic cache
▓ full surface— every gateway route, tiered by complexity
SIMPLE
MODERATE
COMPLEX
ESOTERIC
ping the surface — no spend · LIVE callable with this key · LOCKED needs a scope this key lacks (returns 401/403)

// Meta

GET/v1/health— HealthLIVE▸
Liveness + version + endpoint map. No auth.
scope:public
GET/v1/models— List modelsLIVE▸
The four virtual models: cognitum-auto / -low / -mid / -high.
scope:public
GET/v1/catalog— Product catalogLIVE▸
Public product/pricing catalog. No auth.
scope:public
GET/v1/openapi— OpenAPI specLIVE▸
The machine-readable spec the gateway serves.
scope:public

// Auth

GET/v1/verify— Verify keyLIVE▸
Introspect the current key: scopes, account, active/expiry.
scope:public · Read-only key check — no body; the key rides in the header. Great first call.
GET/v1/whoami— WhoamiLIVE▸
Introspect the calling credential — account id, credential type, isolation.
scope:public · Account id comes only from the verified credential — no header/param can select another tenant.
POST/v1/verify— Verify key (POST)LIVE▸
Same read-only key check as GET /v1/verify, for callers whose proxy strips headers on GET.
scope:public

// Completions

POST/v1/messages/count_tokens— Count tokensLIVE▸
Token accounting for a message payload — no generation, no spend.
scope:completions:*