Count every model call
Include planning, execution, reflection, evaluation, and fallback calls. Agent cost is usually call volume multiplied by context growth, not one visible chat request.
A single task can trigger planning, retrieval, tool use, validation, and retries. Model those calls together instead of pricing one prompt in isolation.
Use this as a shortlist, then test quality and retry behavior on your own tasks.
This models token charges, not hosting, vector storage, search tools, human review, or provider minimums. Cache savings apply only to models with a published cached-input rate.
Include planning, execution, reflection, evaluation, and fallback calls. Agent cost is usually call volume multiplied by context growth, not one visible chat request.
Failed tool calls, malformed output, and quality retries still consume tokens. A small retry assumption makes forecasts more realistic and exposes fragile routes.
Per-call cost is useful for debugging. Cost per accepted task is better for business decisions because it includes multi-step behavior and failures.
Any request to a language model: planning, tool selection, summarization, execution, self-checking, fallback, and final response generation.
Measure representative production traces when possible. Otherwise start with the assembled system prompt, conversation history, retrieved context, tool schemas, tool output, and expected response.
No. It estimates model token charges. Add embeddings, vector storage, search, browser tools, hosting, and human review separately.