LLM Comparison

GLM-5.3-Flash vs Hunyuan A13B Instruct

Side-by-side specs, pricing & capabilities

Add to comparison

2/6 models
Same tier:
 Z.aiGLM-5.3-FlashTencentHunyuan A13B Instruct
OrganizationZ.aiZ.aiTencentTencent
OpenTools Score
74
456
FamilyGLMHunyuan
StatusCurrentCurrent
Release DateAug 2026Jul 2025
Context Window1.3M tokens131K tokens
Input Price$0.07/M tokens$0.14/M tokens
Output Price$0.25/M tokens$0.57/M tokens
Pricing NotesOpenRouter lists a limited-time discounted price of $0.075/M input and $0.25/M output. Standard first-party style pricing is commonly $0.15/M input and $0.50/M output; cache-read pricing may vary by provider.—
Capabilities
textvisionvideo-inputcodetool-usereasoninglong-contextopen-weights
textcode
Training CutoffNot disclosed—
Max Output131K tokens131K tokens
API Identifierz-ai/glm-5.3-flashtencent/hunyuan-a13b-instruct
Benchmarks
Artificial Analysis Intelligence Index v4.3
41.9 indexartificial-analysis
—
GPQA Diamond
91.2%artificial-analysis
—
SciCode
51.6%artificial-analysis
—
Terminal-Bench 2.1
84.3%artificial-analysis
—
 View GLM-5.3-FlashView Hunyuan A13B Instruct

Cost Calculator

Enter your expected monthly token usage to compare costs.

ModelInputOutputTotal / movs Best
GLM-5.3-FlashCheapest$0.08$0.13$0.20—
Hunyuan A13B Instruct$0.14$0.29$0.43+112%

Compare hosting configurations

Compare two exact setups, including different configurations of the same model. Hardware fit, measured speed and costs are separate decisions.

Add your cost assumptions (optional)

Use hours for the same scenario period. Cloud billing includes idle time; active hours alone do not set the bill. Local electricity uses whole-system attributable power, powered hours and your tariff. Missing inputs remain unknown.

Share this configuration comparison

Measured speed needs the same pinned workload protocol, tokenizer, context, batching and cache state.

ConfigurationRun full native GLM-5.3-Flash image, video and reasoning on an owned DGX H200 TP4 subsetRun Hunyuan A13B fast-mode text on a 64 GiB Intel desktop
ModelGLM-5.3-FlashHunyuan A13B Instruct
HardwareOwned NVIDIA DGX H200; 4 of 8 GPUs, diagnostic TP4Intel Core i5-12400 desktop, 8 inference threads, 64 GiB RAM
RuntimeGLM 5.3 Flash full native NVIDIA immutable image Official image 0674a3ea, declared vLLM 385dce36 / Python 3.12 / CUDA 13.0.2; reader source guards required · CUDAllama.cpp v0.7.0 (620d2225cc436ab0b001e3200e590e3b286ef9ab) · CPU
ArtifactGLM-5.3-Flash complete native mixed FP8/BF16 multimodal checkpoint · Native mixed FP8 with the exact BF16 vision, attention, KDA and mHC exclusions retained · Native FP8 language experts with exact BF16 exclusions and full BF16 vision; no re-quantization/component dropHunyuan A13B Instruct Q4_K_M publisher GGUF · GGUF Q4_K_M mixed quantization · Q4_K_M GGUF quantization published by Tencent
Context / concurrency16,384 tokens / 14,096 tokens / 1
Required memoryUnknown (unknown)Unknown (unknown)
EvidenceDocumented setupDocumented setup
Hardware fitHardware fit unknown

Your operating system is unknown. Runtime support has not been confirmed. Full weights, BF16 vision, KDA recurrent/convolution states, sparse MLA, mHC, MTP, collectives, kernels and caches have not been measured. Enter available memory per device or unified memory pool. Host RAM: Preserve the DGX vendor 2 TB and AWS 2,048 GiB source labels. Reader records actual MemTotal; no nominal-to-usable threshold or measured minimum is asserted. Free disk space: A 1 TiB usable working-space guard is prescribed for assets, image/staging and results. It is a conservative reader allocation, not a measured minimum or proof the unpacked runtime fits. Container requirement: Separate immutable Linux amd64 container; host/container versions not conflated

Hardware fit unknown

No exact full-process peak for Hunyuan A13B Q4_K_M and CPU workload. Enter available memory per device or unified memory pool. Host RAM: 64 GiB is chosen host capacity, not a measured minimum. Free disk space: 80 GiB is an author free/root disk allocation, not measured disk minimum.

One-time cost
Unknown

Existing hardware/allocation: Existing owned acquisition cost is unknown. Reader setup labor: Reader download, image pull, setup and labor costs are unknown and separate from recurring use.

Unknown

hardware: Existing desktop purchase price and incremental hardware cost depend on the reader; unknown. setup: Initial provisioning/build time and labor cost are unknown.

Recurring scenario cost
Unknown

Owned electricity: Owned-host electricity/power price and measured use are unknown. Retained local/storage: Existing NVMe retention/opportunity cost is unknown. Instance-store data may be lost on stop or termination; copy wanted results first. Network/egress: Network, data-transfer charges and taxes are unknown; no free assumption. Administration: Reader-specific labor and administration costs are unknown.

One-time setup and recurring costs are separate. Unknown components are not treated as free. No monthly token output is inferred from peak throughput.

Unknown

electricity: Actual wall power, electricity rate and powered hours are unknown; no TDP-to-wall-power conversion. storage: Incremental cost of local disk capacity is unknown. The 80 GiB free-disk walkthrough allocation is an author choice, not a measured requirement. egress: Data transfer price, allowances and traffic volume are unknown. administration: Maintenance labor rate and hours are unknown.

One-time setup and recurring costs are separate. Unknown components are not treated as free. No monthly token output is inferred from peak throughput.

Published measurements (unranked)No compatible measurement availableNo compatible measurement available

Different currencies and incomplete costs are not ranked. Model quality benchmarks remain on the model pages; they do not establish quality or speed for every deployment.

Find configurations for your hardware

Looking for more AI models?

Browse All LLMs