OttoPort
Your own OttoPort key — GPT, Claude and Gemini behind one gateway. Bring your own key; nothing is billed by us.
Diese Seite ist auf Englisch geschrieben. Die Begriffe, die sie erklärt, werden auf Englisch gesucht, und ein übersetzter Fachbegriff ist ein anderer Begriff.
What the harness already knows
| Provider id | ottoport |
| Base URL | https://ottoport.ai/api/v1 |
| Protocol | OpenAI-compatible chat completions |
| API key | OTTOPORT_API_KEY |
| Model discovery | Yes — the model list is asked of the endpoint rather than shipped. |
Connecting it
The endpoint above is built in, so there is nothing to configure. Put the key in the environment and the provider appears in the model picker:
export OTTOPORT_API_KEY="..."Keys are issued by OttoPort — where to get one.
Worth knowing
Bring-your-own OttoPort account: the user makes an op- key in OttoPort's console and is billed there. Not the official plan — that is official, which happens to route through this gateway today but never hands the subscriber a key to it. The two lines above are the upstream gateway's, not any model's: it wants an Idempotency-Key on every completion and caps max_tokens at its own GATEWAY_MAX_OUTPUT_TOKENS — 4096 by default, and nothing in /models mentions either, so both have to be stated here. Raise the number in step with the deployment, or a shorter answer is the least of it: over the line is a 400, not a truncation.
Pointing it somewhere else
A regional host, a gateway, or a server of your own. Overrides in ~/.oharness/config.json are field level, so changing the endpoint does not mean restating the rest of the provider — this is the whole block, shown holding the default so the shape is clear:
{
"providers": {
"ottoport": {
"baseUrl": "https://ottoport.ai/api/v1"
}
}
}What you get either way
The same agent loop, the same tools, the same MCP servers and the same permission rules, whichever provider is underneath — and switching between them mid-session converts nothing, because history is never stored in a vendor’s shape. What an agent harness is covers why that is the hard part, and the providers reference covers the catalogue itself.