Keep your provider contracts. Take the platform anyway.
Add your own provider keys and Multigrid routes through them — your rates, your billing relationship. We charge nothing on that traffic and it does not touch your credit balance.
- 0%
- fee on BYOK traffic
- 5
- providers you can key
- Write-only
- keys are never returned
- Mixed
- BYOK and credits together
What it actually does
Your keys go first
When a model can be served on your key and on ours, yours wins. You are only charged when there was no key of yours that could serve it.
Keys you cannot read back
Encrypted with AES-256-GCM under a master key held only by the server, with a fresh IV per key. Only the last four characters are stored in the clear, and the plaintext is never logged or returned to a client.
Spillover, not failure
If your key rate-limits, expires or is disabled, traffic falls through to Multigrid's own capacity instead of erroring. Every request records whether it was served on your key or ours.
Mix both models
Run one provider on your own contract and the rest on prepaid credit, in the same account, under the same routing rules.
Same platform, no asterisks
Routing, caching, guardrails, logging and CSV export behave identically on your keys. BYOK is not a degraded tier.
Counted separately
Usage reporting splits BYOK requests from charged ones, so you can see how much of your traffic never cost you anything here.
Fair questions
Why would you give up the percentage?
Because the routing, logging and cost controls are the product; reselling tokens is the commodity. Teams big enough to have their own provider contracts are exactly the teams that need this most, and we would rather have them on the platform than lose them over a margin.
Where exactly is my key stored?
As AES-256-GCM ciphertext in our database, decrypted in memory only to sign a request upstream. The master key comes from the server environment, not from the database, so a copy of the table alone is not enough to use the keys. We do not claim an HSM, because we do not use one.
What if my key expires?
The failure is recorded against the key and shown on the BYOK page, and affected traffic spills to pooled capacity rather than erroring — which means it starts costing credit until you fix it.
Can I start on credits and move to BYOK later?
Yes, and you can run both at once during the transition. Nothing about your presets or your logs changes.
Works with the rest of the platform
Name a model, name the ones to try if it cannot be served, and set which providers you prefer. Multigrid retries transient failures on each provider and moves down the list when it runs out of attempts.
Every request writes a row: model, provider, tokens, cost, latency, attempts, cache outcome and your own tags. No prompt text, no completion text — the schema has nowhere to put them.
Six rule types, evaluated inside the request path. A client that forgets to call them still gets them, and a rule can run in warn mode against real traffic before it is allowed to refuse anything.
Bring your own provider keys and pay us nothing for that traffic
Requests served on your own key are not charged and do not touch your credit balance. You still get the routing, the logging and the cost record.