Skip to main content
Every response includes an 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

Usage is calculated using your currently configured rates. If your pricing changed recently, updated rates may not appear until any existing prepaid balance has been fully consumed.

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_usd across 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
The cost data is already in the response. No extra round-trip needed.

Examples by endpoint

Contact Enrichment Launcher
Phone Enrichment Launcher
Prospector Launcher
Search Contact Launcher
Search Company Launcher
Email Verifier
Job Change Launcher
Company Reveal Launcher
Company Enrichment Launcher