Integrations
Integration has one rule: point the base URL at the Router and use an sk- key. The Router serves the OpenAI API, so anything that lets you configure a custom OpenAI-compatible endpoint already works — there is no plugin to install and no adapter to write. These pages cover where each kind of tool hides those two settings, and what the tool does to 0G-specific fields on the way through.
What’s here
Section titled “What’s here”| Page | When you need it | What it solves |
|---|---|---|
| Coding agents | You are configuring an editor or coding agent to run against the Router | Where these tools take a custom endpoint, picking a model that supports tool calling, and keeping the key out of the repository |
Where to start
Section titled “Where to start”Start at Coding agents — it covers editors, agents, and framework wrappers alike, because they all reduce to the same three settings. Whichever you are wiring up, run the Quickstart first and confirm a plain request succeeds with the same key. It takes a minute and removes a variable: when a third-party tool then fails, you know the problem is its configuration and not your credentials or balance.
One thing to expect from framework code: typed libraries normalize responses and usually discard fields the OpenAI schema does not define, including the x_0g_trace block that carries the request ID, the serving provider, and the cost. Trust mode survives, because it travels in a header. When you need the cost or verification data, see the framework section in Coding agents.
Related
Section titled “Related”- Migrate from OpenAI or Anthropic — the same base-URL swap applied to code you already have.
- Provider routing headers — every header you may want your framework to send.
- Model catalog — the identifiers and capability fields to configure a tool against.