What costs credits
| Operation | Credit behaviour |
|---|---|
POST /api/v1/companies/search | Charged based on the companies searched and enriched |
POST /api/enrichments | Charged per enrichment lookup attempt |
POST /api/v1/platform/scrapers/* | Charged per scrape request |
POST /api/deep-research | Charged for LLM-powered deep research |
What is free
| Operation | Why it’s free |
|---|---|
GET /api/health | Infrastructure probe — no external calls |
GET /api/operations/:id | Polling — reads stored operation state only |
Metered charges
Launch endpoints charge based on the work completed for your request. Responses expose customer-safe credit fields such ascreditsCharged, estimates, and request metadata.
Credit metering in company search responses
Company search responses include ametering object so you know exactly what was charged:
creditsCharged reflects what was actually deducted. estimatedMaxCredits is the ceiling that was reserved at the start of the call — you’re only charged the actual amount.
Insufficient credits — 402 error
If your account doesn’t have enough credits to cover an operation, the API returns a402 Payment Required response before any external calls are made:
402 is returned. Reduce the request scope or add credits before retrying.