Pricing - Crustdata Docs

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. To see what a call actually cost, read the X-Credits-Used response header returned on every request.

Person endpoints

Endpoint	Credit usage	Notes
`/person/search`	0.03 per result	Best for low-cost discovery and filtering.
`/person/search/autocomplete`	Free	Use for typeahead and filter builders.
`/person/enrich`	1–7 per record	Starts with a base profile and scales with requested data.
`/person/contact/enrich`	1–5 per matched person	Billed per requested contact type — no base credit. Enterprise plans.
`/batch/person/contact/enrich`	1–5 per matched person	Same per-type prices as `/person/contact/enrich`. Enterprise plans.
`/dev_platform/enrich`	1 per result	Available on enterprise plans.

Company endpoints

Endpoint	Credit usage	Notes
`/company/search`	0.03 per result	Lightweight company discovery.
`/company/search/autocomplete`	Free	Useful for search UX and filter pickers.
`/company/enrich`	2–4 per record	Base 2; requesting `technographics` adds +2 per company that returns technographics data.
`/company/identify`	Free	Resolve a company from a domain or other supported identifier.
`/employee_review/enrich`	1 per company	Available on enterprise plans.

Job endpoints

Endpoint	Credit usage	Notes
`/job/search`	0.03 per result	Indexed job discovery, filtering, and hiring analysis.

Web endpoints

Endpoint	Credit usage	Notes
`/web/search/live`	1 per query	Web search. Available on self-serve and enterprise plans.
`/web/enrich/live`	1 per page	Web page fetch. Available on self-serve and enterprise plans.

Endpoint	Credit usage	Notes
`/social_post/professional_network/search/live`	1 per post · 3 per post with `exact_keyword_match` (reactors/comments unavailable — use enrich)	Available on enterprise plans.
`/social_post/professional_network/enrich/live`	1 per post · 5 per 100 reactors or comments · 10 per 100 reactors and comments	Available on enterprise plans.

Watcher endpoints

Endpoint	Credit usage	Notes
`/watch/person/search`	0.5 per new person	Discovery watcher. First run is a free baseline (up to 5 matches).
`/watch/company/search`	2 per new company	Discovery watcher. First run is a free baseline (up to 5 matches).
`/watch/person`	5–150 per changed entity	Entity watcher. First run is a free baseline; no charge on runs with no change. 5 at the default 30-day freshness; fresher data costs more (see below).
`/watch/company`	5 per changed entity	Entity watcher. First run is a free baseline; no charge on runs with no change.

You’re charged only for what’s delivered on recurring runs — a discovery run that finds nothing new, or an entity run where nothing changed, costs nothing. Each watcher lives under its dataset: Person → Watch and Company → Watch, each with an Entity and a Discovery watcher. For a person entity watcher, the per-notification rate is tiered by config.refresh_frequency_days — how fresh the tracked data is kept. It does not depend on how often the watch runs.

`refresh_frequency_days`	Credits per changed entity
not set / `30` (default)	5
`14`	10
`7`	20
`3`	50
`1`	150

Company entity watchers run at the 30-day baseline (5 credits per changed company).

Batch endpoint

Endpoint	Credit usage	Notes
`/batch/company/search`	0.03 per result	Same as company search pricing.
`/batch/company/enrich`	2–4 per record	Same as company enrich pricing, including the `technographics` add-on.
`/batch/company/professional_network/search/live`	2 per company	Same as live company search pricing.
`/batch/person/search`	0.03 per result	Same as person search pricing.
`/batch/person/enrich`	1–7 per record	Same as person enrich pricing.
`/batch/person/professional_network/search/live`	2 per profile	Same as live people search pricing.
`/batch/person/professional_network/enrich/live`	7 per profile	Same as live people enrich pricing.
`/batch/person/identify`	1 per match	Reverse email lookup. Only emails that resolve to a person are billed; unmatched are free.
`/batch/job/search`	0.03 per result	Same as job search pricing.
`/batch/social_post/professional_network/enrich/live`	1 per post · 5 per 100 reactors or comments · 10 per 100 reactors and comments	Same as social post enrich pricing. Enterprise plans.
`/batch/{batch_id}`	Free	Current pricing assumption: batch status checks are non-billable.
`/batch`	Free	Current pricing assumption: batch listing is non-billable.

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 returned	Additional credits	What you get
Base profile	1	Core person identity, role, location, experience, education, certifications, skills, and social handles
Personal email data	+2	Personal email details
Phone data	+2	Direct phone numbers
Business email data	+1	Verified business email details
Developer platform data	+1	Developer platform profile, repos, orgs, and activity

