Where can I access Jamba 1.6 Large?

Artificial Analysis

This model is deprecated. We still benchmark its performance, but less often: every 18 hours instead of every 6.

AI21 Labs has launched a newer release, Jamba 1.7 Large. We suggest considering it instead.

AI21 Labs

•

Open weights model

•

Released March 2025

Jamba 1.6 Large API Provider Benchmarking & Analysis

Model Comparison

This analysis is intended to support you in choosing the best API provider of Jamba 1.6 Large for your use-case.

Lowest Time per Task

Time per Intelligence Index task (minutes)

Total 0 providers

Lowest Cost per Task

Cost per Intelligence Index task

Total 0 providers

No API providers are currently available for Jamba 1.6 Large.

Benchmarks of providers are not available for this model.

Please see the models page for Jamba 1.6 Large for details of the model and its intelligence compared to other models.

Time per Task

Inference time (minutes) per Intelligence Index task · Lower is better

No data available

Cost per Task

Weighted average cost (USD) per Intelligence Index task · Lower is better

No data available

Pricing

Cost per Intelligence Index Task: Jamba 1.6 Large

Weighted average cost (USD) per Intelligence Index task · Segmented by token type · Lower is better

No data available

Weighted average cost per Intelligence Index task. Each evaluation’s cost is calculated from input, cache hit, cache write, reasoning, and answer token prices, divided by task count, and weighted by its Intelligence Index weight.

Pricing: Cache Hit, Input, and Output: Jamba 1.6 Large

Price (USD per M Tokens) · Lower is better

No data available

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.

Output Speed vs. Cost per Task: Jamba 1.6 Large

Output speed: output tokens divided by total request time, including time to first token · Weighted average cost (USD) per Intelligence Index task

Most attractive quadrant

No data available

Output tokens, including reasoning tokens, received per second over a request's full duration, from sending the request to receiving the final token. The headline value averages each Performance v3 workload over the past 5 days, then averages the workloads.

Speed

Average of the single-request and multi-turn agentic workloads measured

Output Speed: Jamba 1.6 Large

Output tokens divided by total request time · Includes time to first token · Average of the single-request and multi-turn agentic workloads measured · Higher is better

No data available

Speed and latency metrics average each endpoint's runs over the past 5 days, and the error rate pools them. We run the benchmark every 6 hours, and endpoints of deprecated models every 18 hours.

Latency

Average of the single-request and multi-turn agentic workloads measured

Time to First Answer Token: Jamba 1.6 Large

Seconds until the first answer token after any reasoning · Average of the single-request and multi-turn agentic workloads measured · Lower is better

No data available

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.

Speed and latency metrics average each endpoint's runs over the past 5 days, and the error rate pools them. We run the benchmark every 6 hours, and endpoints of deprecated models every 18 hours.

Reliability

Share of requests the endpoint failed, across all the single-request and multi-turn agentic workloads measured

Endpoint Error Rate: Jamba 1.6 Large

Share of requests the endpoint failed with an error, a rate limit or a timeout · Across all the single-request and multi-turn agentic workloads measured · Lower is better

No data available

Share of requests over the past 5 days that the endpoint failed with an error, a rate limit or a timeout. Failures on our side are left out of both counts. Across several workloads, the failures and requests are pooled before dividing.

Speed and latency metrics average each endpoint's runs over the past 5 days, and the error rate pools them. We run the benchmark every 6 hours, and endpoints of deprecated models every 18 hours.

Key Comparison Metrics & API Features



No results.

Frequently Asked Questions

Common questions about Jamba 1.6 Large providers

Jamba 1.6 Large is not currently available through any API providers we benchmark. As an open weights model, it can be self-hosted.

Jamba 1.6 Large API Provider Benchmarking & Analysis

Lowest Time per Task

Lowest Cost per Task

Time per Task

Cost per Task

Pricing

Cost per Intelligence Index Task: Jamba 1.6 Large

Cost per Intelligence Index Task

Pricing: Cache Hit, Input, and Output: Jamba 1.6 Large

Cache Hit

Output Speed vs. Cost per Task: Jamba 1.6 Large

End-to-End Output Speed

Speed

Output Speed: Jamba 1.6 Large

End-to-End Output Speed

Time Period

Latency

Time to First Answer Token: Jamba 1.6 Large

Time to First Answer Token

Time Period

Reliability

Endpoint Error Rate: Jamba 1.6 Large

Endpoint Error Rate

Time Period

Key Comparison Metrics & API Features

Frequently Asked Questions

Where can I access Jamba 1.6 Large?