Resources

Support

Most problems can be pinned down in a minute with the request ID, the error code and the live status.

Diagnose a failing request

1. Check Status. A service that is down or degraded shows there first.
2. Read the error. Gateway errors carry a stable code and a docs_url; look the code up in Error codes. A 403 names the required_scope.
3. Check the credential. genesis whoami or GET /v1/whoami shows the organization, kind and scopes the gateway sees.
4. Check the operation's API key result. Its badge in the API reference says whether API keys passed it in the latest test run, or whether it needs a signed-in session.
5. Match the versions. Use the same version of @lifesi/genesis, @lifesi/genesis-cli and @lifesi/genesis-mcp, on Node.js 20.19 or later (tested on 20, 22 and 24).

What to include when you ask for help

• The request_id (the x-request-id header, or request_id in the error).
• The time, in UTC.
• The operation id or method and path, and the status you got.
• The error code and message, if any.
• The package versions (genesis --version), and your Node.js version.

Never include an API key or secret value. A request ID is enough for us to find the request.

One Superintelligence, Inc. · Built from Genesis 0.1.12 and the live gateway on 2026-10-20. Support