Plans and billing
This page covers plans, the daily quota, and payments. The API fields that a plan unlocks are in the API reference.
Plans
An organisation with no subscription is on the free tier.
| Free tier | BLAPI-30KPM | BLAPI-150KPM | BLAPI-500KPM | BLAPI-1MPM | |
|---|---|---|---|---|---|
| Price | US$0 | US$20 per month | US$50 per month | US$100 per month | US$200 per month |
| Lookups per month | — | 30,000 | 150,000 | 500,000 | 1,000,000 included |
| Daily limit | 10 | 1,000 | 5,000 | 10,000 | No fixed daily limit |
| Prepaid credit packs | No | No | No | No | Yes |
| Data | Production data | Production data | Production data | Production data | Production data |
meta.longer_bin_available | No | No | Yes | Yes | Yes |
| Batch lookup and Batch CSV | No | No | No | Yes | Yes |
| Support | Email, 1 business day | Email, 1 business day | Email, 1 business day | Priority, 8 hours | Priority, 8 hours |
| Subscribe | — | Billing page | Billing page | Billing page | Billing page |
A higher plan includes the features of the plans below it. On BLAPI-30KPM to BLAPI-500KPM, there is no charge for use above the daily limit. Requests stop when the organisation reaches the limit. BLAPI-1MPM uses a monthly allowance instead of a daily limit. See BLAPI-1MPM.
Some older pages used the names Basic, Standard and Pro. These are BLAPI-30KPM, BLAPI-150KPM and BLAPI-500KPM.
A test-mode organisation can use every plan feature before it pays. The data is mock data. The test-mode daily limit is 500 lookups.
If you need more than 10,000 requests each day, see BLAPI-1MPM.
Free tier
- The limit is 10 lookups each day.
- The data is the same production data as a paid plan.
- The dashboard is available.
- You do not need a payment card.
When the 10 lookups are used, the API returns HTTP 429 and QUOTA_EXCEEDED. The body includes upgrade_url. That URL opens the Billing page for the organisation.
Daily quota
This section applies to the free tier and BLAPI-30KPM to BLAPI-500KPM. BLAPI-1MPM has no fixed daily limit; see BLAPI-1MPM.
The plan name shows a monthly count. The API enforces a daily limit. Example: BLAPI-30KPM allows 1,000 requests each day, not 30,000 in one day.
- The counter resets at 00:00 UTC.
- Unused requests do not move to the next day.
- One single lookup uses one unit.
- Each BIN in a batch request uses one unit.
- Each data row in a Batch CSV file uses one unit.
- All API keys in one organisation share one quota.
When the count for the current UTC day reaches the daily limit, the API returns:
{
"error": "QUOTA_EXCEEDED",
"message": "Daily request quota exceeded"
}
The HTTP status is 429. On the free tier, the body also includes upgrade_url.
If a batch or a CSV file is larger than the remaining quota, the API uses no quota. See Batch lookups.
After an upgrade, the new daily limit applies immediately. Lookups from earlier in the same day still count.
Rate limits
No plan sets a fixed limit on requests per second. On the free tier and BLAPI-30KPM to BLAPI-500KPM, the daily quota is the plan limit. BLAPI-1MPM has no fixed daily quota. On every plan, technical capacity and acceptable-use limits still apply. If you plan to send sustained high-throughput traffic, contact sales first.
Quota headers
Each success response and each 429 response includes:
| Header | Meaning |
|---|---|
X-Quota-Limit | The daily limit. |
X-Quota-Remaining | The units that remain today. |
X-Quota-Reset | The next reset, as a Unix timestamp in seconds. |
On BLAPI-1MPM, the same headers describe the billing period, and X-Credits-Remaining is added. See BLAPI-1MPM quota headers.
When a single lookup returns 429, X-Quota-Remaining is 0. When a batch is rejected because it does not fit, X-Quota-Remaining is the real remainder.
You can also read Remaining on the dashboard home page.
Quota emails
BINLookupAPI sends two emails:
| Subject | When |
|---|---|
[Organisation] has used 80% of today's API quota | Usage reaches 80% of the daily limit. |
[Organisation] has reached its daily API limit | Usage reaches the daily limit. |
Owners and billing managers receive the emails. Each email is sent at most once per day. BLAPI-1MPM has its own emails; see BLAPI-1MPM emails and banners. The sender is noreply@binlookupapi.com. You cannot turn these emails off.
Subscribe to a plan
Only an owner or a billing manager can subscribe. See Roles.
- Open Billing.
- Select a plan.
- Complete the payment form.
- Return to the dashboard.
The new daily limit is active immediately. Payments use Stripe. BINLookupAPI does not store your card details.
You can add a tax ID or VAT number on the payment form. You can also add it later in the customer portal.
If the Billing page still shows the free tier after payment, wait one minute and refresh the page. Confirm that you are in the correct organisation. See Troubleshooting.
Promotion codes
- Open Billing.
- Select a plan.
- On the payment form, select Add promotion code.
- Enter the code and complete the payment.
If the code fails, check that it has not expired. If it still fails, contact support.
Change your plan
- Open Billing.
- Select Change Plan.
- Select the new plan in the customer portal.
- Confirm the change.
| Change | When it is active | Payment |
|---|---|---|
| Upgrade | Immediately | The difference for the rest of the current period is charged. |
| Downgrade | At the start of the next billing period | The next invoice uses the new price. |
After an upgrade, the new daily limit applies immediately. Earlier requests from the same day still count. After a downgrade, the current limit continues until the next billing period.
An upgrade to BLAPI-1MPM starts a new allowance of 1,000,000 included lookups for the rest of the current billing period. Lookups from the daily plan do not count against it. After a downgrade from BLAPI-1MPM, unused prepaid credits are paused. See Prepaid credits.
Cancel a subscription
- Open Billing.
- Select Manage billing.
- In the customer portal, select Cancel subscription.
- Confirm the cancellation.
The plan continues until the end of the current billing period. The Billing page shows Cancels at period end. After that time, the organisation returns to the free tier. API keys still work, with a limit of 10 lookups each day.
Invoices and payment methods
Only an owner or a billing manager can open the customer portal.
- Open Billing.
- Select Manage billing.
In the portal you can:
- Download invoices and receipts.
- Change the payment method.
- Change the billing address.
- Add or change a tax ID or VAT number.
Payment problems
The last payment failed
The banner text is We couldn't process your last payment. Stripe tries the payment again, up to 10 times over 30 days. The plan limits stay active during that time.
- Select Update your payment method in the banner.
- Enter a valid payment method.
The subscription has lapsed
The banner text is Your subscription has lapsed. Every payment attempt failed. The organisation is on the free tier, with 10 lookups each day.
- Select Update your payment method in the banner.
- Enter a valid payment method.
- Subscribe again.
Other banners are on the dashboard page.
BLAPI-1MPM
BLAPI-1MPM is for organisations that need more than BLAPI-500KPM allows. It costs US$200 per month and includes every BLAPI-500KPM feature: meta.longer_bin_available, batch lookup, Batch CSV, priority support and a contract SLA for uptime. It also gives access to discounted prepaid credit packs.
Subscribe to BLAPI-1MPM on the Billing page, the same way as the other plans. See Subscribe to a plan.
Monthly allowance
BLAPI-30KPM, BLAPI-150KPM and BLAPI-500KPM enforce a daily limit. BLAPI-1MPM enforces a monthly allowance instead.
| BLAPI-30KPM to BLAPI-500KPM | BLAPI-1MPM | |
|---|---|---|
| Plan limit | Daily limit, resets at 00:00 UTC | 1,000,000 lookups per billing period |
| Unused lookups | Do not move to the next day | Do not roll over to the next period |
| Fixed daily limit | Yes | No |
| Additional lookups | Upgrade the plan | Prepaid credit packs |
The billing period is the monthly period of your subscription in Stripe, not a calendar month. There is no reset at 00:00 UTC on BLAPI-1MPM.
- The 1,000,000 included lookups are used first.
- Then prepaid credits are used, from the pack that expires first.
- When the included lookups and all prepaid credits are used, the API returns HTTP 429 and
QUOTA_EXCEEDED.
{
"error": "QUOTA_EXCEEDED",
"message": "Included lookups for this billing period and prepaid credits are used up. Buy a credit pack at https://app.binlookupapi.com/organisation/org_.../billing or wait for the next billing period."
}
Requests work again at the start of the next billing period, or as soon as a prepaid credit pack purchase completes.
A batch request or a Batch CSV file can use the remaining included lookups and credits together. If the batch is larger than both together, the API rejects it and uses nothing.
While Stripe retries a failed payment, the plan and its credits keep working.
Technical capacity and acceptable-use limits still apply to BLAPI-1MPM. Each BIN in a single lookup, a batch request or a Batch CSV file uses one lookup, the same as on other plans.
Prepaid credits
BLAPI-1MPM customers can buy lookups upfront in packs. Larger packs cost less per lookup.
| Credits | One-time price | Cost per 1M | Cost per lookup | Discount |
|---|---|---|---|---|
| 1M | US$200 | US$200 | US$0.000200 | — |
| 5M | US$850 | US$170 | US$0.000170 | 15% |
| 10M | US$1,500 | US$150 | US$0.000150 | 25% |
| 25M | US$3,000 | US$120 | US$0.000120 | 40% |
| 50M | US$5,000 | US$100 | US$0.000100 | 50% |
| 100M | US$8,000 | US$80 | US$0.000080 | 60% |
| 250M | US$15,000 | US$60 | US$0.000060 | 70% |
| 500M | US$25,000 | US$50 | US$0.000050 | 75% |
- Credits are in addition to the 1,000,000 included lookups.
- Included lookups are used first. Credits are used only after the period’s included lookups run out.
- Credits do not reset monthly. Each pack expires 12 months after purchase. When you have more than one pack, the pack that expires first is used first.
- Credits can be used only while the organisation is on BLAPI-1MPM. After a downgrade or a cancellation, unused credits are paused until they expire. They work again if the organisation returns to BLAPI-1MPM.
- If a pack is refunded, its unused credits are removed. Credits already used are not affected.
- Nothing is charged automatically. Automatic top-ups are planned.
Buy a credit pack
Only an owner or a billing manager can buy a pack, and the organisation must have an active BLAPI-1MPM subscription.
- Open Billing.
- In Prepaid Credits, select a pack.
- Complete the payment form.
The credits are added when Stripe confirms the payment, usually within seconds. Prepaid Credits on the Billing page shows the usable balance, and each pack’s purchase date, remaining credits, expiry and status.
BLAPI-1MPM quota headers
Each success response and each 429 response includes:
| Header | Meaning on BLAPI-1MPM |
|---|---|
X-Quota-Limit | The included lookups for the billing period: 1000000. |
X-Quota-Remaining | The included lookups that remain in this billing period. |
X-Quota-Reset | The end of the billing period, as a Unix timestamp in seconds. |
X-Credits-Remaining | The prepaid credits that you can use now. |
X-Quota-Limit: 1000000
X-Quota-Remaining: 0
X-Quota-Reset: 1793966400
X-Credits-Remaining: 4999120
X-Credits-Remaining is sent only on BLAPI-1MPM. When a single lookup returns 429, every remaining value is 0. When a batch is rejected because it does not fit, the headers show the real remainders.
BLAPI-1MPM emails and banners
On BLAPI-1MPM, the home page shows Included This Period, Resets and Prepaid Credits in place of the daily statistics.
Owners and billing managers receive these emails. Each email is sent at most once per billing period.
| Subject | When |
|---|---|
[Organisation] has used 80% of this period's included lookups | Usage reaches 80% of the included lookups. |
[Organisation] has used all of its lookups for this billing period | The included lookups and all prepaid credits are used. |
The dashboard banners for BLAPI-1MPM are listed on the dashboard page.