Prices per 1M tokens. A dash means no single price is listed, or, under capability, no independent score.

API prices by model
ModelInputCache readOutputCapability (Epoch AI)
Mistral 7BDeprecated$0.15No single price$0.20No independent capability score

Rates, billing conditions and sources

Mistral 7B

Deprecated by provider · still listed · price checked Nov 12, 2026 (deprecation notice ↗)

All rates, conditions and sources

Conditions of every rate below:

  • Listed for model "Mistral 7B" (provider "Mistral") in us-east-1 with no service_tier attribute (feature "On-demand Inference"), as one USD price dimension from 0 to Inf.
  • AWS lists this price in USD per 1K tokens (unit "1K tokens"); it is multiplied by 1,000 exactly, by decimal arithmetic, to give USD per 1M tokens.
  • AWS's on-demand price for this model with no service tier stated: the row carries no service_tier attribute, so it is not labelled as the standard or any other tier. Only this plain on-demand usagetype in us-east-1 is published: any flex, priority, batch, latency-optimized, custom-model or cross-region (global) variant, other AWS Regions, provisioned throughput and model customization are excluded. The offer file lists no cache price for this model without a service tier; missing cache prices are unknown, not zero.

Input: $0.15 per 1M tokens · Region: us-east-1

  • AWS Price List Bulk API offer file for Amazon Bedrock in US East (N. Virginia) (pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonBedrock/current/us-east-1/index.json), on-demand (OnDemand) term of usagetype USE1-Mistral7B-input-tokens.
  • Input tokens.

Output: $0.20 per 1M tokens · Region: us-east-1

  • AWS Price List Bulk API offer file for Amazon Bedrock in US East (N. Virginia) (pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonBedrock/current/us-east-1/index.json), on-demand (OnDemand) term of usagetype USE1-Mistral7B-output-tokens.
  • Output tokens.

Price observed:

API availability: listed as available when checked (not a live service check)

Collection record

Primary source ↗ · provider documentation · Claims: bedrock-mistral-7b: availability · Retrieved · Checked · Reviewed · Review due · Freshness: unknown · Confidence: A

  • Official Amazon Bedrock model card for Mistral 7B Instruct, Model ID mistral.mistral-7b-instruct-v0:2, raw SHA-256 0d5f00e268659191bcf6f7eeb4cfb2f75d6de4d394cbf540a45e2e191f5c3670, read once at 2026-11-02T11:40:22Z under the #837 AWS facts-plus-link basis: "Model lifecycle: Legacy"; "Model EOL date: March 30, 2027"; "Model lifecycle policy: Model lifecycle (For Models Launched Prior to Sept 7 2026)".
  • Amazon Bedrock "Model lifecycle (Legacy)" page (https://docs.aws.amazon.com/bedrock/latest/userguide/model-lifecycle-legacy.html), read once at 2026-11-02T11:37:59Z, raw SHA-256 c33d9d25d7da7f47c098aa864830361de770224f38a790070bada021dac56850: its Legacy table lists Mistral 7B Instruct (mistral.mistral-7b-instruct-v0:2) with Legacy date September 30, 2026, EOL date March 30, 2027 and public extended access start date "To be announced". The page states: "New customers can't use Legacy models and existing customers may lose access to Legacy models after 15 days of inactivity."
  • That table row's Regions (ap-south-1, ap-southeast-2, ca-central-1, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-west-2) include us-east-1, the region this offer is published for.
  • Availability stays available: the us-east-1 price list still lists an on-demand price (2026-11-06 archive), and the page says "you can continue to use a Legacy model during this period" (the Legacy period before the EOL date), though not as a new customer. The EOL date is in the future, so no retirement is recorded; reviewAfter is the EOL date, a re-review date, not a retirement.
  • Reviewed by Claude (owner delegation 2026-09-27), #863.

Raw API evidence ↗ · provider API · Claims: bedrock-mistral-7b: pricing · bedrock-mistral-7b: availability · 122 more claims about 61 other catalog entries · Retrieved · Checked · Review due · Confidence: A

  • Raw SHA-256: f1ac6a175fb27b3ad80d2c5d8970be8c2e5f957906349e52d15ec11d43e97896; collector aws-bedrock-price-list-json-1.
  • AWS Price List Bulk API offer file for Amazon Bedrock (us-east-1): offer version 20261111013037, publicationDate 2026-11-11T01:30:37Z.
  • Reviewed on-demand token prices only: each curated model's exact usagetypes in us-east-1, with service_tier "standard" for standard-tier models and with no service_tier attribute for the reviewed untiered models, in US dollars as the offer file states them (hence confidence A). A hosted listing and pricing observation only: no checkpoint, developer, license, context-window, modality or release-date assertions, and the usagetype is not a documented Bedrock model ID.
  • No Anthropic Claude price is published from this offer file: prices are read only from curated usagetypes, and no curated entry is an Anthropic model. (When the collector was reviewed on 2026-10-29, the file listed only legacy Claude models, all without a service tier.)
  • Availability rests on AWS's own offer file listing an on-demand price for the model in us-east-1.
About capability scores (Epoch AI)

Capability scores: Epoch AI, 'Capabilities & benchmarking'. Published online at epoch.ai. Retrieved from 'https://epoch.ai/benchmarks' [online resource], epoch.ai/benchmarks. Accessed Nov 18, 2026. Licensed CC BY 4.0; values here are rounded to one decimal place and grouped into bands.

The Epoch Capabilities Index (ECI) combines many benchmarks on a scale where Claude 3.5 Sonnet is 130 and GPT-5 is 150. Bands, on the displayed one-decimal score: Frontier 160+, Strong 150–159.9, Capable 140–149.9, Entry below 140. Each score has a 90% range, listed with each model's rates and sources; a range that crosses a band boundary is flagged there. Models are not ranked: neighbouring scores often overlap.

A benchmark is not your workload. Epoch's scores mostly reflect runs at the highest reasoning effort, which use more output tokens than default settings. Scores are dated and can shift between Epoch releases. A score belongs to the developer's model; a host listing shows the same model's score, but hosts may serve different versions or quantizations.

How headline rates are chosen

Headline rates use the directory's shared rule: the rate a buyer meets by default, chosen by billing, tier and context dimensions and never by price. Context caps, the bracket starting at zero and short-context variants are labeled. Every price is a listed price, not a service guarantee; each offer's details say what its source states about availability. Batch, off-peak and other variants remain in the details; where no single rate is the default, the table shows a dash.

No currency conversion is performed. Missing cache prices are unknown, not zero. Equal units do not establish equivalent models or service conditions. See the methodology and source register.