AI Agent Pricing: API Rates, Build Budget and Monthly Cost
A custom AI agent costs engineering time plus recurring model, platform, tool and operating fees. As a capacity example, 100 backend-engineering hours at Powercode’s starting rate of USD 36/hour cost from USD 3,600. AI specialists are quoted against the role brief; this example is not a complete agent price. The scope and role mix determine how much work an agent needs.
Measure cost per accepted task, not just per attempt. In the planning example below, USD 400 spent on 1,000 attempts with 700 accepted completions means about USD 0.57 per accepted task. These are illustrative inputs, not client results.
| Budget item | What to include |
|---|---|
| Implementation | Engineering, integrations, evaluation, permissions and handover. |
| Operation | Models, platforms, tools, retries, monitoring and human review. |
| Accepted task | Total operating cost divided by accepted completions for the same period. |
Budget separately for implementation and running the agent. Include integrations, permissions, evaluation and handover in the build estimate. For running costs, count completed tasks, model and tool usage, retries and human review. The comparisons below show API rates, platform billing and workload calculations so you can price the same job across options.
Vendor prices were checked on 30 October 2026. Workloads and capacity calculations below are explicit planning examples, not measured results or fixed-price project offers.

AI agent pricing at a glance
These selected examples use different billing units. API rates are per one million tokens; Fin prices are per defined outcome.
| Product | Published rate | What the unit covers |
|---|---|---|
| OpenAI GPT-6.1 Terra | $1 input / $5 output per million tokens | Standard short-context API input/output. Official Terra rates. |
| OpenAI GPT-6.1 Sol | $2 input / $10 output per million tokens | Standard short-context API input/output. Official Sol rates. |
| Anthropic Claude Sonnet 4.6 | $3 input / $15 output per million tokens | Base API token rates for this named model. Official Anthropic rates. |
| Intercom Fin AI Agent | $0.99 per resolution; $9.99 per qualification | Procedure handoffs, disqualifications and self-serve routing are also $0.99. Applies to chat/email on Intercom; check voice, platform and high-volume terms separately. Official Fin outcome rates. |
For APIs, caching, tools, long context and processing tiers can change the bill. Compare the exact configuration and task quality; our Terra business-test guide explains a bounded model comparison.
A billed outcome is not automatically an independently verified business result. For example, Fin can count a resolution when the customer confirms the answer or leaves without asking for more help. It bills at most one outcome per conversation. Agree what counts as an accepted task in your own evaluation before comparing that meter with a custom agent.
Use those rates inside the full cost stack below. Neither an API rate nor an outcome fee includes every implementation and operating cost.
Choose what you are buying
Before comparing build quotes, give each supplier the same acceptance task. See how to choose an AI agent development company for a practical account-update example.
| Option | What you pay for | Work you must still allocate |
|---|---|---|
| Direct model API | Metered model and tool usage | Workflow code, integrations, permissions, deployment and operations |
| Ready-made agent platform | A subscription, seats, usage or defined outcomes | Configuration, data preparation, integrations and review of the platform’s limits |
| Custom agent engineering | Discovery and engineering, followed by runtime and support | An owner for scope, acceptance, data access, ongoing evaluation and handover |
Include the full cost stack
| Cost layer | How it is charged | What makes it grow |
|---|---|---|
| Model inference | Input, cached input, reasoning and output tokens | Long context, verbose output and repeated loops |
| Tools | Per search, call, document, transaction or third-party API request | Multi-step tasks and failed calls |
| Retrieval and memory | Embedding, storage, vector search and database operations | Large knowledge bases and frequent re-indexing |
| Execution | Compute time, containers, browsers or sandboxes | Code execution and long-running workflows |
| Operations | Monitoring, evaluations, incident response and support | Customer-facing or regulated use cases |
| Implementation | Engineering hours | Integrations, permissions, edge cases and compliance |
That is why two products using the same model can have radically different economics. A support assistant that answers from a curated help centre is not comparable to an agent that opens a CRM record, checks a contract, calculates a quote and sends the result for approval.
What does an AI agent cost per month?
Build the monthly estimate from the workload. For example, assume 10,000 model requests, each with 40,000 uncached input tokens and 5,000 billed output tokens, at the standard rates above.
| Model | Input per request | Output per request | Total per request | 10,000 requests |
|---|---|---|---|---|
| GPT-6.1 Terra | $0.040 | $0.025 | $0.065 | $650 |
| GPT-6.1 Sol | $0.080 | $0.050 | $0.130 | $1,300 |
| Claude Sonnet 4.6 | $0.120 | $0.075 | $0.195 | $1,950 |
This is model usage only. The token counts and request volume are assumptions; include all billed output, including reasoning where applicable. Add platform, tools, retrieval, infrastructure, review and support to obtain the running budget. Different models may tokenise the same material differently.
A business task can trigger several model requests. Four Sonnet 4.6 requests with the example counts cost $0.78 in model usage. Measure the complete workflow and its accepted results. When task difficulty varies, compare LLM routing with a single-model baseline using the same acceptance criteria.
The formula that matters: cost per completed task
Use this formula before choosing a platform or setting your customer price:
Cost per successfully completed task = total operating cost during the measurement period ÷ accepted completed tasks during that period.
Make failure visible in the cost calculation
Keep all attempts in the numerator, including failures and retries. Count only accepted completions in the denominator. If no task is accepted, cost per accepted completion is undefined; report the spend and failure rather than dividing by an invented success count. Compare the same task mix and quality threshold before choosing a route.
Include platform fees, model usage, tools, retrieval, execution, monitoring, support and human review for all attempts, including failures. If 1,000 attempts cost $400 in total and 700 complete correctly, the cost is about $0.57 per accepted task, not $0.40. Avoid counting retries twice. Add an explicit allocation for initial implementation when estimating fully loaded cost.
Cost per task helps compare the bill. To decide whether that bill creates enough value, use the separate AI agent ROI calculation and pilot scorecard. Keep cost measurement and investment return distinct.
Track at least these six fields for every run:
- task type and customer or workspace;
- model, input tokens, cached tokens and output tokens;
- number and cost of tool calls;
- retries, loop count and stop reason;
- human-review time;
- final status: completed, corrected, escalated or failed.
This telemetry belongs in the first production version. Retrofitting it after customers discover an unlimited plan is expensive.
AI agent implementation cost: hours, roles and scope
Our current role rate card starts at USD 32/hour for frontend engineering and USD 36/hour for backend engineering. Mid starting rates are USD 40/hour for AI automation and USD 48/hour for machine learning and MLOps engineering; Senior and Lead rates are listed in the role rate card. The table illustrates these general engineering roles; scope AI, integration, evaluation and deployment work separately.
| Developer allocation | Hours over four weeks | Frontend from USD 32/hour | Backend from USD 36/hour |
|---|---|---|---|
| 8 hours/week | 32 | from USD 1,024 | from USD 1,152 |
| 20 hours/week | 80 | from USD 2,560 | from USD 2,880 |
| 40 hours/week | 160 | from USD 5,120 | from USD 5,760 |
These are developer-capacity calculations for four weeks, or 28 days, rather than a calendar-month fee or a promise to deliver a complete agent. Agree the engineer, role mix, scope, inclusions and terms in the proposal; runtime and platform costs are additional budget lines.
Break the engineering brief into concrete work: the first workflow and acceptance test, data access and integrations, permissions and approval gates, evaluation, deployment, monitoring and handover. The estimate should state what is delivered at each boundary and what remains for later.
If the workflow is uncertain, begin with a bounded MVP or proof of concept. For production, compare direct APIs, managed platforms and orchestrators against the same operating requirements.

