BYOK & NOME Credits

NOME Code has two billing lanes. NOME Credits is the managed lane: subscribe and NOME negotiates with providers, handles rate limiting and failover, and meters usage across models. BYOK (Bring Your Own Keys) is the direct lane: connect your own provider API keys and pay the provider while NOME provides the interface, memory, routing, and receipts.

Add provider API keys in NOME's account/keys surface (or native settings). Each key is validated on entry with a real-time provider status check and stored with encrypted persistence. Supported providers include the major frontier models — OpenAI, Anthropic, Google/Vertex, DeepSeek, and xAI — plus any OpenAI-compatible endpoint for custom or self-hosted models.

Credits are consumed by hosted inference on the managed lane. Your credit summary shows total balance, available credits, usage this period, and any included monthly allocation. NOME normalizes token counts across providers so cost is comparable regardless of which model ran.

Two kinds of work consume no NOME credits: turns run on a local model on your host, and turns run through a provider seat you signed into yourself (those bill against your own provider subscription, recorded as a provider-subscription cost lane). BYOK inference is paid to the provider, not in NOME credits.

BYOK keys are stored encrypted and are never written into receipts — secret-shaped values are scrubbed before anything is logged. Provider seat sign-ins are never copied by NOME at all; they live in each provider CLI's own config on the machine where you signed in. NOME cloud does not store subscription tokens. See Security.