Credit usage and endpoint mappings can change over time. Confirm current
pricing in your dashboard or with the Crustdata team before production
planning.
Credit model overview
Crustdata pricing is credit-based.
- Credits are consumed when APIs return data.
- Different endpoints and optional fields can have different credit costs.
- Realtime and advanced payload options can cost more than baseline queries.
Legacy pricing patterns to expect
From the legacy docs:
- Enrichment APIs generally charge per profile/company returned.
- Search APIs may charge per result set or returned records.
- Auxiliary endpoints (autocomplete, credit checks) were often free.
- Expanded response fields (for example, deep social/post data) could increase cost.
How to estimate usage
- Define your primary endpoints.
- Estimate average records returned per request.
- Account for optional fields and realtime modes.
- Multiply by daily request volume.
- Add a safety buffer for retries and spikes.
Recommended process
- Validate assumptions with a staging workload.
- Monitor credits in the dashboard weekly.
- Set internal usage guardrails per team or workflow.
For plan and quota questions, contact Crustdata support from your account channel.
