Claude 4.1 Opus: API Provider Benchmarking & Analysis
Anthropic has launched a newer model, Claude Opus 4.5, we suggest considering this model instead.
For more information, see Comparison of Claude Opus 4.5 to other models and API provider benchmarks for Claude Opus 4.5.
Comparison Summary
Google Vertex (49 t/s) and 
Azure (47 t/s) are the fastest providers of Claude 4.1 Opus, followed by Anthropic (47 t/s) & 
Amazon (22 t/s).Latency (TTFT): Anthropic (1.22s) and Google Vertex (1.34s) have the lowest latency for Claude 4.1 Opus, followed by Azure (1.57s) & Amazon (2.89s).Blended Price ($/M tokens): Anthropic ($30.00) and Google Vertex ($30.00) are the most cost-effective providers for Claude 4.1 Opus, followed by Amazon ($30.00) & Azure ($30.00).Input Token Price: Anthropic ($15.00) and Google Vertex ($15.00) offer the lowest input token prices for Claude 4.1 Opus, followed by Amazon ($15.00) & Azure ($15.00).Output Token Price: Anthropic ($75.00) and Google Vertex ($75.00) offer the lowest output token prices for Claude 4.1 Opus, followed by Amazon ($75.00) & Azure ($75.00).Highlights
Pricing
Pricing: Input and Output Prices: Claude 4.1 Opus Providers
Price per token included in the request/message sent to the API, represented as USD per million Tokens.
Price per token generated by the model (received from the API), represented as USD per million Tokens.
Speed vs. Price: Claude 4.1 Opus Providers
Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).
Price per token, represented as USD per million Tokens. Price is a blend of Input & Output token prices (3:1 ratio).
Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.
Speed
Measured by Output Speed (tokens per second)
Output Speed: Claude 4.1 Opus Providers
Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).
Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.
Latency vs. Output Speed: Claude 4.1 Opus Providers
Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).
Time to first token received, in seconds, after API request sent. For reasoning models which share reasoning tokens, this will be the first reasoning token. For models which do not support streaming, this represents time to receive the completion.
Price per token, represented as USD per million Tokens. Price is a blend of Input & Output token prices (3:1 ratio).
Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.
Latency
Measured by Time (seconds) to First Token
Time to First Answer Token: Claude 4.1 Opus Providers
Time to first answer token received, in seconds, after API request sent. For reasoning models, this includes the 'thinking' time of the model before providing an answer. For models which do not support streaming, this represents time to receive the completion.
Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.
End-to-End Response Time
Seconds to output 500 Tokens, calculated based on time to first token, 'thinking' time for reasoning models, and output speed
End-to-End Response Time: Claude 4.1 Opus Providers
Seconds to receive a 500 token response. Key components:
- Input time: Time to receive the first response token
- Thinking time (only for reasoning models): Time reasoning models spend outputting tokens to reason prior to providing an answer. Amount of tokens based on the average reasoning tokens across a diverse set of 60 prompts (methodology details).
- Answer time: Time to generate 500 output tokens, based on output speed
For fair comparison, the number of reasoning tokens is standardized across all providers for each model based on the model's representative query token counts.
Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.
API Features
Function (Tool) Calling & JSON Mode: Claude 4.1 Opus Providers
Indicates whether the provider supports function calling in their API. Function calling is also known as 'Tool Calling'.
Indicates whether the provider supports JSON mode in their API. When JSON mode is enabled, the models will always return a valid JSON object.
Context Window: Claude 4.1 Opus Providers
Maximum number of combined input & output tokens. Output tokens commonly have a significantly lower limit (varied by model).
While models have their own context window, in cases this is limited by providers.