What an agent task costs
How a ToolsXpo Code request is priced, what makes one task cheaper than another, and where to see what you spent.
Updated September 2, 2026
This page is about what the coding agent costs. For how credits work in general — the two currencies, where they come from and the order they are spent — see Credits, which is the canonical explanation.
What the agent spends
Model requests draw on AI credits. Tools the agent calls from the catalogue draw on general credits. A task can therefore be cheap in one and not the other, which is why the two balances are shown separately in the Account panel.
What makes one task cost more than another
Agent traffic has a shape that ordinary API calls do not: it resends a growing prefix on every turn. Input tokens, not output, are usually the larger half of the bill.
That is what the levers below all address.
Four things that lower it
Leave scout subagents on. Exploration moves to the cheap tier. It is most of an agent's token spend and almost none of its difficulty — finding a file is not the hard part. See Subagents.
Prefer a model that caches for long sessions. The prefix is resent every turn either way; with caching most of it is billed at a discount. On real traffic, agent requests run around 27% of input served from cache against 0% for one-shot calls. See Prompt caching.
Start a new task when the subject changes. A fresh context window is cheaper and sharper than a long one carrying unrelated history you are paying for on every turn.
Use Plan mode for large or unfamiliar changes. A wrong start costs more than the planning that would have avoided it.
What does not lower it
Auto-compact is not a cost control. It stops long tasks failing outright. Leave it on for that reason, not to save money.
Where to see what you spent
- Dashboard → Usage — spend by day, model and workspace.
- Dashboard → AI → Logs — individual requests: model, tokens, credits, cache share, latency, and which key served it.
- In the editor — turn on Settings → Chat → Show cost per request to see it inline.
Using your own key
With bring your own key you pay the vendor for tokens directly, and ToolsXpo charges a share of what the call would have cost instead of token credits. See How AI calls are billed for the general rule.
See also
- Credits — the two currencies, in full
- Prompt caching
- Agent and scout tiers
Related
Quickstart: your first task with ToolsXpo Code
Install the extension, sign in from your browser, and give the agent its first task — about five minutes end to end.
Choosing a model
What the model picker shows you, why some models are greyed out, and how to search a catalogue of hundreds with filters.
Credits: two currencies, three sources, and the order they are spent
General credits pay for our compute; AI credits pay for what a provider charges. Where each comes from, when it expires, and which is spent first.
Agent and scout tiers
Two reserved names — toolsxpo-agent and toolsxpo-scout — that let your workspace decide which model runs, without pinning it into the extension.