BYOK for AI visibility tracking: provider keys, billing, and questions to ask
Some AI visibility tools run prompts on their own accounts and sell you credits. Others, including RankStacky, run prompts on API keys you bring. This guide covers how bring-your-own-key (BYOK) works, the trade-offs, and what to check before you paste a key into any tool.
Vendor credits vs your own keys
| Vendor-run credits | Bring your own key | |
|---|---|---|
| Setup | Nothing to configure | Create provider accounts and keys |
| Model choice | Whatever the vendor offers | Any model your key can access |
| Cost visibility | Credits bundled in the plan | Itemised on your provider bill |
| Spending control | Plan limits | Provider budgets and limits you set |
| Key management | None | You rotate and revoke keys |
Direct provider keys or an aggregator?
Direct keys(OpenAI, Anthropic, Google, Perplexity, and others) give you each provider's full model list and billing in that provider's dashboard. You manage one key and one bill per provider. Some features need extra setup: Claude keys need an Anthropic workspace, and web search can require a paid tier.
An aggregator such as OpenRouter gives many models behind one key and one bill, with credit limits in one place. Check that the specific models and web-search options you need are available through it.
RankStacky accepts keys for OpenAI, Claude, Gemini, Perplexity, Grok, DeepSeek, Qwen, Mistral, Kimi, and OpenRouter, plus a SerpApi key for Google AI Overviews and AI Mode. Setup steps are on the how it works page and in the FAQ.
Decision checklist
- Models: which engines do your buyers use, and can your key reach them with web search turned on?
- Token costs: estimate prompts × engines × markets × runs per month, then price that with each provider.
- Billing visibility: who in your company sees and approves the provider bill?
- Credential burden: how many keys will you rotate, and who owns them when people change roles?
- Security: how does the tool store keys, who can use them, and how do you delete them?
Questions to ask any BYOK vendor
- Are keys encrypted at rest, and with what?
- Is a saved key ever sent back to the browser or shown to other users?
- When exactly is a key used: only on runs I start or schedule?
- How do I delete a key, and does account deletion remove it?
- Which charges come from the provider, and which from the tool?
Security, cost, and data handling FAQ
What does BYOK mean in AI visibility tracking?
Bring your own key: the tool sends your tracking prompts to AI providers using API keys from your own provider accounts, instead of the vendor running prompts on its accounts and charging you credits.
Who pays for model usage with BYOK?
You do, directly. The provider bills your account for the tokens and any web-search fees each run uses. The tool's own subscription is a separate charge.
Where does RankStacky store my API keys?
Keys are encrypted with AES-GCM before they are saved in RankStacky's database. They are decrypted on the server only when a run you requested or scheduled needs them, and the app never sends a saved key back to your browser; it only shows that a key is saved.
Who can use my keys in RankStacky?
Keys belong to your user account. Runs use them only for your own requests and schedules.
How do I remove a key?
Delete it in RankStacky Settings. To be certain it can never be used again, also revoke or rotate it in the provider's dashboard.
How do I cap spending?
Set budgets or usage limits in each provider's billing dashboard, or use OpenRouter credit limits. Those limits apply no matter which tool uses the key.
More detail on how RankStacky handles data is in the privacy policy. Plan prices and allowances are on the pricing page. Last reviewed November 18, 2026.