Per-action pricing for agent tools
Search- and agent-native vendors are starting to bill discrete tool actions — a web search, a code run, a research task — as their own unit, on top of (or instead of) tokens. Four corpus companies do it so far; the billable unit is shifting from the token to the action.
What's happening — and why
What's happening: when an AI agent uses a tool — searches the web, opens a page, runs code, kicks off deep research — some vendors now charge for that action directly, per call, separate from the tokens the model generates.
Why: agent workloads make tool calls a real, attributable cost (an API hit, compute, a third-party fee) that doesn't map cleanly to tokens. Pricing the action lets vendors recover it and signal it to buyers. It's early — mostly search/agent-native APIs — but it points at a future where the unit of value is the task an agent completes, not the text it emits.
How it works
Evidence over time
4 supporting · 2 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Groq | Jan 2026 | Built-in tools priced per use — web search, page visits and code execution billed per call on top of token rates. |
| Perplexity AI | Jan 2026 | API restructured around a Search API plus an Agentic Research tier — research priced per task, above raw per-call search. |
| You.com | Mar 2026 | Research API launched with effort tiers — agentic research billed per call by effort level, separate from token rates. |
| Exa | Jun 2026 | Per-endpoint usage pricing with a dedicated Agent endpoint and free monthly credits — each action billed per call. |
For buyers
Where tools are billed per action, forecast on the agent's plan — how many searches, page visits and code runs per task — not just token volume. A verbose agent can rack up tool fees that dwarf its token cost; cap tool calls per run where the vendor allows it.
For vendors
To price actions you need per-tool metering and a clear line item for each (search, visit, execution, research), plus a free monthly allotment to ease adoption. Make the per-call price legible so buyers can model an agent run end to end.
Outlook — what to watch
Watch whether the big general-model APIs (OpenAI, Anthropic) move tool use out of tokens into explicit per-action fees — if they do, this jumps from emerging to standard fast. The natural endpoint is pricing the completed task, which edges into outcome-based pricing.
Bottom line
Per-action tool pricing is early but real: four search/agent-native vendors now meter tool calls directly. If the major model APIs follow, the action overtakes the token as the unit that matters.
FAQ
What is per-action (agent-tool) pricing?
Charging for each tool an AI agent invokes — a web search, a page visit, a code execution, a research task — as its own billed unit, separate from the tokens the model generates.
Which vendors price agent tools per action?
In the corpus: Groq (built-in web search / visits / code execution), Perplexity (Agentic Research tier), You.com (Research API effort tiers) and Exa (per-endpoint + Agent). The big general-model APIs still fold tools into tokens.
How do I budget for an agent that uses tools?
Estimate tool calls per task (searches, visits, runs), not just tokens — tool fees can exceed token cost for search-heavy agents. Use any per-run caps or free allotments the vendor offers.