> ## Documentation Index
> Fetch the complete documentation index at: https://devtools.waterfall.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage and signup economics

> Measure coverage, quality, and cost on your own signup data.

Completed results can include `output.usage`, which shows the cost breakdown and remaining balance. For asynchronous requests, the first response contains a job ID. Check the completed result for usage details.

| Field | Meaning |
| - | - |
| `total_usd` | Total recorded cost for the result. |
| `persons_usd` / `persons_count` | Person data cost and count. |
| `companies_usd` / `companies_count` | Company data cost and count. |
| `phones_usd` / `phones_count` | Phone data cost and count. |
| `balance_remaining_usd` | Reported account balance. |

See the [full usage reference](https://docs.waterfall.io/v1/inline-usage) for billing details and the [account reporter](https://docs.waterfall.io/v1/account-reporter-v2) for aggregate usage.

## Evaluate a representative signup sample

Measure personal and work email results separately. Track:

* Usable profile matches and company-domain coverage.
* Correctness on a reviewed sample.
* Response times at your expected volume.
* Total cost across person enrichment, company enrichment, and any later contact search.

Check that returned profiles match the right people. Compare cost alongside accuracy and the fields your workflow needs.

## Job-change checks

Only pay when a job change is found. There is no job-change charge for `no_change` or `unknown` results. If you enrich the new company or search for contacts afterward, those are separate billable operations.

[Track users across companies](/v1/track-users)

## Plan for volume

The dedicated DevTool setup is being tested. [Discuss your monthly signup volume](https://www.waterfall.io/book-a-call) to agree on pricing, capacity, and performance for your workflow. Sample values in the API reference are not a quote.