API reference
Gateway
The gateway answers these routes itself. Everything else under /v1/<service>/ is forwarded to a service.
| Route | Credential | What it returns |
|---|---|---|
GET /v1/status | none | Live state of each service. |
GET /v1/whoami | any | The verified caller. |
GET /v1/usage | signed-in session | Usage for your organization. |
GET /v1/errors | none | Every error code the gateway emits. |
GET /v1/openapi.json | none | The operations this gateway serves. |
Status
curl "https://os.one.ml/api/v1/status"{
"object": "gateway_status",
"checked_at": "2026-10-20T06:52:00.991Z",
"cache_ttl_seconds": 30,
"services": [
{ "service": "auto", "state": "up", "http_status": 200, "latency_ms": 127 },
{ "service": "beacons", "state": "up", "http_status": 200, "latency_ms": 81 }
]
}Each service's state is from a live probe, cached for 30 seconds. genesis status prints the same table. The Status page reads it live.
Whoami
curl "https://os.one.ml/api/v1/whoami" -H "Authorization: Bearer $GENESIS_API_KEY"{
"object": "principal",
"kind": "api_key",
"org": "o_01M4RYY608B21SF83WXTJD5E9D",
"principal": "api_key_01M5BNSJZMXBX0XF4F6DF1R8YG",
"scopes": ["hives:read", "hives:write"]
}kind is api_key, m2m_token or bridge_session (a signed-in session). genesis whoami prints the same.
Usage
GET /v1/usage returns usage for the caller's own organization, optionally for one service (?service=hives). It needs a signed-in session with genesis.usage.read; an API key gets 403 SCOPE_MISSING. Organization-wide usage is also in the Console.
Errors and OpenAPI
curl "https://os.one.ml/api/v1/errors"
curl "https://os.one.ml/api/v1/openapi.json"/v1/errors is the catalog behind every gateway error; it is rendered at Error codes. /v1/openapi.json lists the operations this gateway serves right now; the full document with descriptions and schemas ships as @lifesi/genesis/spec.json.
One Superintelligence, Inc. · Built from Genesis 0.1.12 and the live gateway on 2026-10-20. Support