Help

Something failed, a term does not mean what you assumed, or you need to reach a person. This group is those three exits.

What’s here

Page	When you need it	What it solves
Troubleshooting	A call is failing and you want it working again	Organized by what you see rather than by status code: each entry gives the likely cause, a way to confirm it, and the fix — auth failures, balance and scope errors, rate limits, both `503`s, and broken streams
Glossary	A term in a doc, a field, or an error message is unfamiliar or ambiguous	Defines the vocabulary as this API uses it — trust modes, TeeML and TeeTLS, providers, credentials, response fields — and maps loose or outdated wording onto the fields that actually exist
Contact and feedback	Nothing here explains it, or the docs themselves are wrong	Sets out what to include so a report can be answered on the first reply, and what never to paste anywhere

Where to start

Go to Troubleshooting first and match the symptom — most failures have a known cause and a definite fix. If you find your symptom but a term in the explanation is unclear, Glossary defines it. Only when neither resolves it should you move to Contact and feedback, and bring the request_id with you.

Every error response carries request_id at the top level, next to the error object. It is the only handle that identifies one specific request, so log it before you change anything.

Error Codes — the full status, type, and code table behind these symptoms.
Trust Modes — for the 503 that means no provider could meet the tier you asked for.
Console — balance, keys, and usage.