Four ways vendors price AI agents
Compare the billing unit with the work your agent performs. Google Cloud Marketplace’s AI-agent guidance, for example, allows subscription, usage-based and combined pricing. Even a free listing can leave the customer paying for the cloud resources used.
Per seat
Predictable and familiar, but poorly aligned with automated work. It fits assistants whose usage is naturally limited by human users. It is risky when one user can launch thousands of autonomous tasks.
Per task or resolution
A useful model when a completed task is easy to define: a ticket resolved, document processed or lead qualified. It aligns price with value, but requires reliable outcome tracking and rules for partial completion.
Subscription plus usage
A base fee covers access, support and a usage allowance; overages cover variable work. This can make a defined workload predictable while charging separately for additional usage. The allowance must be based on measured task economics rather than a guess.
Outcome-based pricing
Payment is tied to a business result. It can work for narrow, measurable processes, but attribution becomes contentious when the agent is only one part of the outcome. Define the baseline, measurement window and exceptions before using it.
Where AI agent platforms hide cost
Long context. Sending an entire knowledge base with every turn is an architecture shortcut. Test whether retrieval, summarisation or caching reduce total cost without losing required context or quality.

Unbounded loops. Every agent needs limits for steps, tokens, elapsed time and spend. When a limit is reached, the system should stop or ask for human input.
Tool definitions and results. Schemas, browser output and API responses return to the model as context. Tool use therefore creates both a direct charge and additional token usage.
Evaluation. A cheap agent that fails silently is expensive. Budget for test sets, regression checks and sampled human review. The same principle applies to AI code-review systems: the model is only one layer of the production workflow.
Permissions and audit logs. Agents that act need least-privilege credentials, approval gates and traceable decisions. These are engineering requirements, not optional enterprise polish. Our agent security checklist covers permission and approval boundaries. Our guide to adaptive AI architecture explains the monitoring and feedback loops needed for systems that change over time.
How to compare AI agent platform pricing
Ask every vendor for the same workload and the same boundaries. A useful request includes monthly completed tasks, average documents retrieved, tools called, latency target, retention, human-review rate and expected failure handling.
- Request a price for a defined workload, not a generic “agent”.
- Separate platform fees from model and third-party usage.
- Ask whether failed runs, retries and reasoning tokens are billed.
- Confirm export options for prompts, logs, evaluation data and embeddings.
- Model a normal month and a 3× spike.
- Calculate cost per successful task for both scenarios.
If the vendor cannot show usage at task level, the low headline price is not comparable. If you need a system built around your own workflow and data, Powercode Group’s AI and data science team covers discovery, data pipelines, model integration, deployment and monitoring.
When Powercode Group fits the work
Compare a ready-made product first when it covers the workflow and operating requirements. Custom engineering is useful when the agent needs your data, product integrations, permission controls or a delivery model that an existing platform does not provide.
“Scope the agent around one workflow before committing to a platform. […] the important estimate is how much integration, evaluation and handover that workflow needs.”
Bohdan Semenov, Head of Delivery at Powercode Group
Our Qube case describes one senior machine learning architect supplied during July–December 2025. The scope covered chatbot development, data pipelines, cloud deployment, documentation and knowledge transfer. Include those supporting responsibilities when preparing your own brief.
Powercode Group provides software engineering and staffing. Our AI and data science service and AI and machine learning specialists support the implementation and delivery work around a model. Send us the workflow, tools and expected volume to discuss an appropriate scope.
Frequently asked questions
How much does an AI agent cost per month?
Multiply the expected model requests and other billable usage by the selected rates, then add platform access, infrastructure, support and human review. Use the worked example above as a calculation template. For live operations, divide the full operating spend by accepted tasks and count each cost once.
How much does an AI agent cost per hour?
Separate engineering time from runtime usage. For illustration, 100 backend-engineering hours at the starting price of USD 36/hour cost from USD 3,600. That buys backend capacity, not a complete-agent project or a specialist AI quote; agree the engineer, scope and terms in the proposal.
Runtime follows the provider’s billing unit, such as tokens, tool calls, defined outcomes or compute time. Specify usage per task, task volume and retries, then add platform access, infrastructure, monitoring and human review. An agent running for an hour does not consume a fixed amount of those resources. Compare the full cost per accepted task using the formula above.
How much does an AI assistant cost compared with an AI agent?
Compare the actual workflow. An agent that takes actions needs a budget for tool calls, permissions, retries, audit records and failure handling as well as model usage. Those responsibilities determine the extra implementation and operating work.
What is included in AI agent platform pricing?
Check whether the quoted price includes model tokens, tool calls, retrieval, storage, compute, observability, support and overages. Platforms package these differently, so compare a defined workload rather than list prices alone.
Should I price an agent per user or per task?
Per user works for human-paced assistants. Per task is usually safer when automation can run independently. A subscription with an included task allowance and transparent overages combines predictability with protection against extreme usage.
How do I stop an AI agent from creating unexpected costs?
Set maximum steps, tokens, time and spend per task. Route simple work to cheaper models, cache stable context, require approval for consequential actions and alert on changes in cost per successful task.
Is it cheaper to build or buy an AI agent?
Buy when the workflow is standard. Build when proprietary data, deep integrations, differentiated behaviour or unit economics matter enough to justify ownership. Start with a proof of concept before committing to a production architecture.
Sources and price-check date
Checked on 30 October 2026: OpenAI GPT-6.1 Terra, GPT-6.1 Sol, Anthropic API pricing, Fin outcome pricing and Google Cloud Marketplace pricing models. Use the provider’s applicable plan and configuration when preparing a quote.
Powercode Group builds production AI systems and the software around them. If you can describe the task, tools and expected volume, send us the workflow. We will tell you whether it needs custom engineering or whether an existing platform is the better purchase.