Amazon Bedrock AgentCore pricing calculator

Runtime, Gateway, Memory & Policy Costs. Estimate your costs using AWS list prices.

Estimates from AWS list prices, not an AWS quote. Discounts, taxes and credit terms may affect your bill.

01 · How Amazon Bedrock AgentCore pricing works

What you pay for

Runtime, Browser and Code Interpreter: per vCPU-hour ($0.0895) and GB-hour ($0.00945), billed per second on active consumption.
Gateway: per 1,000 tool API calls ($0.005), search calls ($0.025) and tool indexing.
Memory: short-term events ($0.25 per 1,000), long-term records stored per month and retrievals.
Identity token/API-key requests (bundled when used through Runtime or Gateway), Policy authorisation requests, Evaluations; model tokens billed by Bedrock; observability by CloudWatch.

Common cost traps

Model tokens, not AgentCore, are usually the largest part of an agent bill.
Long-running sessions that keep memory allocated bill GB-hours for the whole session.
Each memory event and retrieval is charged; agents that log every step can multiply memory charges.
CloudWatch observability (spans, logs) adds its own cost.

Ways to reduce cost

Keep sessions short and end them explicitly.
Store only useful facts in long-term memory and batch short-term events.
Use Gateway semantic search only when the tool catalogue is large.
Pair with small Bedrock models for routing and tool selection.

Free Tier & account eligibility

Free Tier depends on account age. Accounts created on or after 15 July 2025 get a $100 sign-up credit plus up to $100 more for completing onboarding activities; on the Free plan these last 6 months (or until used up), on the Paid plan unused Free Tier credits stay usable for 12 months from sign-up. Accounts created before 15 July 2025 keep the legacy Free Tier (12-month offers plus always-free offers). Always-free offers apply on both plans. No AgentCore Free Tier allowance in the data; accounts on the new plans can pay from Free Tier credits.

02 · AWS credits & runway

Do credits cover Amazon Bedrock AgentCore?

AgentCore Runtime, Gateway, Memory, Identity, Browser, Code Interpreter, Policy and Evaluations usage is billed by AWS and is offset by credits. Model calls made by agents are billed by Bedrock (or the external provider) and follow those rules. General rules: credits only offset charges from the billing cycle in which they were applied onward (never past bills), they apply only to the services listed on the credit in Billing and Cost Management > Credits, they expire on the date shown there, and accounts on the AWS Free plan cannot receive Activate credits until they upgrade to the Paid plan.

Check my credits

Excluded charges & conditions

Model or tool charges from non-AWS providers your agent calls.
Upfront payments for Savings Plans and Reserved Instances (All Upfront, and the upfront part of Partial Upfront). The recurring hourly fee of a No Upfront commitment is billed as normal usage and can be offset.
AWS Marketplace charges (Activate credits make an exception for third-party foundation models used through Amazon Bedrock).
AWS Enterprise Support, Enterprise On-Ramp, Unified Operations, resold support and partner-led support.
Amazon Route 53 domain name registration and transfer fees.
Taxes (sales, use, VAT and similar), AWS Professional Services, Training and Certification, Mechanical Turk, AWS Managed Services, and any use for cryptocurrency mining.

Illustrative credit runway

Single-service examples from the supplied data, not your calculator result. Months = credit amount ÷ monthly cost, before credit expiry. Credits can expire before these theoretical months are used; coverage and other AWS services can shorten runway.

Estimated months before expiry limits, by credit amount
Usage profile	Monthly estimate	$10,000	$25,000	$100,000
Small	$18.92	528.5 mo.	1,321.4 mo.	5,285.4 mo.
Medium	$891.80	11.2 mo.	28.0 mo.	112.1 mo.
Large	$11,418.00	0.9 mo.	2.2 mo.	8.8 mo.

Small profile assumptions

Runtime averaging 0.5 vCPU and 1 GB active for 100 hours/month, 200k Gateway calls, 50k memory events | Runtime CPU: 50 vCPU-hours x $0.0895 = $4.47; Runtime memory: 100 GB-hours x $0.00945 = $0.95; Gateway API calls: 200 1K calls x $0.005 = $1.00; Short-term memory events: 50 1K events x $0.25 = $12.50 | Total ~$18.92/month, us-east-1 on-demand list prices, before Free Tier, taxes and support.

Medium profile assumptions

Runtime 1 vCPU / 2 GB active for 2,000 hours, 5 M Gateway calls, 1 M memory events, 200k long-term records, 500k retrievals | Runtime CPU: 2,000 vCPU-hours x $0.0895 = $179.00; Runtime memory: 4,000 GB-hours x $0.00945 = $37.80; Gateway API calls: 5,000 1K calls x $0.005 = $25.00; Short-term memory events: 1,000 1K events x $0.25 = $250.00; Long-term memory storage: 200 1K records-month x $0.75 = $150.00; Long-term retrievals: 500 1K x $0.5 = $250.00 | Total ~$891.80/month, us-east-1 on-demand list prices, before Free Tier, taxes and support.

Large profile assumptions

Runtime 20,000 vCPU-hours and 40,000 GB-hours, 50 M Gateway calls, 10 M memory events, 2 M long-term records, 10 M retrievals | Runtime CPU: 20,000 vCPU-hours x $0.0895 = $1,790.00; Runtime memory: 40,000 GB-hours x $0.00945 = $378.00; Gateway API calls: 50,000 1K calls x $0.005 = $250.00; Short-term memory events: 10,000 1K events x $0.25 = $2,500.00; Long-term memory storage: 2,000 1K records-month x $0.75 = $1,500.00; Long-term retrievals: 10,000 1K x $0.5 = $5,000.00 | Total ~$11,418.00/month, us-east-1 on-demand list prices, before Free Tier, taxes and support.

04 · Questions

Amazon Bedrock AgentCore pricing FAQ

How is AgentCore Runtime billed?

Per second of active CPU (vCPU-hours) and memory (GB-hours). AWS states CPU is not billed while an agent waits on I/O such as model responses; memory is billed while allocated.

Are model tokens included?

No. Model calls are billed by Bedrock or the external provider you call.

Do credits cover AgentCore?

Yes for AgentCore charges. Third-party model charges follow Bedrock and Marketplace rules.

What does Memory cost?

Short-term events are $0.25 per 1,000; long-term memory is charged per 1,000 records stored per month and per 1,000 retrievals.

05 · Sources & estimate notes

Content pack dated 2026-10-19. Calculator rates remain their existing snapshots; this content update is not a price refresh.

Verification notes

The CPU-not-billed-during-I/O-wait behaviour is from AWS launch material; confirm on the current pricing page.
The data also lists a "runtime v2" rate ($0.1276 per vCPU-hour); which rate applies to which runtime is unclear.
Runway prices come from the calculator repository snapshot rate card agentcore (no AWS Price List mapping in the build). Confirm the main unit prices on https://aws.amazon.com/bedrock/agentcore/pricing/ before publishing.