OpenRouter Credits Explained
Quick Answer
OpenRouter credits are a prepaid balance used for API inference across multiple models and providers. Each request deducts from your balance based on the model's pricing. Credits can be confusing because different models charge differently, and usage may not always match expectations. Understanding how credits work helps you plan budgets and avoid unexpected charges.
Who This Is For
This guide is for developers using OpenRouter to access multiple AI models through a single API. If you're trying to understand why your credit balance changes unexpectedly, or if you want to plan costs across different models and providers, this guide will help.
What Cost Unit Matters
OpenRouter uses credit as the primary cost unit. Credits are purchased in packages and deducted based on per-request pricing set by each model provider. Some key points:
- Different models have different credit costs per request
- Some providers charge per token, others per request
- Longer contexts or larger outputs may cost more credits
- Some models offer free tiers or trial credits
What Credits Mean
Credits on OpenRouter represent prepaid purchasing power for API inference. Unlike a monthly billing cycle, credits are deducted immediately when you make a request. The rate at which credits are deducted depends on:
- The specific model being used
- The input and output token count
- Any provider-specific pricing adjustments
- Whether the model has volume discounts
What Usage Means
Usage refers to your API activity—each request you make. OpenRouter tracks:
- Total requests — Number of API calls made
- Tokens used — Input and output token counts
- Credits spent — Total credit deduction
- Per-model breakdown — Which models you're using most
How to Check Credits and Usage
To monitor your OpenRouter credits and usage:
- Log into your OpenRouter account dashboard
- Navigate to the Credits or Usage section
- Review the current balance and recent transactions
- Check per-model usage if available
- Set up usage alerts if the platform supports it
Why Credits May Not Match Expectations
Several factors can cause credit usage to differ from initial estimates:
- Provider pricing changes — Model providers may adjust pricing
- Token count differences — Actual tokens may differ from estimates
- System prompts — Some models include hidden context
- Caching behavior — Some requests may be cached, reducing costs
- Failed requests — Some providers may charge for failed requests
No Credits / Error Cases
Common error scenarios and their meanings:
- 401 Unauthorized — Invalid or expired API key
- 403 Forbidden — Insufficient credits or permissions
- 404 Model Not Found — Model unavailable or discontinued
- 429 Rate Limited — Too many requests, wait and retry
- Insufficient Credits — Balance too low for the request
Small Prepaid Test Checklist
Before scaling your OpenRouter usage:
- Purchase a small credit package to start
- Make a few test requests with different models
- Record the request_id for each test
- Compare actual credit deduction vs. estimated cost
- Review the provider dashboard for usage details
- Scale gradually while monitoring credit balance
Logs / Usage / Request ID Checklist
When reviewing OpenRouter usage:
- Save request_id for every API call
- Check tokens_in and tokens_out per request
- Review the OpenRouter usage dashboard regularly
- Compare your local logs against the dashboard
- Flag any discrepancies for investigation
OpenRouter credit usage can feel confusing when model routing, cached tokens, provider policy or failed requests affect what you expected to see. Use the billing transparency guide if you need a focused checklist for reconciling logs, request IDs and dashboard records.
Related Guides
OpenAI API Credits
Learn more about this topic
OpenAI API Billing
Learn more about this topic
OpenAI API Usage
Learn more about this topic
API Billing Mismatch
Learn more about this topic
Billing Transparency
Learn more about this topic
OpenRouter credits are a prepaid balance used for API inference across multiple AI models. Each request deducts credits based on the model's pricing. Different models charge differently per token or per request. Usage tracking requires checking the OpenRouter dashboard, saving request IDs, and comparing logs against actual credit deduction. Common errors include 401 (invalid key), 403 (insufficient credits), 404 (model not found), and 429 (rate limit). This guide is educational; check live OpenRouter pricing before scaling. Test with a small credit balance to verify cost expectations.
Frequently Asked Questions
How do OpenRouter credits work?
OpenRouter credits are a prepaid balance purchased in packages. Each API request deducts from your balance based on the model's pricing. Different models have different per-request or per-token costs. Credits do not expire but cannot be refunded in most cases.
Why is my credit usage higher than expected?
Several factors can cause this: actual token counts may differ from estimates, system prompts add hidden context, provider pricing may have changed, or failed requests may have been charged. Review your usage dashboard for a detailed breakdown by model.
How can I check my OpenRouter usage?
Log into your OpenRouter account and navigate to the Usage or Credits section. You can see your current balance, recent transactions, and per-model breakdown. Some integrations may also support API-based usage queries.
What happens when I run out of credits?
When your balance is insufficient for a request, you'll receive a 403 Forbidden or insufficient credits error. Requests will not be processed until you purchase more credits. Consider setting up balance alerts to avoid interruptions.
Ready to start?
Create an API key with $1 trial credit and explore live model pricing.