Amazon Bedrock AgentCore Pricing
Pay only for what you use
Amazon Bedrock AgentCore offers flexible, consumption-based pricing with no upfront commitments or minimum fees. Each feature can be used independently or together, and you pay only for what you use. This modular approach allows you to start small and scale as your agent applications grow.
AgentCore features
Open all- No upfront resource selection required
- Billing is calculated per second, using actual CPU consumption and peak memory consumed up to that second, with a 1-second minimum
- You only pay for actual resource consumption during your session, which spans from microVM boot, initialization, active processing, idle periods, until session termination (microVM shutdown)
- Billing includes system overhead in addition to your application's resource usage
- 128MB minimum memory billing applies for memory
- Storage costs: Container deployment requires ECR storage (billed separately). Direct code deployment bills you for the size of the code artifacts you deployed at S3 Standard rates.
- Network data transfer charges apply at standard EC2 rates
AgentCore Runtime is a secure, serverless runtime purpose-built for deploying and scaling agents and tools. Choose between direct code deployment for rapid iteration or container-based deployment for maximum control. AgentCore Runtime is built on microVMs (serverless, consumption-based).
microVMs: you only pay for the active resources you consume
Unlike traditional compute services that charge for pre-allocated resources (i.e., fixed instance size and cost per second while hosting the agent), with AgentCore Runtime you only pay for active resource consumption. This delivers substantial cost savings for agentic workloads, which typically spend 30-70% of time in I/O wait (waiting for LLM responses, tool / API calls, or database queries). With pre-allocated pricing, you would pay for idle CPU during these wait periods. With the active resource consumption-based pricing in AgentCore Runtime, I/O wait and idle time is free, if no other background process is running.
Billing is based on CPU and memory consumption across your session lifetime, calculated at per-second increments. For CPU resources, you are charged based on actual consumption - if your agent consumes no CPU during I/O wait, there are no CPU charges. For memory resources, you're charged for the peak memory consumed up to that second.
Key details:
- No upfront resource selection required
- Billing is calculated per second, using actual CPU consumption and peak memory consumed up to that second, with a 1-second minimum
- You only pay for actual resource consumption during your session, which spans from microVM boot, initialization, active processing, idle periods, until session termination (microVM shutdown)
- Billing includes system overhead in addition to your application's resource usage
- 128MB minimum memory billing applies for memory
- Storage costs: Browser Profiles require Amazon S3 storage for storing profile artifacts (cookies, local storage) and you will get billed at Amazon S3 Standard rates.
- Network data transfer charges apply at standard EC2 rates.
AgentCore Browser provides a fast, secure, cloud-based browser runtime to enable agents to interact with websites at scale.
You only pay for the active resources you consume
Unlike traditional compute services that charge for pre-allocated resources (i.e., fixed instance size and cost per second while hosting the agent), with AgentCore Browser you only pay for active resource consumption. This delivers substantial cost savings for agentic workloads, which typically spend 30-70% of time in I/O wait (waiting for LLM responses, tool / API calls, or database queries). With pre-allocated pricing, you would pay for idle CPU during these wait periods. With the active resource consumption-based pricing in AgentCore Browser, I/O wait and idle time is free, if no other background process is running.
Billing is based on CPU and memory consumption across your session lifetime, calculated at per-second increments. For CPU resources, you are charged based on actual consumption - if your agent consumes no CPU during I/O wait, there are no CPU charges. For memory resources, you're charged for the peak memory consumed up to that second.
Key details:
- No upfront resource selection required
- Billing is calculated per second, using actual CPU consumption and peak memory consumed up to that second, with a 1-second minimum
- You only pay for actual resource consumption during your session, which spans from microVM boot, initialization, active processing, idle periods, until session termination (microVM shutdown)
- Billing includes system overhead in addition to your application's resource usage
- 128MB minimum memory billing applies for memory
- Network data transfer charges apply at standard EC2 rates
AgentCore Code Interpreter enables agents execute code securely in sandbox environments, enhancing their accuracy and expanding their ability to solve complex end-to-end tasks.
You only pay for the active resources you consume
Unlike traditional compute services that charge for pre-allocated resources (i.e., fixed instance size and cost per second while hosting the agent), with AgentCore Code Interpreter you only pay for active resource consumption. This delivers substantial cost savings for agentic workloads, which typically spend 30-70% of time in I/O wait (waiting for LLM responses, tool / API calls, or database queries). With pre-allocated pricing, you would pay for idle CPU during these wait periods. With the active resource consumption-based pricing in AgentCore Code Interpreter, I/O wait and idle time is free, if no other background process is running.
Billing is based on CPU and memory consumption across your session lifetime, calculated at per-second increments. For CPU resources, you are charged based on actual consumption - if your agent consumes no CPU during I/O wait, there are no CPU charges. For memory resources, you're charged for the peak memory consumed up to that second.
Key details:
- No upfront costs or minimum commitments required
- Network data transfer charges apply at standard EC2 rates
- There are no extra charges for customer-defined rate limiting
Amazon Bedrock AgentCore Gateway enables agents to securely access tools, models, and other agents.
Consumption-based pricing
You pay only for the API calls made to Gateway. You're charged based on the number of operations (such as listing available actions, invoking actions, and health checks) and targets indexed for semantic search functionality.
Key details:
- No minimum fees and no upfront commitments
- Billing is calculated per successful OAuth token or API key requested to perform a task requiring authorization for a non-Amazon Web Services resource
- No additional charges incurred when customers use AgentCore Identity through AgentCore Runtime or AgentCore Gateway
AgentCore Identity simplifies agent identity and access management and allows your agents to securely access Amazon Web Services resources and services on behalf of users or by themselves with pre-authorized user consent.
Consumption-based pricing
Customers who use AgentCore Identity through either AgentCore Runtime or AgentCore Gateway, do not incur any additional charges for their use of AgentCore Identity. For all other scenarios, you pay for only what you use and are charged based on the number of requests from the agent to AgentCore Identity for an OAuth token or an API key.
Key details:
AgentCore Observability gives developers complete visibility into agent workflows to trace, debug, and monitor agents' performance in production environments.
Consumption-based pricing
You pay as you go for telemetry generated, stored, and queried for your agents. The telemetry data is ingested and stored in your Amazon CloudWatch account. You are charged for data ingestion and storage, queries to retrieve and analyze information, and masking of sensitive/Personally Identifiable Information (PII) data in logs. To review pricing details visit Amazon CloudWatch pricing page.
Pricing Table
| Service/Capability | Resource | Price |
| Runtime microVMs | v2 CPU | ¥0.866904192 per vCPU-hour |
| v2 Memory | ¥0.114817248 per GB-hour | |
| Browser Tool | CPU | ¥0.60805584 per vCPU-hour |
| Memory | ¥0.064202544 per GB-hour | |
| Code Interpreter | CPU | ¥0.60805584 per vCPU-hour |
| Memory | ¥0.064202544 per GB-hour | |
| Gateway | API Invocations (e.g. ListTools, InvokeTool, Ping) | ¥0.0339696 per 1,000 invocations |
| Identity | Token or API key requests for non-Amazon Web Services resources | ¥0.0679392 per 1,000 token or API keys requested by the agent |
| (Note: AgentCore Identity is available at no additional charge to customers when they use it through either AgentCore Runtime or AgentCore Gateway) | ||
| Observability | Spans, logs, and metrics | Charged as per Amazon CloudWatch pricing |