output.usage object alongside the enrichment payload. No separate API call needed. Cost and balance data is always present.
Usage data is returned inside
output, at the same level as the enrichment, prospector, search, or verification results.Fields
More than one
*_usd field can be non-zero in the same request. For example, if you run a Contact Enrichment with include_phones: true and we return both a contact record and a phone number, you’ll see charges under both persons_usd and phones_usd.
Cost mapping
Agentic and automated pipelines
balance_remaining_usd is returned on every call, making it straightforward to build cost-aware automation without polling the Account API.
Common patterns:
- Budget enforcement: halt a loop or batch job when balance drops below a threshold
- Top-up triggers: fire an alert or webhook when balance crosses a floor
- Per-run cost tracking: sum
total_usdacross calls to measure spend per job or workflow - Self-regulating agents: let an LLM-orchestrated pipeline decide whether to continue enriching based on remaining balance
Examples by endpoint
Contact Enrichment
Contact Enrichment
Phone Enrichment
Phone Enrichment
Prospector
Prospector
Search Contact
Search Contact
Search Company
Search Company
Email Verification
Email Verification
Job Change
Job Change
Company Reveal
Company Reveal
Company Enrichment
Company Enrichment