---
title: Quotes
description: How to price a run before you make it, using a search row's estimatedPrice and costPerSuccessUsd, or inspect's estimatedMaxCost.
---

There is no separate quote step. What a search row shows and what [`inspect`](/mcp-tools/inspect) shows before a run
are the numbers you plan against.

## On a search row

Every row carries `estimatedPrice`, `priceBasis` (per call, or per result) and
`costPerSuccessUsd` (the price divided by the provider's measured success rate, the better number
for comparing providers that fail at different rates):

```json
{
  "endpointId": "hunter-email-finder",
  "estimatedPrice": 0.0245,
  "priceBasis": "perCall",
  "costPerSuccessUsd": 0.0327
}
```

## Before you run one endpoint: `inspect`

<CodeGroup>

```bash CLI
looot inspect hunter-email-finder
```

```json MCP
inspect { "endpointId": "hunter-email-finder", "detail": "run" }
```

</CodeGroup>

`inspect` returns the exact price formula in `endpoint.price` and `estimatedMaxCost`, the most one
run can hold. Running it needs available balance at least equal to `estimatedMaxCost`: check
[your balance](/money) first.

## Before you run a job

For `job:<id>` runs, price the job from its rows in a search answer, not from a single
`inspect` call: `inspect job:<id>` is not supported yet. Search `job:company.enrich` (or filter by
`capability`) and read `costPerSuccessUsd` on the row you expect to be picked.

## Batch math

For a batch, multiply `costPerSuccessUsd` by the row count to estimate the total, and check
[your balance](/money) before you start. Tell the person running the batch the total when
it is more than they would expect to spend.

For example, verifying 500 emails through `job:people.email.verify` at
`costPerSuccessUsd: 0.0033` estimates to about $1.65 for the batch; the charged total is the sum of
what each run's `actualCost` turns out to be, since a per-result price only charges for what came
back. See [Receipts](/money/receipts).

<Related />