Multiverse Computing logo
Multiverse Computing
•

Proprietary model

•

Released August 2026

Quasar 438B API Provider Benchmarking & Analysis

Model Comparison

This analysis is intended to support you in choosing the best API provider of Quasar 438B for your use-case.

Fastest

#1
Multiverse ComputingMultiverse Computing
182.7 t/s

Output speed

Total 1 provider

Lowest Latency

#1
Multiverse ComputingMultiverse Computing
12.03 s

Time to first answer token

Total 1 provider

Lowest Price

#1
Multiverse ComputingMultiverse Computing
$0.72

Blended price (per 1M tokens)

Total 1 provider

Quasar 438B is available through Multiverse Computing.

Highlights

Speed

Output tokens per second · Higher is better

End-to-End Response Time

Seconds · Lower is better

Price

USD per 1M tokens (blended) · Lower is better

Update: Default performance benchmarking workload has updated to 10k input tokens to better reflect production use cases. You can still select different workloads above.

Pricing

Pricing: Cache Hit, Input, and Output

Price (USD per M Tokens) · Lower is better · 10,000 input tokens

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

Pricing: Blended Price

Blended at 7:2:1 (cache-input-output) · USD per 1M tokens (blended) · Lower is better

Price per token, shown in USD per million tokens. Price is a blend of cache hit, input, and output token prices using the selected ratio (default 7:2:1 cache-input-output).

Output Speed vs. Price

Blended at 7:2:1 (cache-input-output) · Output speed: output tokens per second · USD per 1M tokens (blended)
Most attractive quadrant

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).

Speed

Measured by Output Speed (tokens per second)

Output Speed: Quasar 438B

Output speed: output tokens per second · 10,000 input tokens

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 performance of the model's first-party API (e.g. OpenAI for o1) or the median across providers where a first-party API is not available (e.g. Meta's Llama models).

Latency vs. Output Speed

Latency: seconds to first token received · Output speed: output tokens per second · 10,000 input tokens
Most attractive quadrant

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).

Latency

Measured by Time (seconds) to First Token

Time to First Answer Token

Seconds to first token received · Lower is better · 10,000 input tokens

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

Seconds to output 500 tokens, including reasoning model 'thinking' time · Lower is better · 10,000 input tokens

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

Key Comparison Metrics & API Features

Multiverse Computing logoMultiverse Computing
1M
Proprietary
$0.60
183
1.09
14.77
10.94

Frequently Asked Questions

Common questions about Quasar 438B providers

Quasar 438B is available through 1 API provider: Multiverse Computing. Each provider offers different performance characteristics and pricing.

Quasar 438B is currently available through 1 API provider that we benchmark and track.

The fastest provider for Quasar 438B by output speed is Multiverse Computing (182.7 t/s). Output speed measures how quickly tokens are generated after the model starts responding.

The provider with the lowest time to first answer token for Quasar 438B is Multiverse Computing (12.03s). Lower latency means faster initial response time.

The most affordable provider for Quasar 438B by blended price is Multiverse Computing ($0.72 per 1M tokens). Blended price uses a 7:2:1 cache hit/input/output token ratio.

The provider with the lowest input token pricing for Quasar 438B is Multiverse Computing ($0.60 per 1M input tokens).

The provider with the lowest output token pricing for Quasar 438B is Multiverse Computing ($1.80 per 1M output tokens).

The only provider of Quasar 438B supports JSON mode for structured output.

The only provider of Quasar 438B supports function calling (tool use).

Multiverse Computing leads across all key metrics for Quasar 438B, offering the fastest speed, lowest latency, and most competitive pricing.

When choosing a provider for Quasar 438B, consider: output speed (for throughput-intensive tasks), latency (for interactive applications requiring quick first responses), pricing (for cost-sensitive workloads), and API features like JSON mode or function calling.

Yes, provider performance can vary over time due to infrastructure changes, load balancing, and updates. We continuously benchmark all providers and display historical performance trends in the "Over Time" charts.

For information about Quasar 438B's intelligence, capabilities, modalities, and how it compares to other models, see the model overview page. View model overview