Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.crustdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Pricing can change by plan, entitlement, and endpoint version. Confirm the current credit cost in your dashboard or with the Crustdata team before you plan production usage.
Crustdata uses a credit model across its APIs. Use low-cost search endpoints to narrow your list, then enrich only the records you want to inspect in detail.

Search first

Use search endpoints for low-cost discovery, then enrich only the records you want to keep.

Enrich selectively

Person enrich starts with a base profile and adds cost only when you ask for higher-value data.

Plan for live endpoint usage

Web live endpoints are available on self-serve plans. Company and Person live endpoints remain plan-gated.
Credits are currently valid for 6 months from the purchase date.

​
Self-serve endpoint pricing

This page lists pricing for the endpoints currently documented in this docs site. It does not include unpublished or not-yet-documented routes.
Use these tables to estimate common self-serve search, identify, and enrich costs.

​
Person endpoints

EndpointCredit usageNotes
/person/search0.03 per resultBest for low-cost discovery and filtering.
/person/search/autocompleteFreeUse for typeahead and filter builders.
/person/enrich1–7 per recordStarts with a base profile and scales with requested data.

​
Company endpoints

EndpointCredit usageNotes
/company/search0.03 per resultLightweight company discovery.
/company/search/autocompleteFreeUseful for search UX and filter pickers.
/company/enrich2 per recordFlat-rate company enrichment.
/company/identifyFreeResolve a company from a domain or other supported identifier.

​
Job endpoints

EndpointCredit usageNotes
/job/search0.03 per resultIndexed job discovery, filtering, and hiring analysis.

​
Web endpoints

EndpointCredit usageNotes
/web/search/live1 per queryWeb search. Available on self-serve and enterprise plans.
/web/enrich/live1 per pageWeb page fetch. Available on self-serve and enterprise plans.

​
Person enrich pricing

Person enrich uses additive pricing. You pay for the base profile first, then add credits only for the extra data you request.
Data returnedAdditional creditsWhat you get
Base profile1Core person identity, role, location, experience, education, certifications, skills, and social handles
Personal email data+2Personal email details
Phone data+2Direct phone numbers
Business email data+1Verified business email details
Developer platform data+1Developer platform profile, repos, orgs, and activity
The maximum current cost for a single enriched person record is 7 credits.
For person enrich, send a JSON body with either professional_network_profile_urls or business_emails, based on the identifier you have.

​
Common credit patterns

Use caseTypical data requestedCredits
Basic profile lookupBase profile only1
Sales outreachBase profile + business email2
Full outbound prospectingBase profile + business email + phone4
Recruiting with personal contact dataBase profile + personal email + phone5
Maximum person enrich payloadBase profile + all add-ons7

​
Person enrich request examples

Use these examples to enrich by LinkedIn URL, request specific fields, or reverse-lookup a person from a business email. 
curl --request POST \
    --url https://api.crustdata.com/person/enrich \
    --header 'authorization: Bearer YOUR_API_KEY' \
    --header 'content-type: application/json' \
    --header 'x-api-version: 2025-11-01' \
    --data '{
        "professional_network_profile_urls": [
            "https://www.linkedin.com/in/abhilashchowdhary"
        ]
    }'
For full request patterns and field selection behavior, see Person enrichment.

​
Enterprise-only and plan-gated live endpoint pricing

Company and Person live endpoints are plan-gated and can have custom quotas or contract pricing.
Web Search and Web Fetch are available on self-serve plans. The live Company and Person endpoints below still require the right plan or enterprise access.

​
Live people, company, and job data

EndpointCredit usageNotes
/person/professional_network/search/live2 per profileFresh live people search.
/person/professional_network/enrich/live7 per profileFresh profile retrieval when cached enrich is not enough.
/company/professional_network/search/live2 per companyFresh live company search.
/job/professional_network/search/live2 per resultFresh live job search for a single company.

​
Shared live-search endpoints

EndpointCredit usageNotes
/professional_network/search/autocompleteFreeShared live-search autocomplete when enabled for your account.

​
Free endpoints

These endpoints do not currently consume credits:
  • /person/search/autocomplete
  • /company/search/autocomplete
  • /company/identify
  • /professional_network/search/autocomplete (when enabled for your enterprise plan)

​
Search vs enrich

If you need to…Best endpoint typeWhy
Explore a large audience cheaplySearchSearch is priced for discovery and returns lightweight records.
Build full profiles or contact-ready recordsEnrichEnrich returns detailed person or company data.
Power typeahead or filter suggestionsAutocompleteAutocomplete is free and designed for interactive search UIs.

​
Estimate usage before you launch

1

List the endpoints your workflow will call

Separate self-serve, enterprise live, and utility requests. They are not billed in the same way.
2

Estimate returned records per request

Search pricing depends on results returned, not only the number of calls.
3

Account for optional data and live modes

Contact data, developer platform data, and enterprise live workflows can raise per-record cost.
4

Multiply by daily volume

Model normal traffic first, then add weekly or monthly growth assumptions.
5

Add a buffer for retries and spikes

Keep headroom for queue bursts, replay jobs, and production debugging.

​
Rate limit considerations

Endpoint setTypical rate limit
Endpoints listed on Rate limits15 requests per minute
Other gated or unpublished endpointsMay vary by plan
For throughput planning, see Rate limits.

​
Frequently asked questions

Search is billed per result returned. For example, 10 results at 0.03 credits per result use 0.30 credits. A request that returns no results uses no credits.
Start with the base profile. Add business email, personal email, phone, or developer platform data only when your workflow uses it.
Billable requests return an error until you purchase more credits or your account is replenished under your plan.
Yes. Credits are valid for 6 months from the date of purchase.
For plan, quota, or enterprise pricing questions, contact Crustdata support through your account channel.