Providers

A provider is somewhere models come from. You add one, paste the key you already have with that service, and nemu holds it from then on.

​

Automatic or custom

Automatic is the default and the right choice for a known service. Pick it from the models.dev catalog and nemu already knows its address, the protocol it speaks and the models it offers, and keeps context windows and pricing current without you maintaining them. Custom is for anything the catalog does not know: a local server, a private deployment, a proxy of your own. You supply the address and say whether it speaks the OpenAI or the Anthropic protocol.

​

Fields

The name becomes the first half of every model’s public name, so openrouter gives you openrouter/something. Keep it lowercase, which is what the form does for you.

​

User agent

Some providers only answer clients they recognise. The picker carries presets for Claude Code, Cline, Roo Code, Kilo Code, the Codex CLI, OpenCode and Cursor, or you can type your own. It is only sent when your own request does not already carry one.

​

Where the key goes

Not into the database. It is encrypted with a key derived for your account alone, stored in a secrets vault, and the database keeps only a pointer. Deleting a provider destroys the secret. Rotating one seals the new key before destroying the old.

​

Base URL safety

A custom address has to be https, and it is resolved before being accepted. Private and loopback ranges are rejected, so a provider cannot be pointed at something inside our network.

​

Priority

Priority orders your provider list, which also orders GET /v1/models. It does not choose between providers and there is no failover. A request names one model, and that model belongs to exactly one provider. If you want fallback behaviour, that is what workflows are for.

​

Limits

Providers count against your plan while they are enabled, so disabling one frees the slot without deleting your configuration.