Skip to main content
An agent is priced by the work it does on each row, not by the answer it gives. Effort, web research and added tools each move that price, and an estimate shows before you spend it.
The agent editor's Effort picker and Web research switch, each with a credit chip showing what a row costs at that setting.

Rate chips beside Effort and Web research, before anything runs.

​
What moves the price

Three things move what one row costs:
  • Effort, the level you pick or leave on Auto
  • Web research, which adds its own surcharge when it is on
  • An added server under MCP servers, billed at its own rate when web research is off

​
See the estimate before you run

The price per row shows wherever you are about to spend it. That means beside each effort level, on the Web research switch, and on the button that commits a deploy.
1

Check the picker

Open Effort to see every level’s price per row, or click Compare effort levels to see them side by side.
2

Check the deploy dialog

When you click Add to table, the button that commits your choice opens a menu naming each batch and its price before anything runs.

​
Good to know

An added MCP server is not visible to that estimate, so the number shown is a floor rather than a ceiling when one is attached.
Usually, unless the agent has an MCP server added. Then the run still bills at that server’s own rate rather than the model’s plain rate.
Yes. Training runs the agent over your sample rows at the same per-row rate a deployed column would pay, and the estimate shows before you start.
Your overall spend, including agent runs, is on the Credits and billing page.

​
Next steps

Choose an effort level

Weigh cost against depth before you pick one.

Credits and billing

See your credit balance and the two ways to buy more.