Teams that already have lab contracts

• Using existing contract prices and data agreements with a lab.
• One integration for those labs and for models without a contract.
• Fallback when a key hits its own rate limit or runs out of credit.
• Control over where traffic is allowed to go.

• Keys for any of 15 supported labs; requests for those labs' models run on your own accounts at the labs' official endpoints.
• The order is configurable: keys marked prioritized, then platform routes, then keys marked fallback.
• Use my keys only, set per lab, turns platform routes off for strict data boundaries.
• Models outside your contracts run on platform routes with the same BoostRail key.
• Keys are encrypted with AES-256-GCM, shown only by their last four characters, and every key change is audited.

1. Choose a BYOK plan; the free plan covers 1,000,000 requests a month for up to 3 labs.
2. Add your lab keys in the console and set their order.
3. Keep using one BoostRail API key in your application.

• BYOK covers models available on a supported lab's official API; other models run on platform routes only.
• When the monthly BYOK allowance runs out, requests use platform routes at platform prices until the 1st of the month (UTC); models that run only on your own key pause until then.
• Platform fallback needs a balance.

BYOK plans →Pricing and billing →All use cases →