Skip to main content
Data result responses can include output.usage alongside the returned profiles or verification result. It describes the job’s cost breakdown and an account balance snapshot. For asynchronous enrichment, first launch the job and save its job_id. Read usage from the Finder result when available. The initial launch response contains job_id and start_date, without output.usage.

Read the cost breakdown

This illustrative excerpt shows only the usage object; the data payload is omitted. The amounts are examples, not a price list.
A job can report costs in more than one category. For example, a contact lookup with include_phones: true can return both person and phone costs. Read the returned breakdown rather than assuming one category per endpoint.

Track a workflow’s spend

Store the reported usage with your local record and the Waterfall job_id. Count each job once when calculating a workflow total. Reading the same Finder result again does not make its reported total_usd a new cost to add to your total. Use the data to:
  • Compare cost per useful result across use cases.
  • Review phone costs separately from profile costs.
  • Alert your team when a reported balance reaches a threshold.
  • Decide whether your workflow should submit more records.
A balance snapshot helps you observe spend. It does not reserve a budget for work already in flight or enforce a shared spending cap across concurrent requests. Apply your workflow’s spending controls before starting more jobs.

Check account totals and configured prices

Account Reporter V2 returns account and key usage and the current balance. Master-key requests also return a price object with unit prices from the latest payment; it can be empty if there is no payment record. Use start_date and end_date to inspect a date range. The report groups usage by its recorded UTC date; it is not a list of individual jobs. Prices depend on your account’s configuration. When a prepaid balance carries earlier rates, new rates may take effect after that balance is consumed. Contact the team to confirm your pricing and billing terms, including how missing or partial results are charged for the APIs you plan to use.
  • Evaluate Waterfall: compare useful results and cost on a representative sample.
  • API Keys Management: organize access and usage by workflow.
  • Errors: distinguish account quota errors from request rate limits.
  • FAQ: common pricing and integration questions.