[docs] AI Coding — PAYG vs Token Plan: per-service-type tabs for every copy-paste example — VI + EN - #40
Merged
Merged
Conversation
…y copy-paste example — VI + EN
Every config example hardcoded the PAYG endpoint, with the Token Plan URL
mentioned only in a hint below the code block the reader had already copied.
Token Plan users got 401/404 with no path to the answer.
- Add a service-type table + 2x2 Base URL matrix (PAYG/Token Plan x Anthropic//v1)
to the AI Coding hub and the prerequisites page
- Wrap every config block in {% tabs %} PAYG | Token Plan so examples are
copy-ready per service type (Claude Code: 4 tabs, service type x OS)
- Identify key type by provenance (API Keys page vs plan Subscription keys tab),
since the two key types are visually indistinguishable
- Document the new failure mode everywhere: valid key + wrong host = 401;
add 403 (model outside plan) and 402 (plan expired) rows
- Add a curl step to verify the URL+key pair before configuring any tool
- Surface that Model ID differs between service types (z-ai/glm-5.2 vs Model code)
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
AI Coding docs now handle two service types (PAYG and Token Plan) in every copy-paste example, VI + EN.
Why
Every config example hardcoded the PAYG endpoint (
maas-llm-aiplatform-hcm.api.vngcloud.vn), with the Token Plan host (tokenplan.api.greennode.ai) mentioned only in a hint block below the code the reader had already copied. A Token Plan user following any tool page got401/404with nothing in the troubleshooting tables explaining why.Changes
/v1/ OpenAI-with-/v1) on the AI Coding hub and the prerequisites page{% tabs %}PAYG | Token Plan so examples are copy-ready per service type. Claude Code uses 4 flat tabs (service type x OS) since GitBook nested tabs are unreliable401; added403(model outside plan) and402(plan expired) rowscurlverification step so the URL+key pair is proven before any tool configz-ai/glm-5.2vs the plan Model codeglm-5.2)Files (18, all pre-existing — no SUMMARY.md changes needed)
VI —
ai-stack/ai-coding/: README, bat-dau, ket-noi-openai-compatible-voi-maas, dong-lenh/{README,claude-code,codex-cli,opencode}, co-giao-dien/{README,codex-desktop}EN —
ai-stack/ai-coding/: README, getting-started, connect-openai-compatible-to-maas, cli-tools/{README,claude-code,codex-cli,opencode}, gui-tools/{README,codex-desktop}Verified
GitBook tag balance (tabs/tab/hint), code-fence parity, all relative links and image paths resolve, VI/EN heading counts and tab counts match on all 7 page pairs.
Note for review
The Token Plan Model code examples (
glm-5.2) come from the existing Token Plan A-Z guide. The docs say Model IDs can differ between service types rather than asserting a naming rule — worth confirming against the actual portal behaviour.🤖 Generated with Claude Code