Credits and request limits
A credit is a billing unit. It is not a provider account, an API request, or an unconditional promise of source capacity.
Cost per result
| Data action | Credits per returned record |
|---|---|
| Sales Navigator people search | 1 |
| Full profile enrichment | 20 |
| Company enrichment | 1 |
| Profile posts or content search | 1 |
| Post comments or reactions | 1 |
A successful call returning no records uses zero customer credits. A failed run refunds its remaining reservation. Records with omitted optional fields are still returned records; design your quality checks around the fields your application needs.
Reserve, run, settle
Before work starts, the API reserves max_results × credits_per_record. If max_credits is set below that amount, the request is rejected before execution. This prevents a request from silently exceeding its declared budget.
For a ten-result search, the reservation is 10 credits. If seven records are returned, the final charge is seven credits and three are released. A full-profile request reserves 20 credits for a maximum of one record. Available credits exclude active reservations; credits_reserved reports outstanding reservations separately.
Introductory credits
A verified new workspace receives 100 one-time credits. You can spend them on any supported action. This covers five full-profile records at 20 credits each, 100 one-credit records, or a combination. You cannot interpret 100 credits as 100 full profiles.
Planned monthly plans
Paid checkout is not implemented yet. These are launch pricing proposals, not currently purchasable subscriptions.
| Plan | Monthly price (USD) | Credits | Illustrative cost per 1,000 credits |
|---|---|---|---|
| Starter | $49 | 10,000 | $4.90 |
| Growth | $149 | 50,000 | $2.98 |
| Pro | $249 | 100,000 | $2.49 |
| Scale | $599 | 300,000 | $2.00, rounded |
Scale is the largest planned tier. These figures exclude any applicable taxes and do not establish overage, rollover, refund, annual-billing, or SLA terms. No paid entitlement is granted until billing is implemented and verified.
Request and queue limits
| Boundary | Current value |
|---|---|
| Workspace API requests | 60 per minute |
| Subject API requests | 100 per minute |
| Source IP requests | 120 per minute |
| Active runs per workspace | 1 |
| Outstanding runs per workspace | 20 |
| Results per list action | 1–100; default 10 |
| Results per profile/company enrichment | 1 |
| Input string length | 500 characters |
| Request body | 32 KiB |
| Queue expiry | 15 minutes |
| Running lease expiry | 120 seconds |
Infrastructure and upstream limits can be tighter than the workspace request rate. A live request can return 202 instead of completing immediately. Respect Retry-After on 429 responses.
Credits are separate from source capacity
The initial source capacity ceiling is shared across the service: 300,000 reserved source records per UTC month. Source-account daily caps and pacing also apply. A customer's 300,000-credit plan does not reserve the entire source pool, guarantee immediate throughput, or provide 300,000 full-profile lookups.
Publicly available source data varies. Read coverage and run a representative sample before choosing your workload mix.
Standard person lookup
salesnavigator-search-person costs one credit only when it returns a person. It uses Sales Navigator name and current-company filters and never visits the profile. Empty results, ambiguous matches, and failed/incomplete lookups do not consume customer credits. The bounded search reserves ten internal source lines; these are separate from the one-credit customer price.