Favicon for tencent

Tencent: Hunyuan A13B Instruct

Going away November 15, 2026

tencent/hunyuan-a13b-instruct

Model weights

Hunyuan-A13B is a 13B active parameter Mixture-of-Experts (MoE) language model developed by Tencent, with a total parameter count of 80B and support for reasoning via Chain-of-Thought. It offers competitive benchmark performance across mathematics, science, coding, and multi-turn reasoning tasks, while maintaining high inference efficiency via Grouped Query Attention (GQA) and quantization support (FP8, GPTQ, etc.).

Modalities
In / out price
$0.14 / $0.57per 1M
Context
131K
Released
Jul 8, 2025
Knowledge cutoff
Mar 2025

Providers

This model is hosted by one provider. OpenRouter forwards every request without routing.

Pricing

The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.

Weighted average

Input
$0.1393/M tokens
Output
$0.5694/M tokens
Price history
No effective price data for this selection

Performance

Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).

Throughput
28tok/s

P50, best across providers

Latency
1.00s

P50, best provider

Uptime

Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.

Uptime (3d)The model was reachable. Request routed to a provider.
100.00%
Availability (3d)The model returned inference from any provider. Errors and empty responses count against it.
99.81%

Availability over the last 3 days

Last 72 hours
Availability 99.81%
3 Days Ago2 Days AgoYesterdayNow

Availability over the last 24 hours

OpenRouter Availability
99.95%

When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and provider routing options.

Apps

Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.

1.
3.14Mtokens
2.
2.52Mtokens
3.
2.02Mtokens
4.
1.45Mtokens
5.
1.33Mtokens
Rest of OpenRouter
19M
Top 5 Apps
84K

Activity

Token volume and request traffic to this model over time.

API

Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.

Not currently available through EU in-region routing. In-region routing docs

Frequently asked questions

Explore more models