What each API call costs
One credit per call on every endpoint but one, and almost nothing else is billed. This page is the whole of it, so you can work out what a run costs before you make it rather than after the invoice.
What each call costs
Credits start at $1.00 per 1,000 and drop to $0.90 per 1,000 from a million.
| Endpoint | Credits | What one call returns |
|---|---|---|
| ProfileGET /api/v1/profile | 1 | One professional profile with its full history and attributes. |
| CompanyGET /api/v1/company | 1 | One company with its firmographics. |
| PostsGET /api/v1/posts | 1 | One page of posts from a profile or a company. |
| Post commentsGET /api/v1/post/comments | 1 | One page of comments on a post. |
| Post reactionsGET /api/v1/post/reactions | 1 | One page of reactions on a post. |
| Profile reactionsGET /api/v1/profile/reactions | 1 | One page of reactions left by a profile. |
| Post engagementGET /api/v1/post/engagement | 2 | Comments and reactions on a post in one call. Two credits because it does the work of two. |
| SubscriptionGET /api/v1/subscription | Free | Your plan, balance and rate limit. Free, and never blocked when you are out of credits. |
What you are charged for
Only two outcomes consume credits: a successful call, and a not-found. Everything else is free, including our own failures.
| Response | Cost | Why |
|---|---|---|
| 200Success | Charged | The price of the endpoint you called, from the table above. |
| 404Not found | 1 credit | The record does not exist, or is not public. Establishing that costs more than returning a record, not less: a success answers on the first attempt, while an absence is only concluded once two independent sessions agree, across up to ten attempts. Always one credit, even on the two-credit engagement endpoint. |
| 400Invalid parameter | Free | A malformed URL or a missing parameter. Nothing was fetched. |
| 401 / 403Authentication | Free | A missing, wrong or revoked API key. |
| 402Out of credits | Free | Your balance is exhausted. Being out of credits never costs you a credit. |
| 429Rate limited | Free | You went over your requests per second. Retry after a short backoff. |
| 5xxOur fault | Free | A timeout, an upstream failure or capacity exhaustion on our side. You are never billed for our problems. |
Not-found billing starts on 1 October 2026 for existing accounts
Accounts opened before that date are not charged for not-found responses until then, so nothing about your current bill changes before 1 October 2026. Accounts opened from now on are charged from their first request.
Keeping track
- Check your balance from code. GET /api/v1/subscription returns your remaining credits and never costs anything. Usage is written back every 30 seconds, so leave that much headroom rather than pacing down to the last credit.
- Paging costs one call per page. The endpoints that paginate charge for each page you request, not for the whole timeline.
- Retries cost what they return. A retry after a 429 or a 5xx is free until it succeeds, because neither of those outcomes is billed.
Questions
- How many credits does one request cost?
- One credit for every endpoint except post engagement, which costs two because it does the work of two calls, and the subscription endpoint, which is free. There is no minimum, no rounding and no per-call surcharge on top.
- Are failed requests billed?
- Almost none of them. Invalid parameters, authentication errors, rate limiting, running out of credits and any failure on our side all cost nothing. The one exception is a not-found, which costs one credit because it is the more expensive answer to produce rather than the cheaper one.
- Why is a not-found charged?
- Because confirming an absence costs more than returning a record, not less. A successful lookup answers on the first attempt. A not-found is only concluded once two independent sessions agree the record is gone, and the request traverses up to ten attempts to reach that agreement. That verification is there to protect you: without it a login wall or a throttled session would be reported as a missing record, and you would act on a wrong answer. Confirming an absence is also a real result, and often the one a data hygiene job is looking for.
- When does not-found billing start?
- Accounts opened from 27 August 2026 onwards are charged from their first request. Accounts that already existed are not charged for not-found responses until 1 October 2026.
- Does pagination cost more?
- One credit per page you request, not per item returned and not for the whole timeline. If you only need the first page, you only pay for the first page.
- How do I check my remaining credits?
- Call the subscription endpoint. It is free, it is never blocked when you are out of credits, and it returns your balance, plan and rate limit. Usage is written back every 30 seconds, so leave that much headroom rather than pacing down to your last credit.
Try it with 1,000 free credits
No card. Enough to enrich a thousand records and see the meter move before you decide anything.