Skip to content
Orbit Docs

BYOK

Published Updated

Also called Bring Your Own Key

What is BYOK?

BYOK (bring your own key) means using your own provider API key instead of a vendor’s pooled access. In Orbit, a key stored in the Vault sends that provider’s usage straight to your account and bypasses Sivants Credits.

Using your own API key (stored in the Vault) for a provider, instead of routing through Sivants infrastructure. Bypasses Sivants Credits entirely.

When you add a provider key (e.g., `FAL_KEY`, `ANTHROPIC_API_KEY`) to the Vault, Orbit calls the provider directly using your key. You're billed by the provider, not by Sivants. Without a key, the same operation routes through Sivants infrastructure and consumes Sivants Credits.

How it relates to Orbit

Orbit lets you configure an API key for a model tier instead of using a subscription sign-in. See Complexity Tiers & Routing for details.

When you would use it

You use BYOK when your provider relationship is cheaper than Sivants Credits, or when you want direct control of billing for a specific service.

Common operations

  • Using your own Anthropic subscription rather than Sivants Credits for premium model calls
  • Direct billing for high-volume image generation
  • Bypassing Sivants for any provider you already pay for

Frequently asked questions

Which providers support BYOK in Orbit?

Anthropic, OpenAI, Google, fal.ai, Recraft, ElevenLabs and others. Each provider you add a key for bypasses credits. See Credits & BYOK.

Are my keys sent to Sivants?

No. Keys live in Orbit’s local encrypted Vault and are never sent to Sivants. See The Vault.

Can I mix my own keys and credits?

Yes. Use your own key where you use a provider heavily, and credits for occasional tasks where a separate account is not worth setting up.

Related terms

Where this is taught

No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.