Skip to main content

​
Check these first

Onboarding troubleshooting

Diagnose MCP access, agent behavior, workflow trials, and missing replies step by step.

Host status

Timestamped probe results. Compare the checked date with your request; this report is context rather than a live diagnosis.

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. Include the failing step and observed result so we can check the guide or underlying service contract.

​
Report an API problem

Include the details below so the team can reproduce the failure. Remove API keys, authorization headers and customer data before sharing a request or response.
If a documentation example fails, include the step number and any changes you made to it. For a timeout, say whether a later read showed that the operation completed. The error guide shows where each service puts its error code and request identifier.

​
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.
Last modified on September 20, 2026