Glm 5.3 vs deepseek v4 usage

The undocumented endpoint Everyone scraping the settings page for usage stats can stop. This works with your API key (the same Bearer you use for chat completions): curl -H "Authorization: Bearer $OLLAMA_API_KEY" https://ollama.com/api/usage Returns: activity: 4-week metered cost + per-model {request_count, cost} limits.session and limits.weekly: usage (0–1) + per-model request counts POST /api/me (note: POST, not GET) returns your account/plan info What it does NOT expose: reset times, absolute quota, extra-usage balance. No query params — ?period= etc. are silently ignored, and every sub-endpoint 404s. When does the session quota actually reset? The API won't tell you, so I watched it. Baseline evidence: session sat at 49.9% (1,289 reqs) at 11:45 UTC and dropped to 0.001% by 15:53. A rolling 5h window would still show ~50% — only a fixed boundary explains that drop. I then logged usage every 30 minutes for 48 hours and caught 6 boundaries, all landing 5h apart at minute :55, anchored to 11:55 UTC. Zero drift across 6 resets. The practical formula (no cookie needed): EPOCH = 2026-08-12 11:55 UTC next_reset = EPOCH + ceil((now - EPOCH) / 5h) * 5h Weekly appears to be a fixed 7-day window too (my reset hit exactly 7d after the previous one), but I have fewer observations there — treat it as provisional. The experiment: GLM 5.3 vs DeepSeek Method: same ~400-token prompt to each model via /v1/chat/completions (max_tokens 120), 20 calls per model, read /api/usage before/after each batch with a 60s settle. | Model | avg tokens/call | session quota pts/call | |---|---|---| | glm-5.3-flash | ~410 | 0.030 | | deepseek-v4-flash:0731 | ~481 | 0.015 | GLM cost roughly 2× per call (~2.3× per token) for the identical workload. Caveats: n=20 per model, the weekly meter ticks in 0.1pt quanta so the true ratio is bounded ~1.7–2.3×, single Pro account, and the metered-cost ledger didn't show GLM rows at all during the experiment (only older DeepSeek activity), so this is quota-pts, not dollars. Practical takeaways If your priority is max requests per weekly quota: DeepSeek is the range king. The meter ignores tiny requests (a 4-token "say OK" didn't move it at all) — quota tracks meaningful GPU work, not call count. If you run both, the hybrid works well: better model where a human reads the output, cheaper model for automation (my automation was 8,500 of 8,600 weekly requests). Repro: any Pro account, one bash loop over the endpoint above. Happy to share the measurement script. TL;DR Ollama Cloud exposes an undocumented usage API: GET https://ollama.com/api/usage with your Bearer key. It returns activity (4wk), per-model request counts, and session/weekly quota as 0–1 fractions. Session quota resets in fixed 5-hour blocks, every 5h at minute :55 (verified 6× over 48h, zero drift). Because 5 doesn't divide into 24, the reset time cycles through all 24 hours over 5 days. Controlled experiment: identical ~400-token prompts, 20 calls per model. GLM 5.3 flash cost ~0.030 quota-pts/call vs DeepSeek v4 flash ~0.015 — GLM drains the tank ~2× faster. submitted by /u/subimpact [link] [comments]

Source: r/ollama | 2026-08-27

Related