Credits
Each call to POST /research consumes 1 credit from your monthly plan.
Credits reset at the start of your billing cycle.
GET /research-status does not consume credits — poll as many times as
needed.
Cache hits
If a prospect or company was recently enriched (within cache TTL),
the request returns cached data immediately. A credit is still consumed,
but the response is near-instant.
Credit alerts
You can enable email notifications when you reach 75% and 95% of your monthly credits
in Settings → Notifications.
What happens when credits run out
POST /research will return 429 credits_exhausted.
Your existing data and API keys remain active — you just can’t start new research jobs
until the next billing cycle or until you upgrade your plan.
Concurrent requests
There is no hard limit on concurrent requests, but the research worker
processes one job per invocation. For high-volume batch enrichment,
consider spacing requests out or contact us about custom plans.
API key limits
See the API Keys page for key limits per plan.