Zhipu AI · text · exact comparison

GLM-5.2 API pricing by provider

Compare GLM-5.2 API token prices across provider routes with exact model identity, meter, tier, source, and check date.

Current answer: 6 accepted GLM-5.2 observations; one current example is $1.4 / 1M input tokens, checked Aug 22, 2026. Open the evidence source, then compare an exact matching configuration below.

Model-level provider comparison

GLM-5.2 price ranking status

Reviewed scopes, no current winner

Current answer: No current cheapest provider is published. The reviewed scopes do not have enough fresh, like-for-like offers to name a winner.

Provider routes with evidence
3
Accepted observations
6
Billing meters
1M input tokens, 1M output tokens
Latest accepted check
Aug 22, 2026

GLM-5.2 API input token pricing

GLM-5.2 input token price ranking

Not currently rankable
Reviewed comparison scope
GLM-5.2 · chat completions · global · USD per 1M input tokens
Publication gate
At least 3 unique providers with accepted, fresh, reviewed evidence

Why there is no winner

Ranking withheld: 0 of 3 required providers have fresh, matching evidence.

The exact model and meter match; provider tier features may differ. The result does not rank throughput, quality, quotas, uptime, privacy, or support.

GLM-5.2 API output token pricing

GLM-5.2 output token price ranking

Not currently rankable
Reviewed comparison scope
GLM-5.2 · chat completions · global · USD per 1M output tokens
Publication gate
At least 3 unique providers with accepted, fresh, reviewed evidence

Why there is no winner

Ranking withheld: 0 of 3 required providers have fresh, matching evidence.

The exact model and output meter match. The order does not claim equivalent latency, limits, reliability, data terms, or total production cost.

Uncollapsed source records

All accepted offer evidence

These rows remain separate until their offered model ID, route, meter, tier, resolution, duration, audio, and region are proven comparable.

GLM-5.2 provider offers · exact configuration scope
ProviderModelConfigurationRecorded priceEvidence
Fireworks AIaggregatorGLM-5.2model: z-ai/glm-5.2 · chat-completions · serverless-standard · not-applicable · no audio$1.4 / 1M input tokensstaleProvider sourceChecked Aug 22, 2026
Fireworks AIaggregatorGLM-5.2model: z-ai/glm-5.2 · chat-completions · serverless-standard · not-applicable · no audio$4.4 / 1M output tokensstaleProvider sourceChecked Aug 22, 2026
OpenRouterrouterGLM-5.2model: z-ai/glm-5.2 · chat-completions · standard · not-applicable · no audio$0.966 / 1M input tokensstaleProvider sourceChecked Aug 22, 2026
OpenRouterrouterGLM-5.2model: z-ai/glm-5.2 · chat-completions · standard · not-applicable · no audio$3.036 / 1M output tokensstaleProvider sourceChecked Aug 22, 2026
Together AIaggregatorGLM-5.2model: z-ai/glm-5.2 · chat-completions · serverless · not-applicable · no audio$1.4 / 1M input tokensstaleProvider sourceChecked Aug 22, 2026
Together AIaggregatorGLM-5.2model: z-ai/glm-5.2 · chat-completions · serverless · not-applicable · no audio$4.4 / 1M output tokensstaleProvider sourceChecked Aug 22, 2026

Checked evidence, not a ranking: fresh rows were checked against the linked first-party source on the shown date. APIDir does not name a cheapest provider unless exact configurations and units match. Recheck before purchasing.

Developer resources

Provider documentation and pricing links

Compare integration documentation beside the exact first-party source used for each accepted observation.

Provider documentation, pricing, and accepted evidence for this model
ProviderChannelDeveloper resourcesAccepted evidence
Fireworks AIaggregatorDocumentationPricing page2 observationsEvidence source 1
OpenRouterrouterDocumentationPricing page2 observationsEvidence source 1
Together AIaggregatorDocumentationPricing page2 observationsEvidence source 1

Decision guide

How to compare GLM-5.2 API providers

GLM-5.2 is an exact model comparison rather than a family rollup. APIDir reviews OpenRouter, Together AI, and Fireworks AI routes one token meter at a time. Provider tier names stay visible because shared-service limits and features can differ even when the model identity matches.

The lowest token meter is not automatically the lowest production cost. Prompt-output ratio, cache reads, throughput, request limits, retry behavior, regional availability, data terms, and engineering fit should be tested with the actual workload.

What changes GLM-5.2 API cost

  • Input-output token ratio, context length, and provider cache pricing
  • Router or serverless tier, throughput, quotas, and dedicated capacity
  • Tool calls, retries, retention, observability, and operational support

Integration checks before production

  • Pin the exact GLM-5.2 route key and API compatibility mode
  • Apply bounded retries only to safe operations and expose terminal errors
  • Capture route, token counts, tier, retries, and provider request ID

Workloads this comparison can inform

General language workloads

Weight input and output meters using representative production traces.

Structured extraction

Compare schema reliability and repair retries beside the token price.

Provider diversification

Benchmark latency, quotas, error mapping, and data terms before adding a fallback route.

How to read the price result

Three matching provider routes pass the reviewed GLM-5.2 input and output scopes. The published order applies only to those token meters and does not score service quality or total cost.

Related model price comparisons

Use this evidence safely

A recorded price is not a complete production quote. Open the source, reproduce the exact configuration, and include retries, failed work, storage, egress, support, rate limits, and downstream processing in total cost.

Questions developers ask

What makes two GLM offers comparable?

The exact model and endpoint, provider route, input and output meters, cache policy, context-length price band, tools, region, and service tier must match.

Does APIDir name a cheapest provider on this page?

Only when at least three explicitly reviewed provider offers are fresh, publication-permitted, and within the same published comparison scope. Stale or mismatched evidence cannot support that claim.

How should I confirm a budget?

Open the linked provider source, verify the configuration, then calculate your own successful and failed workload volume.

APIDir Delta · controlled rollout

Join the source-linked pricing update waitlist.

Confirm your address to join the waitlist. Editorial delivery starts only after sender, suppression, and evidence checks are active.