> ## Documentation Index
> Fetch the complete documentation index at: https://jesse-7a8b4a1d.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Cost

> The dollar total to show for a search, and what lands on the wallet.

Show `cost.usd` to the user. It is the cost of the search so far, in dollars, with up to 6 decimal places.

Each `cost` event replaces the number you are showing. It is not an amount to add to the previous one.

The last `cost` event before `done` is the final cost. That is the only cost figure to display.

## What is actually charged

Starting a search holds \*\*$5.00** against your balance. The hold grows in $5.00 steps while a long run needs it, and it is only a hold: when the run ends it is released and you are charged what the run really spent, which is the same figure the `cost` events have been reporting all along. A search that cost $1.20 charges $1.20.

So the $5.00 is not the price, and the `402` you get when your available balance is under $5.00 is about the hold rather than about what the search would have cost. Available balance means your balance minus whatever is held by runs already in flight, which is why two searches started at once need \$10.00 between them. See [Errors](/errors).

A run also has a hard ceiling, \$25.00, measured on Floworks' own cost of running the search rather than on the figure you are charged. The two are not the same number, and the one you pay is the smaller of them. A run that reaches the ceiling ends as `budget_exhausted` with the rows it had already verified, charged for what it spent and no more. See [The run](/run).

On the run object the same figure appears as `billableAccruedMicrousd` in micro-USD, with `usd` and `usdDisplay` beside it as strings, so a client that must not use binary floats never has to.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.