> ## 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
> Learn how Crustdata credits work, what common endpoints cost, and how to estimate usage before you ship.
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.
Use search endpoints for low-cost discovery, then enrich only the
records you want to keep.
Person enrich starts with a base profile and adds cost only when you ask
for higher-value data.
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
| 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. |
### 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** per record | Flat-rate company enrichment. |
| `/company/identify` | **Free** | Resolve a company from a domain or other supported identifier. |
### 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. |
## 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**.
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 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** |
## Person enrich request examples
Use these examples to enrich by LinkedIn URL, request specific fields, or
reverse-lookup a person from a business email.
```bash Base profile request (1 credit) theme={"theme":"vitesse-black"}
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"
]
}'
```
```bash Request specific fields theme={"theme":"vitesse-black"}
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"
]
}'
```
```bash Reverse lookup by business email theme={"theme":"vitesse-black"}
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](/person-docs/enrichment/introduction).
## 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
Separate self-serve, enterprise live, and utility requests. They are not
billed in the same way.
Search pricing depends on results returned, not only the number of
calls.
Contact data, developer platform data, and enterprise live workflows can
raise per-record cost.
Model normal traffic first, then add weekly or monthly growth
assumptions.
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](/general/rate-limits) for the full per-endpoint table.
For throughput planning, see [Rate limits](/general/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.