GLM
Listed by the current MonkeyCode project README. Verify the specific model identifier and provider route available to your installation.
Product
Product overviewFeaturesPricingModelsSelf-hosting
Self-hosted guideCompare
CompareTools
ToolsResources
Your first task: fix, test, explainProduct update logAI NewsResearchDirect answersTry MonkeyCode ↗GitHub ↗Language
Independent community guides about MonkeyCode.
MODEL GUIDE · MODEL FACTS CHECKED 2026-09-10
The public project currently names GLM, Kimi, MiniMax, Qwen, and DeepSeek. Exact model versions, endpoints, pricing, regions, limits, and availability can change and must be checked in the deployment you evaluate.
Documented model families
The names below reflect the public project README checked on 2026-10-20. “Supported” should not be interpreted as every version, region, account type, or deployment mode.
Listed by the current MonkeyCode project README. Verify the specific model identifier and provider route available to your installation.
Listed by the current MonkeyCode project README. Verify the specific model identifier and provider route available to your installation.
Listed by the current MonkeyCode project README. Verify the specific model identifier and provider route available to your installation.
Listed by the current MonkeyCode project README. Verify the specific model identifier and provider route available to your installation.
Listed by the current MonkeyCode project README. Verify the specific model identifier and provider route available to your installation.
Primary source: MonkeyCode project README ↗
Verify the route
Do the steps once per release before you depend on a model. Each step produces a check you can keep, not a claim you have to trust.
Open the model picker in the release you evaluate and confirm the exact id and version. The README family name is not the selectable id.
Use the fixed first-task example, not a free-form prompt: starter pack and reference solution. Confirm a task is accepted end to end.
Capture the model id returned by the request (logs or response). Only this proves what your account used; the picker label can differ.
Check who owns the key, how it is scoped and rotated, and whether traffic goes direct, through a gateway, or to a local endpoint.
| Symptom | Likely cause | Where to look |
|---|---|---|
| Request rejected with an “insufficient credit / quota” style error | One of several possible causes: the daily token allowance for the current plan is used up, the monthly credit allowance is used up, or a provider-side account quota applies. Daily tokens, monthly credits and provider quotas are separate counters, and a rejected request does not by itself identify which one was hit. | Plan caps and billing period: pricing & TCO page. Actual usage and credit balance for the current period: the product account panel after signing in. Provider-side limits: the provider account dashboard. |
| Request rejected with a rate-limit (429) error | Per-key or per-model request limit | Add backoff/retry, raise the account limit, or spread load across keys |
| Model not found / unsupported in this region | Id not offered for this release, region, or account type | The picker in this release; the provider's model list for the region |
| Works in one deployment, fails in another | Different route, key scope, or network egress | Compare request paths, gateway config, and egress policy between the two |
Model facts checked 2026-09-10 · page content updated 2026-10-09. Source: provider model documentation ↗.
Selection matrix
Two deployments can select the same model family and still have different privacy, reliability, latency, and cost characteristics.
| Decision | Question to answer | Evidence to retain |
|---|---|---|
| Availability | Which exact model IDs and versions are selectable in this release and region? | Configuration screenshot and successful test request. |
| Routing | Does traffic go directly to a provider, through a private gateway, or to a locally operated endpoint? | DNS, proxy, firewall, and request-path evidence. |
| Credentials | Who owns the account and how are keys scoped, stored, rotated, and revoked? | Secret inventory and rotation test. |
| Data handling | What source context is sent and what are the provider's retention and training terms? | Current contract, policy, and request sample. |
| Operations | What are the rate limits, fallback behavior, observability, and outage procedure? | Load test, failure test, and runbook. |
| Cost and quality | Which model meets acceptance criteria at an acceptable total task cost? | Same-task pilot results, including retries and review. |
Model evaluation
A model leaderboard does not measure your environment, tools, policies, or reviewer effort.
Use representative bug fixes, tests, documentation, and small features with written acceptance criteria.
Use the same repository state, environment, tools, prompts, and retry policy.
Record pass rate, human corrections, latency, tokens, model cost, compute, and review time.
Exercise quota errors, timeouts, unavailable models, credential revocation, and fallback routes.
Common questions
Source-backed direct answers: can it use local models?, can it run offline?