Check these first
Host status
Probed, with a checked date. If a host says being provisioned, a 503 is expected and not
yours to debug.
Errors across the engines
Every error envelope side by side, and the five families with what to do about each.
Which API am I calling?
The most common cause of a mystery 401 or 404 is the right key on the wrong engine.
API history
If a call that used to work stopped, the tab’s history page says what changed in the surface.
Ask a person
- Discord — the fastest path for build questions; the team and other builders are in the channel.
- Book time with the team — onboarding, architecture review, or anything commercial.
- Tell us when a page is wrong — say so in Discord with the URL; we treat “this page is wrong” as a bug report, and the docs are regenerated from the servers’ own contracts, so a fix usually lands the same day.
When money is involved
Billing follows the outcome model: outcomes can be disputed within 14 days, a dispute lands as a credit on your next invoice, and the ledger is visible in the billing portal — the process and the High-Value Action gate are documented in Billing.When you report an API problem, include the request id from the response (
request_id,
meta.requestId, or the correlation header, depending on the engine — the
errors page says which) and the timestamp. That turns a
mystery into a lookup.