> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/provider-usage.md).

# Provider usage and lookup costs

Open **Settings → Provider usage** to review recorded provider calls and any balance reported during the provider's last check.

Distro uses your connected provider accounts. The provider bills usage under your account; the numbers shown here are not a universal Distro enrichment-credit balance.

## Understand a call estimate

A lookup can make more than one provider request. Workflow enrichment can dispatch multiple chain providers and merge their results. Records enrichment tries supported providers in order until one returns data.

A provider's billing rule can also charge for no-match requests, polls or verification. Review that provider's terms and plan before relying on a displayed call count as a monetary quote.

## Before a larger run

1. Check the provider connection and permitted surface.
2. Review the selected chain and [Provider support](/data-and-integrations/provider-support.md).
3. Start with a small controlled sample.
4. Compare the destination result and provider usage.
5. Split larger selections according to [batch limits](/records/results.md).

Pre-submit enrichment and a later workflow Enrich Lead step currently perform separate enrichment work; the later step is not guaranteed to reuse the earlier lookup. Avoid adding both just for speed without reviewing the cost and data requirements.

Use [Simulation](/workflows/test-and-publish.md) for branch checks that should not call providers. A last-reported balance can be stale; use the provider's dashboard for its current billing balance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/provider-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.