Google Gemini
Gemini models, official API. Bring your own key; nothing is billed by us.
Esta página está escrita en inglés. Los términos que explica son los que se buscan en inglés, y un término técnico traducido es un término distinto.
What the harness already knows
| Provider id | google |
| Base URL | https://generativelanguage.googleapis.com/v1beta |
| Protocol | Google Gemini API |
| API key | GEMINI_API_KEY or GOOGLE_API_KEY |
| Model discovery | No — models come from the catalogue and from what you configure. |
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 GEMINI_API_KEY="..."Keys are issued by Google Gemini — where to get one.
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": {
"google": {
"baseUrl": "https://generativelanguage.googleapis.com/v1beta"
}
}
}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.