Nebius Token Factory
Open models on Nebius. Bring your own key; nothing is billed by us.
What the harness already knows
| Provider id | nebius |
| Base URL | https://api.tokenfactory.nebius.com/v1 |
| Protocol | OpenAI-compatible chat completions |
| API key | NEBIUS_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 NEBIUS_API_KEY="..."Keys are issued by Nebius Token Factory — where to get one.
Models on Nebius Token Factory
The newest models Nebius Token Factory serves that can call tools, from the models.dev snapshot OHarness ships. The harness also asks the endpoint for its live list, so a model released after this snapshot still appears in the picker.
| Model id | Context / output | $/M in / cached / out | Reasoning |
|---|---|---|---|
zai-org/GLM-5.3-Flash | 1.02M / 1.02M | 0.15 / 0.15 / 0.5 | Yes |
nvidia/Nemotron-3_5-Lightning | 1.05M / 1.05M | 0.06 / 0.06 / 0.24 | Yes |
deepseek-ai/DeepSeek-V4-Flash-0731 | 1.02M / 1.02M | 0.14 / 0.14 / 0.28 | Yes |
moonshotai/Kimi-K3 | 1.05M / 8K | 3 / 3 / 15 | Yes |
zai-org/GLM-5.2 | 1.05M / 1.05M | 1.4 / — / 4.4 | Yes |
moonshotai/Kimi-K2.7-Code | 262K / 8K | 0.95 / — / 4 | Yes |
nvidia/Nemotron-3-Ultra-550b-a55b | 1.05M / 1.05M | 1 / 1 / 3 | Yes |
MiniMaxAI/MiniMax-M3 | 1.05M / 1.05M | 0.3 / — / 1.2 | Yes |
deepseek-ai/DeepSeek-V4-Pro | 1.05M / 1.05M | 1.75 / 0.15 / 3.5 | Yes |
nvidia/nemotron-3-super-120b-a12b | 262K / 33K | 0.3 / — / 0.9 | Yes |
List prices in USD per million tokens, read from models.dev on 2026-09-19. Nebius Token Factory changes its prices and models; its own pricing page is the authority. Start a session on the newest:
oharness -m nebius/zai-org/GLM-5.3-FlashPointing 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": {
"nebius": {
"baseUrl": "https://api.tokenfactory.nebius.com/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.