Model Pricing API¶

Query the exact AWS unit prices for one or more models, straight from the same AWS Price List catalog the server uses for request cost tracking. Purpose-built for cost-aware model selection: shortlist models with search_models, then compare their price cards in one call.

Quick Start¶

How It Works¶

Each returned row is one published AWS price: a billed dimension (same vocabulary as the request-log usage entries) plus its published variants — service tier, prompt-cache write TTL, serving profile, media spec, and long-context bucket. unit_price is an exact decimal string per one billed unit (token, image, second, character, request, search unit).

By default the card reflects your server's configuration: only the configured Bedrock regions, each model's default service tier, and its effective serving profile (routing) are returned, with the same fallbacks billing applies (a tier or routing without a distinct published rate falls back to the standard/plain row). Pass all_prices=true for the full published price table, and explicit region/tier/routing filters to override any axis in either mode.

Prices are indexed eagerly: models not currently accessible to your account can still be priced. An empty prices list means AWS publishes no rows for that model (or none match the filters). A missing variant row means AWS publishes no distinct rate for it — billing then falls back the same way cost tracking does.

The endpoint is a pure in-memory read of the loaded catalog — no AWS call at request time. It requires cost tracking to be enabled (COST_TRACKING=true), and returns a retry-later 503 while the catalog is still loading after startup.

Query Parameters¶

All parameters are optional and combine with AND logic.

Response Fields¶

One ModelPricing object per requested model, in request order (duplicates removed); with no model filter, one per available model, sorted by ID:

Each row in prices (axes are omitted when not applicable):

Examples¶

Base price card of a shortlist:

curl -G "$BASE/model_pricing" \
  --data-urlencode "model=anthropic.claude-sonnet-4-5-20250929-v1:0" \
  --data-urlencode "model=amazon.nova-pro-v1:0" \
  --data-urlencode "variants=false" \
  -H "Authorization: Bearer $API_KEY"

Base price card of every available model:

curl -G "$BASE/model_pricing" \
  --data-urlencode "variants=false" \
  -H "Authorization: Bearer $API_KEY"

Token rates in one region:

curl -G "$BASE/model_pricing" \
  --data-urlencode "model=amazon.nova-pro-v1:0" \
  --data-urlencode "region=us-east-1" \
  --data-urlencode "dimension=input_tokens" \
  --data-urlencode "dimension=output_tokens" \
  -H "Authorization: Bearer $API_KEY"

Response (trimmed):

[
  {
    "id": "amazon.nova-pro-v1:0",
    "service": "bedrock-runtime",
    "default_tier": "standard",
    "default_routings": ["us"],
    "prices": [
      {"region": "us-east-1", "dimension": "input_tokens", "tier": "standard", "routing": "us", "unit_price": "0.0000008", "currency": "USD"},
      {"region": "us-east-1", "dimension": "output_tokens", "tier": "standard", "routing": "us", "unit_price": "0.0000032", "currency": "USD"}
    ]
  }
]

Status Codes¶

Using model_pricing as an MCP Tool¶

When MCP is enabled, model_pricing is exposed as an MCP tool under the same name. The intended agent workflow:

1. Call search_models to shortlist model IDs for the task.
2. Call model_pricing with the shortlist and compare.
3. Keep responses small: use variants=false and dimension filters.

{
  "tool": "model_pricing",
  "arguments": {
    "model": ["anthropic.claude-sonnet-4-5-20250929-v1:0", "amazon.nova-pro-v1:0"],
    "variants": false,
    "dimension": ["input_tokens", "output_tokens"]
  }
}