You've been generating images, video and voice-overs. Now you want the receipt: how much have I used, which models did it, and how was that price worked out? You can ask for all of it in plain English, and this page explains every line you get back.
The short version: everything is priced per unit of what you actually made — a second of video, a megapixel of image, a thousand characters of speech. Nothing else. No subscriptions, no minimums, no surprises.
Every model has a price per unit. A unit is a natural measure of the thing you asked for — a second of video, a megapixel of image, 1,000 characters of speech, one image, one 3D mesh.
Your cost for a job = unit price × how many units you asked for.
You don't need to find a dashboard or an invoice page. In Claude (Cowork, Desktop, Code) or Cursor, with the Livepeer Agent connected, type any of these:
Behind the scenes that's the me_usage report — your own activity, under your own key. It needs no special permission, because it's your data. If you'd rather see it job-by-job rather than totalled, ask for "my cost report, per job".
Here's a real one. Three kinds of work — a couple of short videos, one image, three voice lines:
Read it top to bottom:
| You see | It means |
|---|---|
| last 14d | The time window. You can ask for 24h, 7d or 14d. Ask for longer and you'll be told it was shortened to 14 days rather than handed a total that quietly leaves things out. |
| 6 calls | How many separate pieces of work ran. One image is one call; one video is one call. |
| 6 ok / 0 failed | How many finished, and how many didn't. See §6 — a failed render can still cost money, because the model still ran. |
| estimated cost | The total at list price. Called an estimate for one honest reason: it's priced from what you asked for at the moment you asked, so it's the expected charge, not a settled invoice. |
| pixverse-i2v, flux-dev… | The model that did the work. You never have to name one — the agent picks — but the report shows which it used so you can steer next time ("use the cheaper video model"). |
| 2 calls · $0.6300 | How many times that model ran in the window, and what it came to in total. |
| unknown (sometimes) | Work we recorded but couldn't attribute to a single model — usually a step that fans out to several. Rare, and it never inflates the total. |
There is exactly one formula, and it's the one from the top of this page:
What counts as a "unit" depends on what kind of thing you're making. There are five:
| Kind of work | Unit | Counted as | Real prices today |
|---|---|---|---|
| Video | per second | The length of the clip you asked for. A 5-second clip is 5 units. | $0.0394 – $0.42 /sec |
| Image (some models) | per image | One picture, one unit — size doesn't change it. | $0.0022 – $0.063 /image |
| Image (other models) | per megapixel | How big the picture is. A 1024×1024 image is ≈1 megapixel. | $0.0032 – $0.063 /MP |
| Speech | per 1,000 characters | The length of the script you gave it, counted in characters. | $0.0053 – $0.026 /1k chars |
| 3D / music / one-offs | per item | One mesh, one track, one job — a flat price per result. | $0.10 – $0.21 /item |
Editing steps — trimming, cropping, adding captions, stitching clips together — are priced the same way (per second of video touched) and are typically a tenth of a cent per second, so they round to nothing next to generation.
Every number in the report above can be reproduced with the one formula. Here it is:
| Step | Value |
|---|---|
| Model used | pixverse-i2v (turns a still image into a moving clip) |
| Unit price | $0.063 per second |
| Clip length | 5 seconds |
| One clip | 5 × $0.063 = $0.315 |
| Two clips | 2 × $0.315 = $0.63 ✓ |
| Step | Value |
|---|---|
| Model used | flux-dev (text → image) |
| Unit price | $0.02625 per megapixel |
| Image size | 1024×1024 ≈ 1 megapixel |
| One image | 1 × $0.02625 = $0.0263 ✓ |
| Step | Value |
|---|---|
| Model used | gemini-tts (text → speech) |
| Unit price | $0.01575 per 1,000 characters |
| Script length | ~93 characters per line (a short sentence) |
| One line | 0.093 × $0.01575 ≈ $0.0015 |
| Three lines | ≈ $0.0044 ✓ |
If a model runs and then fails — a timeout, a refusal, a bad frame — the work was still done, so it's still charged. That's why the report shows ok and failed counts side by side: a bill bigger than your finished-output count usually means retries. If a job fails for a reason you think is ours, say so and we'll look at it.
A request that fails before a model runs — a bad input, an unreachable service — costs nothing, so it's counted as a call with no price. Your total is never inflated by these; it can only be a slight under-count of things that never actually ran.
The price is worked out from your request at the moment you make it — the model, the length, the size. For the overwhelming majority of jobs that is the charge. It's called an estimate because occasionally a model returns slightly more or less than asked (a clip rounded to the nearest whole second, say).
Detailed per-call records are kept for 14 days. Ask for 30 days and you'll be told it was shortened, rather than shown a "30-day total" that's really 14 days of data. If you need longer-term records, keep the reports you pull — or ask us about longer retention.
Long renders are polled for progress. Those checks are free and are never double-charged — one render is charged once, however many times you or the agent look at it.
No. Your own usage and your own cost are yours to read, always. (An everyone's-usage view — for whoever runs the account — is separate and is the only one that's restricted.)
No. You pay for units of output. Generate nothing this month and it costs nothing.
Just the output — the images, clips, audio and edits it produces for you. Planning and conversation aren't billed as media.
Quality and speed. The range runs from about 4 cents a second to 42 cents a second. Ask "what are my video options and what do they cost?" and pick per job — a social draft and a hero shot don't need the same model.
Yes — ask for "my full usage report" and you'll get a complete, self-contained version with every row, suitable for saving or printing.
Ask for the per-job cost report rather than the model totals — it lists each job with its model and price, which usually makes the culprit obvious (nearly always a longer-than-expected video, or retries). If it still doesn't add up, send us the report and we'll trace it.