Amazon API Cost Calculator

How much does the Amazon API cost per month?

For Amazon Nova Micro at 200K requests/month, 2,400 input tokens and 350 output tokens per request costs about $12.12 per month after 30% cache use and 100% batch share. Across Amazon's 3 priced models, the cheapest default ranking is Amazon Nova Micro at $24.25 per month.

Verified 2026-06-21

Pricing data as of June 2026. Sources: Amazon pricing and model documentation. Parameters are shareable in this URL.

Amazon Nova Micro: estimated monthly cost

$12.12

Formula: provider-specific cached input multiplier × cache rate, plus uncached input and verbosity-adjusted output; cache writes are amortised over the provider TTL, then batch savings are applied.

Per request$0.000
Per day$0.404
Per month$12.12
Per year$145

OpenAI scenario sensitivity

The default is a server-rendered estimate. Change the cache and batch shares to see when a cheaper qualified model overtakes the selected model; the URL is shareable and preserves the inputs.

Default$12.12/month
No caching or batch$24.25/month
50% cache, 50% batch$18.19/month
100% cache, 100% batch$12.12/month

Batch 11 Amazon Nova workload decision depth

1. Token invoice plus AWS overhead ceiling

Ancillary overheadToken billAll-in scenarioChoice boundary
0%$26.60$26.60Guardrail + KB + orchestration + transfer are user-supplied overhead
10%$26.60$29.26Guardrail + KB + orchestration + transfer are user-supplied overhead
50%$26.60$39.90Guardrail + KB + orchestration + transfer are user-supplied overhead
100%$26.60$53.20Guardrail + KB + orchestration + transfer are user-supplied overhead

2. On-demand versus batch mix

Eligible async shareMonthly billSavingsCollection constraint
0%$26.60$0.0000Converse/on-demand
25%$23.27$3.32Bedrock batch collection later
50%$19.95$6.65Bedrock batch collection later
100%$13.30$13.30Bedrock batch collection later

3. Nova accepted-result frontier

ModelToken billRequired quality upliftWindow/modality
Amazon Nova Micro$26.60User-supplied uplift/retry; formula = bill ÷ success rateExclude unsupported window/modality; otherwise Unavailable
Amazon Nova Lite$45.60User-supplied uplift/retry; formula = bill ÷ success rateExclude unsupported window/modality; otherwise Unavailable
Amazon Nova Pro$608.00User-supplied uplift/retry; formula = bill ÷ success rateExclude unsupported window/modality; otherwise Unavailable

Provenance: Batch 11 Amazon Bedrock invoice/mix/frontier module; selected model Amazon Nova Micro; inputs are 2,400 input tokens, 350 output tokens, 200,000 calls/month, cache rate 30%, batch share 100%. Verified 2026-06-21. Provider source: https://aws.amazon.com/bedrock/pricing/ · Run this scenario →

Batch 59 · server-rendered evidence boards · verified 2026-09-07

Intent answer: Amazon Bedrock Nova models offer aggressive price-performance within the AWS ecosystem (Micro, Lite, Pro). Modeling requires accounting for on-demand token pricing, provisioned throughput, and cross-region inference. Verified 2026-09-07.

Demand evidence: Qualitative demand: Amazon Bedrock pricing calculators reviewed 2026-09-07; exact US monthly volume is unavailable.

Scope boundary: Calculate AWS Amazon Bedrock Nova model API token expenses across Nova Pro, Nova Lite, and Nova Micro with Bedrock infrastructure overhead. Exact joins required; unresolved joins render Unavailable.

Amazon Nova tier selection economics matrix

Deterministic formula / rule: nova_monthly = sum(calls * (in_tokens * rate_tier_in + out_tokens * rate_tier_out)); Micro vs Lite vs Pro.

Boundary: Owns Nova family model tiering economics.

Frozen scenario / field IDExact identity and evidence fieldsResultState
batch59-calc-amazon-m1-r1
high-volume text classification (Nova Micro)
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$high-volume text classification (Nova Micro); task description; recommended Nova model; input rate ($/M); output rate ($/M); monthly cost; relative savings vs Pro; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 1 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m1-r2
agentic customer workflow (Nova Lite)
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$agentic customer workflow (Nova Lite); task description; recommended Nova model; input rate ($/M); output rate ($/M); monthly cost; relative savings vs Pro; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 1 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m1-r3
deep reasoning and multimodal task (Nova Pro)
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$deep reasoning and multimodal task (Nova Pro); task description; recommended Nova model; input rate ($/M); output rate ($/M); monthly cost; relative savings vs Pro; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 1 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m1-r4
real-time translation pipeline
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$real-time translation pipeline; task description; recommended Nova model; input rate ($/M); output rate ($/M); monthly cost; relative savings vs Pro; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 1 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m1-r5
batch data processing job
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$batch data processing job; task description; recommended Nova model; input rate ($/M); output rate ($/M); monthly cost; relative savings vs Pro; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 1 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m1-r6
unsupported Bedrock model ID
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$unsupported Bedrock model ID; task description; recommended Nova model; input rate ($/M); output rate ($/M); monthly cost; relative savings vs Pro; verified=2026-09-07Unavailable — exact calc-amazon evidence join is not closed for "unsupported Bedrock model ID"FAIL CLOSED — manual, probe, or source evidence required

