Reference
These pages are not meant to be read through. They are what you open with an editor already in front of you: a header whose exact value domain you forgot, a code you just got back, a field you need the type of, an endpoint whose credential you are unsure about.
Four tables cover everything you will look up.
What’s here
Section titled “What’s here”| Page | When you need it | What it solves |
|---|---|---|
| Provider Routing Headers | You are setting or debugging routing, price caps, or a trust tier | Gives all eight X-0G-Provider-* request headers with value domain, default, and the error each bad value produces, plus Authorization and every response header the Router returns |
| Error Codes | A call failed and you need to know what the code means and whether to retry | The full HTTP status by type by code table, a retryability matrix, and why the two 503s are different problems |
| Model Catalog | You are choosing a model in code or parsing the catalog | Field-by-field schemas for GET /v1/models and GET /v1/providers, including verifiability and how it maps to trust tiers |
| API Endpoints and Authentication | You are wiring a new endpoint and need to know which key it takes | Every endpoint with method and credential, the sk- versus mk- split, scopes, and the key lifecycle |
Where to start
Section titled “Where to start”Pick by what you already have in hand. Holding an error code, go to Error Codes. Trying to control which provider serves a request, go to Provider Routing Headers. Choosing or filtering models, go to Model Catalog. Unsure whether an endpoint wants an API key or a management key, go to API Endpoints and Authentication.
These pages tell you what something is. If your question is what to do about a symptom, the fix-oriented version lives in Troubleshooting.
Related
Section titled “Related”- Troubleshooting — symptom, cause, confirmation, fix.
- Trust Modes — what the trust tier values in these tables actually guarantee.
- Glossary — definitions for the terms these tables use.