Task costs

Fetch Hive tracks task costs by service. Most services have a fixed task credit cost. Some depend on provider usage, search depth, account model type, or number of generated images.

​

How task costs work

Hosted AI model calls, hosted agent calls, hosted prompt runs, hosted native search, and hosted image generation use the hosted LLM pool for provider usage. Each call still records a task count. Personal model calls use your connected provider account. They charge the platform task credits shown in the table and don’t add a hosted provider charge. Metered hosted tools (Google Search, Bing Search, Google News, Google AI Mode, Website Scrape, Exa Search, Exa Similar, and Perplexity Search) convert the recorded service cost plus a 6% service fee into task credits. Logs show those two USD figures separately so you can see exactly what the provider charged and what Fetch Hive added. They explain the task-credit charge; they are not billed on top of it. This 6% service fee is separate from the 6% fee charged when you top up the Hosted LLM Wallet.

​

Workflow and model services

​

Agent tool calls

Agent tool calls are billed when the agent run records each completed tool call. Sub-agents bill through their child agent run instead of the parent tool call. Nested sub-agent costs, tokens, and task credits roll up through the parent chain, including failed child runs when they produced billable completion records. Execution timeout and depth/parallelism caps are controlled separately from trace and cost rendering.

​

Structural services