First-party citation: AWS Bedrock pricing documentation. Verified 2026-09-07; missing or conflicting joins fail closed.

Bedrock on-demand vs provisioned throughput evaluator

Deterministic formula / rule: break_even_hours = commitment_cost / (hourly_tokens * on_demand_rate); provisioned throughput crossover.

Boundary: Owns AWS commitment planning for Nova.

Frozen scenario / field IDExact identity and evidence fieldsResultState
batch59-calc-amazon-m2-r1
bursty developmental workload
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$bursty developmental workload; average hourly tokens; peak concurrency; on-demand cost; model unit commitment cost; break-even utilization %; deployment mode recommendation; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 2 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m2-r2
predictable 24/7 production traffic
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$predictable 24/7 production traffic; average hourly tokens; peak concurrency; on-demand cost; model unit commitment cost; break-even utilization %; deployment mode recommendation; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 2 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m2-r3
seasonal retail peak event
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$seasonal retail peak event; average hourly tokens; peak concurrency; on-demand cost; model unit commitment cost; break-even utilization %; deployment mode recommendation; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 2 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m2-r4
nightly batch processing window
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$nightly batch processing window; average hourly tokens; peak concurrency; on-demand cost; model unit commitment cost; break-even utilization %; deployment mode recommendation; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 2 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m2-r5
multi-region failover reserve
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$multi-region failover reserve; average hourly tokens; peak concurrency; on-demand cost; model unit commitment cost; break-even utilization %; deployment mode recommendation; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 2 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m2-r6
unsupported commitment tier
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$unsupported commitment tier; average hourly tokens; peak concurrency; on-demand cost; model unit commitment cost; break-even utilization %; deployment mode recommendation; verified=2026-09-07Unavailable — exact calc-amazon evidence join is not closed for "unsupported commitment tier"FAIL CLOSED — manual, probe, or source evidence required

First-party citation: AWS Bedrock pricing documentation. Verified 2026-09-07; missing or conflicting joins fail closed.

Bedrock cross-region inference & egress receipt

Deterministic formula / rule: total_aws_spend = token_cost + cross_region_data_transfer + cloudwatch_logging_overhead.

Boundary: Owns AWS infrastructural cost additions to model inference.

Frozen scenario / field IDExact identity and evidence fieldsResultState
batch59-calc-amazon-m3-r1
single-region us-east-1 standard
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$single-region us-east-1 standard; token charges; data transfer add-on; monitoring overhead; security boundary cost; total AWS bill estimate; optimization lever; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 3 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m3-r2
cross-region inference profile
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$cross-region inference profile; token charges; data transfer add-on; monitoring overhead; security boundary cost; total AWS bill estimate; optimization lever; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 3 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m3-r3
high-compliance isolated VPC endpoint
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$high-compliance isolated VPC endpoint; token charges; data transfer add-on; monitoring overhead; security boundary cost; total AWS bill estimate; optimization lever; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 3 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m3-r4
verbose CloudWatch prompt logging
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$verbose CloudWatch prompt logging; token charges; data transfer add-on; monitoring overhead; security boundary cost; total AWS bill estimate; optimization lever; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 3 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m3-r5
S3 batch input/output storage
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$S3 batch input/output storage; token charges; data transfer add-on; monitoring overhead; security boundary cost; total AWS bill estimate; optimization lever; verified=2026-09-07Unavailable — frozen calc-amazon fixture requires an exact source, identity, and result receiptUNTESTED — module 3 rule is reproducible but no production observation is claimed
batch59-calc-amazon-m3-r6
unresolved AWS account tier
route=$/llm-cost-calculator/amazon; owner=$calc-amazon; scenario=$unresolved AWS account tier; token charges; data transfer add-on; monitoring overhead; security boundary cost; total AWS bill estimate; optimization lever; verified=2026-09-07Unavailable — exact calc-amazon evidence join is not closed for "unresolved AWS account tier"FAIL CLOSED — manual, probe, or source evidence required

First-party citation: Amazon Bedrock Nova model guide. Verified 2026-09-07; missing or conflicting joins fail closed.

Method and limitations: this board exposes deterministic rules, first-party citations, and dated evidence identities. It does not invent volume, coverage, entitlement, retention, residency, quota, capacity, feature support, quality, price, reliability, or legal conclusions. Run the calc-amazon evidence flow →

Ranked cost — 200K requests/month

ModelProviderList monthlyEffective monthlyVerbosityRank Δ
Amazon Nova MicrobudgetAmazon$26.60$12.120.76×
Amazon Nova LitebudgetAmazon$45.60$22.040.91×
Amazon Nova PromidAmazon$608$304

Levers live on Amazon

Batch API: up to 50%Model verbosity: up to 95%Context trimming: up to 47%

The billing gotcha

Amazon Nova is billed through AWS Bedrock rather than a standalone Nova account: the token estimate below covers model input and output charges, while your real invoice can also include regional AWS data-transfer, guardrail, knowledge-base, or orchestration costs. Nova's batch discount applies to eligible asynchronous Bedrock jobs, so selecting a batch share is only realistic when your application can submit and collect work later instead of waiting on Converse synchronously.

Related

Amazon provider profile →Compare against another provider →Global cost calculator →How to reduce LLM API costs →