Bring your own key, often shortened to BYOK, means an app uses an API credential from your own AI provider account. Instead of paying the app developer for a bundle of AI credits, you connect the app directly to a provider such as Google Gemini or OpenRouter. The provider measures the requests and applies its free allowance, prepaid balance, rate limits, and prices to you.
You can see and control the AI usage
With a provider account you can inspect usage in the provider dashboard, revoke one app’s key without changing another, and choose whether paid billing is enabled. A dedicated key makes the app recognizable in usage reports. OpenRouter keys can carry a dollar-denominated limit that resets daily, weekly, or monthly; a Gemini project can remain on its Free Tier until you explicitly upgrade it.
The provider bill is visible to you
AI models charge for the work they process, commonly by input and output tokens. BYOK lets the provider show that usage directly instead of hiding it inside an app-specific credit pack. This does not guarantee the lowest price: Hot Take uses Gemini Flash through both providers, and OpenRouter charges a commission when you top up its prepaid credits. OpenRouter’s benefit here is its consolidated billing and key-level spending controls, while Gemini is the direct route and may provide eligible use through its Free Tier.
Direct does not mean on-device
BYOK removes one middleman, not the network. In Hot Take, the selected image and caption prompt still leave the phone because Gemini Flash runs in a data center. They travel directly to Google or to OpenRouter and its selected model provider. That provider’s current privacy, retention, abuse-monitoring, and model-improvement terms matter. Do not use a cloud caption model for a photo you would not send under those terms.
The tradeoffs are real
You have to create and protect a secret key, provider quotas can interrupt generation, and provider changes can affect availability without an app update. You are also responsible for watching usage and revoking a leaked key. A careful BYOK app should store secrets in the system Keychain, explain exactly where requests go, provide a remove-key control, and fail clearly when the provider rejects a request.
A safe BYOK checklist
Create a separate key for each app. Start on a free tier or with a small prepaid balance. Set a key-level spending cap where available. Never paste the key into a support message or public screenshot. Review the provider dashboard after your first few requests. Revoke the key immediately if a phone, screenshot, or account is compromised. These habits turn BYOK from “bring your own bill” into useful control.
Hot Take follows that pattern: Gemini and OpenRouter are selectable, keys live in the iPhone Keychain, requests go directly to the selected provider, and there is no Hot Take login, subscription, credit ledger, or caption server.
FAQ
Is BYOK cheaper than an AI subscription?
It can be for light or irregular use when Gemini’s Free Tier covers the work, but BYOK is primarily about control and visibility, not a universal discount. Hot Take uses Gemini Flash through both providers, and OpenRouter’s credit top-up fee can make that route more expensive than Gemini direct. Compare the current total cost.
Can the app developer see a BYOK API key?
That depends on the app’s architecture. Hot Take stores the key locally in iOS Keychain and sends it only to the selected provider, so Underrated Software does not receive it. An app that routes requests through its own server may be able to see the key.
Is an API key the same as my Google or OpenRouter password?
No, but it is still a secret. It authorizes API use against your provider account or project. Anyone who obtains it may consume its quota or balance until you revoke it.
