API credits are consumed based on results returned — not requests made. You're charged for what you actually receive, not for making the call itself.
Profile & Company Fetch
Every profile or company record returned by the API costs 1 credit. If you fetch 10 profiles in a single request and all 10 are returned successfully, that's 10 credits. If your request returns 0 results (e.g., no match found), no credits are charged.
Network Mapper
The Network Mapper charges 1 credit per connection found. If a mapping run discovers 47 connections for a given person or company, that's 47 credits.
Search queries are always free
Running a search to find profiles or companies before fetching them doesn't consume credits — only the fetch itself does.
Credits only count on success
If a request fails (anything other than a 200 response), no credits are deducted.
A few examples:
Action | Credits Used |
Search for "software engineers in Warsaw" | 0 |
Fetch 1 profile | 1 |
Fetch 25 profiles in one request | 25 |
Fetch 5 companies | 5 |
Network Mapper run that finds 120 connections | 120 |
Failed API request (non-200 response) | 0 |
Included credits and overages
Each plan includes a monthly credit allowance that resets at the start of every billing cycle — credits don't roll over. Once you've used your included credits, additional usage is billed at your plan's overage rate.
For example: on the Premium 50 plan ($99/mo, 1,000 credits included at $0.10/credit), if you use 1,400 credits in a month, your invoice will be $99 + 400 × $0.10 = $139.