The maximum current cost for a single enriched person record is 7 credits. The base credit is charged once per matched record.

Common credit patterns

Use case	Typical data requested	Credits
Basic profile lookup	Base profile only	1
Sales outreach	Base profile + business email	2
Full outbound prospecting	Base profile + business email + phone	4
Recruiting with personal contact data	Base profile + personal email + phone	5
Maximum person enrich payload	Base profile + all add-ons	7

For person enrich, send a JSON body with either professional_network_profile_urls or business_emails, based on the identifier you have.

Person Contact pricing

/person/contact/enrich bills per requested contact type, per matched person — there is no base credit (the endpoint returns contact data only).

Contact type requested	Credits per matched person
`contact.business_emails`	1
`contact.personal_emails`	2
`contact.phone_numbers`	2

Only the types you request are fetched and billed. Omitting fields requests all three (5 per matched person, the maximum). contact.websites is not one of the billed contact types — requesting it currently uses 0 credits. Identifiers with no match are not billed. /batch/person/contact/enrich bills the same per-type prices, per matched person (maximum 5) — counted per type, not per record (four business-email candidates count once).

Person enrich request examples

Use these examples to enrich by profile 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"
        ]
    }'

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"
        ],
        "fields": [
            "basic_profile.summary",
            "professional_network.followers"
        ]
    }'

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 '{
        "business_emails": [
            "abhilash@crustdata.com"
        ]
    }'

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

Endpoint	Credit usage	Notes
`/person/professional_network/search/live`	2 per profile	Fresh live people search.
`/person/professional_network/enrich/live`	7 per profile	Fresh profile retrieval when cached enrich is not enough.
`/company/professional_network/search/live`	2 per company	Fresh live company search.
`/job/professional_network/search/live`	2 per result	Fresh live job search for a single company.

Shared live-search endpoints

Endpoint	Credit usage	Notes
`/professional_network/search/autocomplete`	Free	Shared 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 type	Why
Explore a large audience cheaply	Search	Search is priced for discovery and returns lightweight records.
Build full profiles or contact-ready records	Enrich	Enrich returns detailed person or company data.
Power typeahead or filter suggestions	Autocomplete	Autocomplete is free and designed for interactive search UIs.

Estimate usage before you launch

List the endpoints your workflow will call

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

Estimate returned records per request

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

Account for optional data and live modes

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

Multiply by daily volume

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

Add a buffer for retries and spikes

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

Rate limit considerations

Default rate limits vary by endpoint, ranging from 10 requests per minute on live (real-time) endpoints to 45 requests per minute on autocomplete endpoints. See Rate limits for the full per-endpoint table. For throughput planning, see Rate limits.

Frequently asked questions

How is search billed?

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.

How do I keep person enrich costs under control?

Start with the base profile. Add business email, personal email, phone, or developer platform data only when your workflow uses it.

What happens when I run out of credits?

Billable requests return an error until you purchase more credits or your account is replenished under your plan.

Do unused credits expire?

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.

Search first

Enrich selectively

Plan for live endpoint usage

​Self-serve endpoint pricing

​Person endpoints

​Company endpoints

​Job endpoints

​Web endpoints

​Social Post endpoints

​Watcher endpoints

​Batch endpoint

​Person enrich pricing

​Common credit patterns

​Person Contact pricing

​Person enrich request examples

​Enterprise-only and plan-gated live endpoint pricing

​Live people, company, and job data

​Shared live-search endpoints

​Free endpoints

​Search vs enrich

​Estimate usage before you launch

​Rate limit considerations

​Frequently asked questions

Self-serve endpoint pricing

Person endpoints

Company endpoints

Job endpoints

Web endpoints

Social Post endpoints

Watcher endpoints

Batch endpoint

Person enrich pricing

Common credit patterns

Person Contact pricing

Person enrich request examples

Enterprise-only and plan-gated live endpoint pricing

Live people, company, and job data

Shared live-search endpoints

Free endpoints

Search vs enrich

Estimate usage before you launch

Rate limit considerations

Frequently asked questions