---
title: Receipts
description: "Where to find the exact charge for a run: actualCost, route.summary, runs_evidence and your ledger."
---

Every run settles to one charge, and you can always trace it back to the attempt or attempts that
produced it.

## `actualCost`

The run's own charge. Compare it against `estimatedCost` (what the hold reserved) to see how much
came back to your balance.

## `route.summary`

On a fallback run, `route.summary` states each attempt's charge exactly, trimmed of trailing
zeros: `"$0.0198"`, `"$0.005"`, `"$1"`, `"$0"`. The full mechanics, including how the wording
changes per job, are in [Receipts](/concepts/receipts).

## Every attempt

```bash
looot runs evidence <run-id>
```

[`runs_evidence`](/mcp-tools/runs-evidence) (MCP) and `GET /v1/runs/{id}/attempts` (REST) list every attempt with its status,
the provider's own response status, latency, a receipt id and its cost. The receipts always sum to
the run's charge.

## Your ledger

```bash
looot ledger list --limit 50
```

Every balance movement, including this run's `reservation`, `charge` and any `release`, is one
ledger entry. See [Wallet](/money#your-ledger) for the entry types.

## Worked example

Run `job:company.enrich` with fallback, get `route.summary` back as `"clearbit: matched
($0.0245). Charged $0.0245."`, then confirm with `runs_evidence` that the one attempt's receipt
cost matches, and with `looot ledger list` that the `charge` entry is the same $0.0245.

<Related />