Skip to main content
Everything Pavo does for you runs on two things: AI models that read and write, and computers where the agents run code and query your data. Usage measures how much of both your work used, in one unit: the ASU.

What an ASU is

One ASU is one cent of usage. 100 ASUs = $1.
Two things use ASUs: Pavo sets a rate for each model and each computer type and converts what your work used into ASUs. Your balance counts down while the work runs, not at the end. Small charges add up until they make a whole ASU, so a very short call can show as 0.

What uses ASUs

Anything that runs a model or a computer uses ASUs. That includes:
Typical figures come from tasks run on Pavo at standard rates. Your own usage depends on how much each task reads and how long it runs.

What costs nothing

A worked project

Illustrative only. Your project depends on the size of your system and how much work it needs.
A team takes one project on one production system from first questions to a tested new ranker.

What drives usage

Most of a bill comes from four things. Knowing them is how you keep usage predictable.
1

How many agents run

A program with eight agents uses roughly eight times what one agent doing the same work would.
2

How much it has to read

Model calls are most of every bill. Long tasks, large files and big query results all add to what the model reads on every call.
3

Starting and restarting

Every time an agent starts or resumes, it first reads its instructions and the task so far. That has a fixed cost before any new work happens, so one message with everything you want costs less than five short ones.
4

How long computers stay running

A computer is charged for every second it runs, including while the agent waits for your reply. It is a small part of most bills, usually under a tenth, but stop work you no longer need.

When your ASUs run out

Your balance is shared by everyone on your account. When it reaches zero, all running work on the account stops.
  • Work starts only while your balance is above zero. Pavo does not estimate a cost before it starts, so a step already under way finishes and can take the balance below zero.
  • At zero, running tasks stop and nothing new can start. Results and files already produced stay where they are.
  • Adding ASUs pays off any amount below zero first. The rest is your new balance.
  • Nothing restarts on its own. After you add ASUs, open the task and send a message to continue.

Seeing your usage

Settings shows your current balance, the rate in ASUs per dollar, and what each task used, so you can find which work used the most. To add ASUs, use Request credits in Settings or contact your Pavo team.

Questions

Pavo uses several models and several kinds of computer, each with its own price. An ASU puts all of them on one balance, so you track one number instead of a rate card.When Pavo changes the rate for a model or a computer, the change applies only to usage from that point on. Usage already recorded is never repriced.
Every start and every resume begins with the agent reading its instructions and the task so far, and its computer is charged for as long as it runs. A task with many short back-and-forth messages, or one left waiting for a reply, can use more than its length suggests. The task’s usage in Settings shows where it went.
That is normal. You are charged for the work the agents do and the time their computers run, not for the weeks the program stays open. Time it sits open with nothing running costs nothing.
Tell us how many systems you want improved and how much work your team wants run each month, and we will size the allowance on the call. You can see what you are using in Settings at any time and add ASUs when you need more.
This page describes how Pavo meters usage and its standard rates. Your own allowance and rates are the ones stated in your agreement and order form.

Next steps

Pricing

Plans, terms, add-ons, and what every plan includes.

Programs, plans & modules

How a program is framed, approved, and broken into the work its agents run.