Simple usage pricing
500 API requests per day are free with no key required. Beyond that, create an account, add credit, and pay only for what you use.
Usage Model
Free first, then metered
No monthly tiers and no bundled plans. You pay only for requests above the free allowance.
| Mode | Limit / Price | Notes |
|---|---|---|
| Anonymous usage (no key) | 500 requests / day | Free. Good for testing and low-volume use. |
| Registered API usage | $0.50 / 1,000 queries | $0.0005 per query, deducted from account credit. |
Account requirement for paid usage: when you exceed the free daily allowance, create an API account with name, email, and password, then add credit.
Step 01
Start free
Send requests without an API key and use up to 500 requests/day at no cost.
Step 02
Create account
For higher usage, register with name, email, and password, then generate an API key.
Step 03
Add credit
Top up account credit and continue usage at $0.0005 per query.
FAQ
Common questions
Do I need to create an account?
Not for the first 500 requests/day. Account registration is only required when you want to go beyond the free daily allowance.
How does billing work?
Billing is usage-based: $0.50 per 1,000 queries ($0.0005 each). Charges are deducted from your account credit balance.
What happens when I hit my daily limit?
Anonymous requests above 500/day return HTTP 429 with a
anonymous_quota_exceeded error. To continue immediately, create an API account, add credit, and use a key.Is my query content logged?
No. We store only daily request counts per API key. We do not store query content, requester IP addresses, or response payloads. See our privacy policy for full details.
Can I use multiple API keys?
Yes. You can create multiple keys under the same account to separate applications, environments, or clients.
What information is required for paid usage?
A name, email, and password are required to create a secure account. Name and email are used for account communications and billing notices. We do not require identity documents.
Is the API available over HTTPS only?
Yes. All API endpoints require HTTPS. Plain HTTP requests are rejected. API keys should be treated as secrets and never embedded in client-side code or public repositories.