Compare
Devstral Medium 2507 vs GLM 5
This page is context-first: how much text each model can take in one request. Full specs adds capabilities and limits; the pricing matrix below is only about $/million tokens from hosts that list both models.
Context window · side by side
Bar length is relative to the larger of the two windows (100% = max of this pair). This is not pricing.
GLM 5 has about 1.6× the context window of the other in this pair.
GLM 5 has 58% more context capacity (202K vs 128K tokens). Devstral Medium 2507 is 60% cheaper on input.
Quick verdicts
Short takeaways — validate with your own workloads.
Long document processing
Use GLM 5. Its 202K context fits entire documents without chunking (vs 128K).
RAG / high-volume retrieval
Use Devstral Medium 2507. Input tokens are 60% cheaper — critical when sending large retrieved contexts.
Full specs
Context, output, capabilities, and dates. Green highlights the favorable value where we compute a winner.
| Spec | Devstral Medium 2507 | GLM 5 |
|---|---|---|
| Context window | 128,000 tokens (128K) | 202,752 tokens (202K) |
| Max output tokens | 128,000 tokens (128K) | 128,000 tokens (128K) |
| Speed tier | Balanced | Balanced |
| Vision | No | No |
| Function calling | Yes | Yes |
| Extended thinking | No | Yes |
| Prompt caching | No | Yes |
| Batch API | No | No |
| Release date | N/A | Feb 2026 |
Pricing matrix
Dollar rates only: hosts that list both models, per 1M tokens. For how much text fits, use the context section above — not this table.
| Provider | Devstral Medium 2507 in | Devstral Medium 2507 out | GLM 5 in | GLM 5 out |
|---|---|---|---|---|
| Baseten | — | — | $0.950/M | $3.15/M |
| Mistral | $0.400/M | $2.00/M | — | — |
| Openrouter | — | — | $0.800/M | $2.56/M |
| Z Ai | — | — | $1.00/M | $3.20/M |
Frequently asked questions
Powered by Mem0
Use a smaller model.
Get better results.
Mem0 gives your AI long-term memory so you stop re-sending context on every call. That means you can use a smaller, faster, cheaper model — and still get better answers.
Example: a multi-turn chat session
80% less to send — works with any model