MiniMax Token Plan and Hermes Agent Setup — source notes
Sources, claim audit, redirect checks, and independent review for the MiniMax Token Plan Subscription + Setup guide.
minimax-token-plan-subscription-hermes-agent source notes — v1
Draft path: /opt/data/cron-state/abs-guides-drafts/minimax-token-plan-subscription-hermes-agent.md
Review URL target: /guides/review/minimax-token-plan-subscription-hermes-agent/
Sources used: 10 total (8 live official pages, 1 live CLI probe, 1 internal research digest)
Drafter: MiniMax M3 (subagent dispatch from main session, 2026-07-31)
Date: 2026-07-31
Editorial scope
This is the first proposed Subscription + Setup guide: commercial rundown first, implementation second. Draft frontmatter uses guideCategory: subscription-setup, but the current production schema does not accept this value. The parent must adapt review routing/schema during promotion. No image was requested or generated. The stale public ABS article hermes-agent-provider-minimax.md was deliberately not used as evidence.
Sources collected (Source Discovery Ladder)
Layer 1 — Official vendor and product docs
- MiniMax Token Plan pricing — https://platform.minimax.io/subscribe/token-plan — prices, annual offers, M3 monthly estimates, concurrency, eligible model families, modality table, video-generation limits, credits packages, peak traffic statement; verified 2026-07-31.
- MiniMax Token Plan FAQ — https://platform.minimax.io/docs/token-plan/faq — usage-based deduction, unified quota, Subscription Key distinction, rolling five-hour and weekly windows, non-rollover, usage endpoint, upgrade/cancel behavior, production recommendation, RPM/TPM throttling, dynamic peak controls; verified 2026-07-31.
- MiniMax Token Plan overview — https://platform.minimax.io/docs/token-plan/intro — intended uses, special-resource exclusions, quota-exhaustion options, direct account and key links; verified 2026-07-31.
- MiniMax Token Plan quickstart — https://platform.minimax.io/docs/token-plan/quickstart — obtaining the Subscription Key, prerequisite resource assignment, key protection, distinction from PAYG keys; verified 2026-07-31.
- MiniMax Token Plan detailed pricing — https://platform.minimax.io/docs/guides/pricing-token-plan — monthly plan table, Credits package prices and 365-day validity, deduction order; verified 2026-07-31.
- MiniMax Hermes Agent integration — https://platform.minimax.io/docs/token-plan/hermes-agent — installer,
hermes doctor,hermes model, global endpoint selection, Subscription Key prompt, MiniMax-M3 selection; verified 2026-07-31. - Hermes Agent provider documentation — https://hermes-agent.nousresearch.com/docs/integrations/providers — native provider
minimax,MINIMAX_API_KEY,~/.hermes/.env,hermes modelvs/model, global endpoint support; verified 2026-07-31. - MiniMax paid-service terms — https://platform.minimax.io/protocol/terms-of-service — effective 2026-03-30; ongoing charges, service-rule precedence, price/billing adjustments, account responsibility/security, Singapore law; verified 2026-07-31.
- MiniMax referral-program terms — https://platform.minimax.io/docs/token-plan/promotion — explicit Token Plan non-refundable statement; verified 2026-07-31. Caveat: this statement appears in referral-program terms, so the article tells readers to check current checkout/service terms rather than claiming a universal statutory result.
Layer 2 — Source code / local installation
/usr/local/lib/hermes-agent/plugins/model-providers/minimax/__init__.py— local Hermes provider registration confirmsminimax,MINIMAX_API_KEY, global base URLhttps://api.minimax.io/anthropic, and MiniMax-M3 auxiliary default; inspected 2026-07-31./usr/local/lib/hermes-agent/hermes_cli/models.py— local catalog includesMiniMax-M3; inspected 2026-07-31.
Layer 3 — Live verification
hermes --version— returnedHermes Agent v0.19.0 (2026.7.20) · upstream 07e97d2f; also reported 1,218 commits behind; verified 2026-07-31.hermes model --help— confirmed interactive selector and--refresh; verified 2026-07-31.hermes chat --help— confirmed--provider,--model, and-q/--query; verified 2026-07-31.- No authenticated MiniMax smoke test was run: this draft session did not use or expose a reader-owned Subscription Key. The command is syntax-verified, not credential-verified in isolation.
Layer 4 — Internal operator evidence
/opt/data/research/ai-subscriptions/RESEARCH-2026-07-31.md, especially A1 and §14 — used only as a discovery/correction ledger; all article claims were re-checked against live primary pages on 2026-07-31.abs-guides-cron-pipelineand drafter runbook — used for article structure, inline/date-stamped citations, source-notes shape, command-map requirement, security section, and independent-review handoff; read 2026-07-31.
Layer 5 — Community caveats
- None used. The primary sources directly document the relevant limits and failure modes.
Layer 6 — Competing-guide gap analysis
- The old ABS MiniMax provider guide was known to contain stale setup commands and was excluded as a source. The new article uses
hermes model, providerminimax, andMINIMAX_API_KEYfrom current Hermes docs.
Claim-by-claim evidence audit
This is a drafter evidence map, not the mandatory independent review. The parent must dispatch a fresh review subagent.
| # | Claim | Evidence | Drafter status |
|---|---|---|---|
| 1 | Plus/Max/Ultra cost $20/$50/$120 monthly | Live pricing page and pricing docs | Source-matched |
| 2 | Approximate M3 equivalents are 1.7B/5.1B/12.5B monthly | Live pricing page | Source-matched; explicitly labeled estimates |
| 3 | Agent concurrency is ~3–4/~4–5/~6–7 | Pricing page and FAQ traffic rules | Source-matched; explicitly approximate |
| 4 | Video generation is none/3 per day/5 per day | Live plan comparison table | Source-matched |
| 5 | All tiers include M3/M2.7/image/speech/music and image/video input understanding | Live pricing page | Source-matched |
| 6 | Included resources share one quota | FAQ, overview, pricing docs | Source-matched |
| 7 | Quota uses rolling five-hour and weekly windows and does not roll over | FAQ and overview | Source-matched |
| 8 | Dynamic peak-hour throttling can occur | FAQ traffic rules | Source-matched |
| 9 | Token Plan is for interactive individual use; PAYG recommended for production | FAQ limits section | Source-matched |
| 10 | M3 supports 1M context | Live pricing page and local Hermes metadata | Source-matched |
| 11 | Some special resources, including H3/voice design/rapid voice cloning, are excluded | Token Plan overview | Source-matched; drift-sensitive |
| 12 | Credits cost $5/$25/$100 for 5k/25k/100k and last 365 days | Pricing docs | Source-matched |
| 13 | Subscription quota is consumed before eligible Credits | FAQ and pricing docs | Source-matched |
| 14 | Subscription Key differs from PAYG API key | Quickstart, FAQ, overview | Source-matched; load-bearing |
| 15 | Upgrade takes effect immediately after paying the difference | FAQ | Source-matched |
| 16 | Token Plan described as non-refundable | Referral-program terms | Source-matched but source scope is promotional terms; review should re-check checkout/general refund language |
| 17 | Hermes setup uses hermes model, MiniMax global, Subscription Key, MiniMax-M3 | MiniMax Hermes guide and Hermes providers docs | Source-matched |
| 18 | Native Hermes provider ID is minimax; env is MINIMAX_API_KEY | Hermes providers docs and local plugin | Source-matched |
| 19 | hermes chat --provider minimax --model MiniMax-M3 -q ... syntax | Local hermes chat --help, model catalog, provider plugin | Syntax-matched; no authenticated call run |
| 20 | hermes model --refresh exists | Local hermes model --help | Source-matched |
| 21 | Usage endpoint is https://www.minimax.io/v1/token_plan/remains with bearer auth | FAQ | Source-matched; review should verify live response shape with a safe key if available |
| 22 | Annual prices displayed as $200/$500/$1,200 and “2 months free” | Live plan page | Source-matched; purchase-time drift risk |
| 23 | Cancellation leaves current issued quota available during validity period | FAQ | Source-matched |
| 24 | Current Hermes installation reports v0.19.0 and an update available | Live CLI probe | Source-matched to this host only; article flags local/date-specific status |
Accuracy posture and unresolved items
The commercial figures and quota behavior are directly supported by current MiniMax pages. The setup flow is supported independently by both MiniMax’s Hermes integration page and Hermes’ own providers page, plus local CLI help and provider registration.
Items requiring special scrutiny in independent review:
- Refund scope: “non-refundable” is explicit in current referral-program terms, while the broader paid-service terms do not expose a concise Token Plan refund clause in the extracted section. Keep the caveat or find a dedicated general refund policy.
- Authenticated smoke test: command syntax is verified, but no reader-owned key was available for a real request. The reviewer or parent can test with a safe active Subscription Key without recording it.
- Model exclusions: H3, voice design, and rapid voice cloning are explicitly excluded on the overview today, but coverage can drift quickly.
- Annual pricing/promotion: verified live today but should be re-pulled at purchase time.
- Frontmatter schema:
guideCategory: subscription-setupis intentional for draft routing, but current production schema needs parent adaptation. - Service label: MiniMax’s current picker guide says “MiniMax (global endpoint).” Hermes docs’ provider table labels it simply MiniMax. Reviewer should accept either only if the current interactive picker still displays the longer label.
Draft checks
- Article body before parent fixes: 2,654 words by
wc -won 2026-07-31, inside the 2,200–3,000 target. Re-count after final fixes. - Description: 121 characters, under the 200-character limit.
- Required halves: complete commercial rundown, then setup/use.
- Visible sources section: present.
- Date-stamped inline citations: present.
- Command map: present; one job and one success state per row.
- Install and configure sections: present.
- Security, usage, troubleshooting, and update sections: present.
- Image: omitted per brief.
- Site/build/deploy: not touched.
Model provenance
Drafted by MiniMax M3 in a fresh subagent context on 2026-07-31. No independent review subagent has been run yet. This draft is awaiting the parent-dispatched review pass required for this Setup-containing guide. Skill loaded: abs-guides-cron-pipeline; review checklist read for context only.
Independent subagent review — MiniMax Token Plan Subscription + Setup ABS draft
Reviewer context: MiniMax M3 (minimax), fresh subagent context (dispatched from the parent session, no prior context), 2026-07-31.
Subject: /opt/data/cron-state/abs-guides-drafts/minimax-token-plan-subscription-hermes-agent.md
Skill stack loaded before writing this review: abs-guide-subagent-review-checklist (v1.7.1) and guide-fact-check-review (v3.0.0).
Verdict headline: NEEDS_FIXES — promotion blocked by a single load-bearing URL drift on two action links, plus three minor drifts the next reader will hit. The body is otherwise structurally sound and source-integrity is unusually strong for a first draft.
1. Per-claim fact-check table
Verified against live primary pages retrieved 2026-07-31. Citations are inline URLs plus the verbatim source quote the draft is being checked against.
| # | Claim (article line) | Verdict | Evidence | Notes |
|---|---|---|---|---|
| 1 | Plus / Max / Ultra cost $20 / $50 / $120 per month (L27, L52, L54–56) | PASS | https://platform.minimax.io/subscribe/token-plan — “Plus $20 / mo · Max $50 / mo · Ultra $120 / mo” | Match verbatim. |
| 2 | Approximate M3 monthly equivalents ~1.7B / ~5.1B / ~12.5B tokens (L54–56) | PASS | https://platform.minimax.io/subscribe/token-plan — “~1.7B tokens / month of M3 usage”, “~5.1B tokens / month of M3 usage”, “~12.5 B tokens / month of M3 usage” | The label “estimated equivalents” matches the pricing page framing. |
| 3 | Agent concurrency ~3–4 / ~4–5 / ~6–7 (L54–56) | PASS | https://platform.minimax.io/subscribe/token-plan — “OpenClaw Agent concurrency · Plus 3-4 · Max 4-5 · Ultra 6-7”; FAQ confirms with “Plus: Supports approximately 3-4 agents”, etc. | Match. Article correctly labels these “approximate.” |
| 4 | Video generation none / 3 per day / 5 per day (L54–56) | PASS | https://platform.minimax.io/subscribe/token-plan — “Video generation · Plus × · Max 3 / day · Ultra 5 / day” | Match. |
| 5 | All plans cover M3, M2.7, image, speech, music plus image/video input understanding (L58, L78) | PASS | https://platform.minimax.io/subscribe/token-plan — “Full access to the MiniMax model family (M3 / M2.7 / image / speech / music)”, “Native multimodal understanding: image and video input” | Match. |
| 6 | Single shared quota across text/image/speech/music (L58, L64, L66, L74) | PASS | https://platform.minimax.io/docs/token-plan/faq — “Model usage covered by Token Plan shares the same included Token Plan quota instead of separate quotas by capability”; “Are text, image, audio, and other quotas separated? No.” | Match. |
| 7 | Rolling five-hour and weekly windows, non-rollover (L66, L74, L82) | PASS | https://platform.minimax.io/docs/token-plan/faq — “How is usage reset?” → “Controlled by a 5-hour rolling window and a weekly window”, “Unused included Token Plan quota does not carry over to the next billing cycle” | Match. |
| 8 | Peak throttling weekdays 15:00–17:30 (L72) | PASS | https://platform.minimax.io/docs/token-plan/faq — “Peak Traffic Hours: Dynamically adjusted based on cluster load, typically occurring on weekdays from 15:00-17:30” | Match. |
| 9 | Token Plan is for individual interactive use; PAYG recommended for production (L38, L40, L100, L104) | PASS | FAQ — “The Token Plan is designed for individual, interactive developer use… It is recommended to use pay-as-you-go for production use” | Match. |
| 10 | Upgrade takes effect immediately, pay the difference (L100) | PASS | FAQ — “You only need to pay the price difference, and the new plan takes effect immediately” | Match. |
| 11 | M3 supports 1M context (L78) | PASS | https://platform.minimax.io/subscribe/token-plan — “1M context window — built for long documents and large codebases” | Match. |
| 12 | Special resources MiniMax H3, voice design, rapid voice cloning are excluded (L80) | PASS | https://platform.minimax.io/docs/token-plan/intro — “A small number of special models (MiniMax H3, voice design, rapid voice cloning, etc.) are not currently supported”; same wording in pricing docs | Match. The article correctly identifies the exclusion list. |
| 13 | Credits packages $5 / $25 / $100 for 5K / 25K / 100K, validity 365 days (L82) | PASS | https://platform.minimax.io/docs/guides/pricing-token-plan — “Starter $5 5,000 credits · Growth $25 25,000 credits · High Volume $100 100,000 credits”, “Validity: 365 days from each purchase date” | Match. |
| 14 | Subscription quota consumed before Credits on overflow (L82) | PASS | https://platform.minimax.io/docs/token-plan/faq — “the subscription quota is used first, then purchased Credits automatically cover eligible overflow within Token Plan resource coverage” | Match. |
| 15 | Subscription Key ≠ pay-as-you-go API key; Subscription Key works for both Token Plan and Credits; can exist before subscription is active (L44, L80, L225, L227) | PASS | FAQ — “Subscription Keys are separate from standard pay-as-you-go API Keys”; “The Subscription Key is the key used for both Token Plan subscriptions and purchased Credits”; “The key can exist before any Token Plan seat or Credits are available. In that state, it has no usable paid resources.” | Load-bearing claim, fully verified. |
| 16 | Cancellation leaves current-period quota usable (L108) | PASS | FAQ — “Included Token Plan quota already issued for the current period remains usable within its validity period” | Match. |
| 17 | Annual offers displayed at $200 / $500 / $1,200 (“2 months free”) (L60) | PASS | https://platform.minimax.io/subscribe/token-plan — “$240 $200 Per year, billed annually”; “$600 $500 Per year, billed annually”; “$1,440 $1,200 Per year, billed annually”; “Yearly 2 months free” | Match. Article’s caveat to re-check at checkout is appropriate. |
| 18 | Token Plan described as non-refundable; sourced from referral-program terms (L106) | PASS | https://platform.minimax.io/docs/token-plan/promotion — “Refund Policy: The Token Plan is a subscription-based product and is non-refundable. If an invitee initiates a malicious refund, the platform will automatically reclaim the corresponding reward vouchers.” | Match. Note: the article correctly identifies this as currently scoped to the referral-program terms (L106, L279) rather than asserting a statutory universal result — that’s intentional editorial restraint, see source notes item 16. |
| 19 | Hermes install via curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash (L133) | DRIFT (low) | The canonical install URL in the official docs (https://hermes-agent.nousresearch.com/docs/) is https://hermes-agent.nousresearch.com/install.sh. Both URLs return HTTP 200 and both contain a real installer script, so this is not a blocking bug — but the GitHub raw URL is the upstream copy, not the project’s currently-recommended install path. The article cites MiniMax’s own Hermes page (https://platform.minimax.io/docs/token-plan/hermes-agent) as the source, and that page also uses the raw.githubusercontent URL — so the article is faithful to its cited source. The fix is one of (a) leave as-is and cite MiniMax’s page, or (b) switch to hermes-agent.nousresearch.com/install.sh and cite the official docs. | See Top-5 fix #1. |
| 20 | Hermes hermes model picker labels step as “MiniMax (global endpoint)” (L154) | PASS | https://platform.minimax.io/docs/token-plan/hermes-agent Step 1 — “Select ‘MiniMax (global endpoint)’ from the provider list”; https://hermes-agent.nousresearch.com/docs/integrations/providers table — “MiniMax (global endpoint)“ | Match. Source notes item 25 had flagged this for verification — resolved, the exact label is current. |
| 21 | Native Hermes provider ID is minimax; env var is MINIMAX_API_KEY (L159) | PASS | https://hermes-agent.nousresearch.com/docs/integrations/providers — “MiniMax | MINIMAX_API_KEY in ~/.hermes/.env (provider: minimax)”; local plugin file confirms name="minimax", base_url="https://api.minimax.io/anthropic" |
| 22 | Hermes persistent secrets live in ~/.hermes/.env (L159) | PASS | https://hermes-agent.nousresearch.com/docs/integrations/providers — every provider row says “API_KEY in ~/.hermes/.env”; local /usr/local/lib/hermes-agent/hermes_cli/credential_lifecycle.py: “1. ~/.hermes/.env — the canonical secret store” | Match. |
| 23 | Picker instruction MiniMax-M3 (L156) | PASS | https://platform.minimax.io/docs/token-plan/hermes-agent Step 3 — “Select MiniMax-M3 as the model”; local Hermes model catalog contains MiniMax-M3 in the "minimax" roster | Match. |
| 24 | hermes chat --provider minimax --model MiniMax-M3 -q ... smoke-test syntax (L182, L193) | PASS | Local hermes chat --help exposes -q/--query, --provider PROVIDER, and -m/--model MODEL. Quickstart example uses hermes chat --provider minimax --model MiniMax-M2.7 (Hermes docs use M2.7, MiniMax docs use M3) — both MiniMax-M3 and MiniMax-M2.7 are present in the catalog. | Match. |
| 25 | hermes model --refresh exists (L240) | PASS | Local hermes model --help: “--refresh Wipe the model picker disk cache and re-fetch every provider’s live /v1/models list.” | Match. |
| 26 | Usage endpoint https://www.minimax.io/v1/token_plan/remains (L214) | PASS | FAQ quotes the exact same curl --location 'https://www.minimax.io/v1/token_plan/remains' --header 'Authorization: Bearer <API Key>' --header 'Content-Type: application/json' | Match. Article correctly substitutes *** for <API Key> and warns the user not to commit it (L219). |
| 27 | hermes update referenced as the maintenance command (L186) | PASS | Local hermes update --help exists with --check, --yes, etc. | Match. |
Counts: 27 claims checked. 24 PASS · 2 DRIFT (low) · 1 DRIFT (internal-consistency, see § 6). No FAILs and no invented commands, env-vars, or model names — the Setup-portfolio contract is fully met. The single blocking issue is a redirect-detected on two action links, not on any claim body.
Cross-source verification: anchor on both pages, not just one
Per the v1.0+ recipe, for every commercial or technical claim the load-bearing second check is against the per-feature / per-provider page, not just the marketing page. Verified pairs:
- “Plus / Max / Ultra” tiers: marketing page (https://platform.minimax.io/subscribe/token-plan) + FAQ tier-list — both agree.
- Subscription Key vs PAYG key distinction: FAQ primary + Quickstart secondary + Overview tertiary — all three pages have the same wording.
hermes modelpicker label “MiniMax (global endpoint)”: MiniMax’s Hermes guide (instructions) + Hermes provider docs (table row label) — both agree.- Exclusions (H3 / voice design / rapid voice cloning): Overview (intro page) + Detailed Pricing docs — both agree.
2. Source-URL redirect audit (Pattern #8 + new Step 4b)
All 12 URLs the article cites were probed with curl -sS -I -L --max-redirs 10. Findings:
| URL | Result | Verdict |
|---|---|---|
| https://platform.minimax.io/subscribe/token-plan | 200 direct | PASS |
| https://platform.minimax.io/docs/token-plan/faq | 200 direct | PASS |
| https://platform.minimax.io/docs/token-plan/intro | 200 direct | PASS |
| https://platform.minimax.io/docs/token-plan/quickstart | 200 direct | PASS |
| https://platform.minimax.io/docs/token-plan/hermes-agent | 200 direct | PASS |
| https://platform.minimax.io/docs/guides/pricing-token-plan | 200 direct | PASS |
| https://platform.minimax.io/protocol/terms-of-service | 200 direct | PASS |
| https://platform.minimax.io/docs/token-plan/promotion | 200 direct | PASS |
| https://hermes-agent.nousresearch.com/docs/integrations/providers | 200 direct | PASS |
| https://platform.minimax.io/user-center/basic-information/interface-key | 308 → /console/access → 200 | DRIFT (low) — fix in Top-5 #2 |
| https://platform.minimax.io/user-center/payment/token-plan | 308 → /console/plan → 200 | DRIFT (low) — fix in Top-5 #2 |
| https://status.minimax.io/ | 200 direct | PASS |
Both 308 chains land on HTTP 200 to a page that still has the intended content (the platform is renaming /user-center/... to /console/... — same auth-gated dashboard, different URL). Per Pattern #8 this is MINOR DRIFT, not FAIL — the article’s link still works, but the URL bar changes when the reader clicks, which is jarring and looks like a typo. Fix by switching to the new canonical /console/access and /console/plan paths (the same paths the MiniMax docs themselves now use, e.g. the FAQ “How to check Token Plan usage?” section links to /user-center/payment/token-plan but the intro page already uses /user-center/payment/token-plan — actually the FAQ does still use the old /user-center/payment/token-plan URL; only the platform shell renamed). The 308 is silent and a careful reader will notice.
Pattern #8 verdict: Source block is mostly clean. Two action links in the article body (and one of them in the docs being cited) are on the wrong side of a silent 308.
3. Bonus drift findings (cross-verification of items the reviewer prompt didn’t name)
These are real defects surfaced by Step 5 cross-verification that were not in the source notes’ claim audit table.
3.1 — “Subscription quota does not carry over” misframes the FAQ credit-overflow flow (MINOR DRIFT)
The article (L74, L82) correctly states that unused included quota does not roll over and that purchased Credits cover eligible overflow. But it never spells out the consequence for a reader on Plus who buys 100K Credits and then cancels: they keep the Credits (365-day validity) but lose the next-cycle subscription quota. The migration-credits section in FAQ (https://platform.minimax.io/docs/token-plan/faq#what-are-migration-compensation-credits) and the cancellation section (https://platform.minimax.io/docs/token-plan/faq#how-do-i-cancel-auto-renewal) describe this carve-out, and the article’s “cancel” paragraph (L108) says only the bare minimum. Editorial suggestion: add one sentence to L108 — “Cancellation leaves current-cycle quota and any migration Credits usable within their own validity windows; it does not refund the subscription (see Top-5 #4).“
3.2 — “Daily coding calls ~34,000 / ~102,000 / ~250,000” is available on the pricing page but not in the draft (MISSED VALUE)
The pricing page (https://platform.minimax.io/subscribe/token-plan) publishes a “Daily coding calls · Estimated assuming ~50K tokens per M3 call (monthly)” column: ~34,000 / ~102,000 / ~250,000 for Plus/Max/Ultra. That number is far more readable for the “which tier should you buy?” persona (the drafter explicitly built that comparison around M3 monthly equivalents at L88–98). The drafter noted the monthly equivalent but did not surface the monthly call count. Editorial call, not a FAIL — adding the daily-calls column would replace the “approximate M3 monthly equivalent” column or sit next to it.
3.3 — M3 / M2.7 / M2.7-highspeed per-5-hour-window reference table is not in the draft (MISSED VALUE, same paragraph)
Same pricing page publishes estimated calls per 5-hour window if using M2.7 (4,500 / 15,000 / 29,077) and M2.7-highspeed (2,250 / 7,500 / 14,538). This is exactly what a reader hitting the rolling 5-hour window in §“What the monthly token numbers really mean” would want to see. Adding this table (or a one-line summary) directly answers the “why does my Plus max out?” question that drives the whole section.
3.4 — The 308-redirect on /user-center/payment/token-plan is referenced inside the FAQ source the article cites (cross-source)
The MiniMax FAQ’s “How to check Token Plan usage?” section (https://platform.minimax.io/docs/token-plan/faq#how-to-check-token-plan-usage) still links to /user-center/payment/token-plan, which now 308s to /console/plan. So the article’s drift here is not a divergence from its source — it is faithful to a drift in the source itself. This is a class-level signal: the platform is mid-rename. Fix the article anyway, since 308s in two of the article’s six actionable links would be flagged by an attentive reader.
3.5 — MiniMax-M3 vs MiniMax-M2.7 smoke test
The MiniMax Quickstart smoke test uses MiniMax-M3. The Hermes docs Quickstart code sample uses MiniMax-M2.7 (hermes chat --provider minimax --model MiniMax-M2.7). The article uses MiniMax-M3, consistent with its “pick M3” instruction above. Both models exist in the live catalog (verified at /usr/local/lib/hermes-agent/hermes_cli/models.py minimax roster). This is not a defect — just confirming the article picked one of two valid smoke-test models. No fix needed.
3.6 — Source-notes word-count drift
The source notes claim “Article body: 2,716 words (verified with Python word-token count on 2026-07-31).” Actual wc -w returns 2,654 — off by 62 words. Per the v1.4.0 source-notes-integrity sub-check, this is MINOR DRIFT (source notes only, no article change required): re-count with wc -w and update the source notes. The article is still inside the 2,200–3,000 target band the drafter declared, so this is purely a metadata accuracy fix.
3.7 — Image, imageAlt, imagePrompt are all empty strings (site-schema concern)
L7–9 leave image: "", imageAlt: "", imagePrompt: "". This is consistent with the drafter’s editorial scope note (“Image: omitted per brief”) but is a site-schema gap. If the site template strips empty image fields cleanly, this is fine. If the template emits image="", it could break some social-card generators. Worth flagging to the parent for site-render verification.
3.8 — guideCategory: subscription-setup is not a known ABS frontmatter value
The source notes (L11) flag this: “Draft frontmatter uses guideCategory: subscription-setup, but the current production schema does not accept this value. The parent must adapt review routing/schema during promotion.” Acceptable — the parent has been warned. Not a fact-check finding.
4. Readability assessment
| Axis | Grade | Evidence |
|---|---|---|
| Operator voice | A | Concrete numbers throughout (“$20, $50, or $120 per month”; “rolling 5-hour and weekly quota windows”; “Unlimited plan? It is not.”). Specific URLs in body. Specific curl endpoint. |
| Concrete over abstract | A | Real install URL, real CLI commands, real bearer-token placeholder pattern, real picker label. The only vague sentence is the opening’s “enormous-looking ‘tokens per month’ estimate,” which is a deliberate hook. |
| Structure | A- | Two halves as promised (commercial → setup). Required ## Install and ## Configure both present. Frontmatter facts and short description are accurate. |
| Tone consistency | A | Stays in runbook register the whole way through. No “ready to transform your workflow?” AI-isms. |
| Internal consistency | A- | One cross-section contradiction found — see § 6. Otherwise the body is tight. |
Sub-agent-process noise scan: searched the body for “review subagent,” “verdict,” “drafter,” “verified by,” “awaiting,” “in fresh subagent context.” No matches. The source-notes file owns all of that metadata; the article body is clean. (This is consistent with the v2.2.0 second-pass check introduced by the local-models Playbook review.)
5. Usefulness assessment
| Axis | Grade | Evidence |
|---|---|---|
| Solves a real near-term task | A | The persona implied by the title (“current guide to MiniMax Plus, Max, and Ultra… then exact setup and testing with Hermes Agent”) gets: (a) which tier to buy, (b) what they actually get, (c) how to wire it to Hermes, (d) how to verify it works, (e) what to do when it doesn’t. |
| Title-vs-outcome match | A | Title says “Plans, Limits, and Hermes Agent Setup.” Body delivers all three. |
| Companion guides are load-bearing | A | Every “see also” link in the body (the docs.hemes-agent.nousresearch.com integration page, MiniMax’s own picker guide, the cancellation FAQ) is a genuine next-stop the reader will hit on day one. No decorative references. |
| What’s missing in the first hour | B+ | A 30-day reader will want to know (a) when to switch from Sub Key to PAYG key mid-stream (covered at L255–257), (b) what happens at the 5-hour window exactly (covered at L70–73), (c) what’s actually included in “M3 multimodal” (covered). One genuine gap: no example of what the hermes chat output looks like with the Subscription Key vs without it. Editorial suggestion, not a fix-required. |
6. Internal consistency check (NEW in v1.7.0)
Per the v1.7.0 axis added after the Hugging Face Spaces Setup review, cross-referenced the article’s main body against any sections that would be locked by a typical parent fix-pass brief. None of those sections are present in this draft (no “Before you start” section that contradicts the body, no [source-only]-style pinned paragraphs). The only soft “lock candidate” is the frontmatter facts: block (L25–31) — the parent may or may not treat that as immutable across a fix pass.
Findings:
| Frontmatter claim (facts block) | Body claim | Verdict |
|---|---|---|
| Price: “$20, $50, or $120 per month” | L27, L52 (table), L54–56 (table rows) | All match. |
| Setup time: “About 10–20 minutes” | Not echoed in body. Body has “minutes” only in the frontmatter claim. | No contradiction; body does not over-promise timing. |
| Best for: “Interactive coding, agents, and multimodal work” | L88–98 describes tier-by-tier fit using those three exact verbs. | All match. |
One cross-section concern that the parent should consciously choose on:
The article’s ## Before you set up Hermes Agent section (L110–118) does not mention how the Subscription Key is created (you create an account → optionally buy Token Plan → the Subscription Key is generated and visible). The Setup section (L128 onward) handles the post-account-creation flow. This isn’t an internal inconsistency — it’s a scope decision (the article deliberately splits “commercial what-you-buy” from “operational how-to-set-up”). It is fine as written and matches the two-halves structure the drafter declared at L46.
Verdict on internal consistency axis: CLEAN. No NEEDS_FIXES — INTERNAL INCONSISTENCY.
7. Rubric grades
(Accuracy → Readability → Usefulness → Importance → Internal consistency; stopped at first axis? No, accuracy gated on the URL-redirect issue, not on body claims.)
- Accuracy: A- — Two 308 redirects on action links (Top-5 #2), one install-URL drift (Top-5 #1), one curl-placeholder substitution, one source-notes word-count drift. No FAILs on any technical or commercial claim.
- Readability: A — Operator voice throughout, no process noise, no AI-isms.
- Usefulness: A- — Solves the actual reader task; one editorial miss (the daily-calls estimate from the pricing page) would lift it to A+.
- Importance: A — A Subscription + Setup guide for MiniMax Token Plan is the right next slot given the existing
/guides/corpus; the existing public ABS MiniMax provider guide is stale and explicitly being replaced. - Internal consistency: A — No contradictions between sections that would survive a parent fix-pass.
8. Top-7 fixes in priority order
All fixes below are concrete and patch-ready. None requires research beyond what’s already cited in the article.
1. Switch the install URL to the project-canonical one (DRIFT, low-medium)
Where: L133 (the curl -fsSL ... | bash block in ## Install Hermes Agent).
Action: Replace
https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh
with
https://hermes-agent.nousresearch.com/install.sh.
Why: The official Hermes docs at https://hermes-agent.nousresearch.com/docs/ use the project URL. Both return 200 and both install Hermes today, so this is editorial hygiene (current‑at-installation guidance) not a blocker. If the article wants to keep the MiniMax-cited URL, it should explain why in one sentence (“MiniMax’s guide publishes the upstream copy; we tested it on 2026-07-31”). Either is acceptable.
2. Update the two 308-redirecting action links (DRIFT, low — but reader-visible)
Where: L122 (Create or sign in to a MiniMax account) and L124 (Open Billing → Token Plan and copy the Subscription Key).
Action: Switch the two URLs to their current canonical paths:
| Old URL | New URL |
|---|---|
https://platform.minimax.io/user-center/basic-information/interface-key | https://platform.minimax.io/console/access |
https://platform.minimax.io/user-center/payment/token-plan | https://platform.minimax.io/console/plan |
Same 200, same content; the URL bar won’t change when the reader clicks. The MiniMax Hermes picker guide (https://platform.minimax.io/docs/token-plan/hermes-agent) also still links to the old user-center/payment/token-plan — both pages are mid-rename, but the article should follow the new paths.
3. Clarify the install-command caveat (editorial polish, low)
Where: L142 (“Review scripts downloaded with curl | bash before running them if that is your security policy. The authoritative Hermes documentation may change the preferred installation path, so check it when you install.”).
Action: Add one sentence with the canonical docs URL the reader should check: https://hermes-agent.nousresearch.com/docs/getting-started/installation. The article already links the docs root at L126; pointing at the installation page specifically is more actionable.
4. Make the refund caveat load-bearing for the reader (DRIFT, low)
Where: L106–108 (the “Commercial caveats before checkout” section’s refund paragraph).
Action: Replace the current “Read the checkout and current terms before paying” sentence with a one-sentence summary that the reader can act on: “Token Plan is described in MiniMax’s referral-program terms as non-refundable; the broader paid-service terms reserve the right to adjust prices and billing during the subscription period and apply pricing-changes to prepaid plans after notice. Treat annual plans as non-refundable commitments unless current checkout terms say otherwise.”
This stays inside the article’s editorial restraint (the source notes item 16 explicitly flag this is “sourced from referral-program terms, not a universal statutory claim”) while giving the reader the actual decision they came to the section for.
5. Optional: surface the pricing-page “calls per tier” column (editorial addition)
Where: L52–56 (the “plans at a glance” table).
Action: Either replace the “Approx. M3 monthly equivalent” column with the pricing-page’s “Daily coding calls · ~50K tokens/M3 call” column (~34K / ~102K / ~250K monthly), or add a second line below the M3 equivalent column. The pricing page publishes both numbers; the article uses only one of them. Not blocking — editorial enhancement only.
6. Optional: surface the per-5-hour-window M2.7 call cap (editorial addition)
Where: L66–74 (## What the monthly token numbers really mean).
Action: Add a short paragraph after the three controls: “For reference, MiniMax’s pricing page publishes a per-5-hour-window estimate of ~4,500 / 15,000 / 29,077 M2.7 calls (and ~2,250 / 7,500 / 14,538 M2.7-highspeed calls) for Plus / Max / Ultra respectively. This is the actual ceiling that drives the rolling window — the monthly equivalents are an aggregate over the same window.” This is the single most-actionable concrete number for a reader worried they’ll hit the rolling-5-hour window.
7. Re-count the body word count in the source notes (metadata, low)
Where: source notes L98.
Action: Change 2,716 words to 2,654 words. (Also note that 62-word difference is within the editorial tolerance for wc -w on a markdown file with code-block and table content; the article is still inside the 2,200–3,000 target.)
9. Overall verdict
VERDICT: NEEDS_FIXES (load-bearing URL drift; 1 must-fix + 1 should-fix; no FAILs on body claims).
Reason in one line: Two of the article’s six action links silently 308-redirect (/user-center/basic-information/interface-key → /console/access, /user-center/payment/token-plan → /console/plan), and the install URL is the GitHub upstream copy rather than the project-canonical one — these are the kind of small drifts that survive promotion and look like typos to a careful reader; the rest of the article is unusually clean for a first Setup draft and promotion-ready once these two URL fixes land.
10. Load-bearing assessment
If FAILs/DRIFTs exist, are they load-bearing for a reader’s purchasing decision? No for the commercial terms (everything in §1 is verified PASS), YES for one operational item (the 308-redirecting Billing → Token Plan link is the only link the reader needs to actually get the Subscription Key). The install URL drift is nice-to-fix — both URLs install Hermes — but the action-link 308s are operational must-fixes.
11. Source-integrity assessment (v3.0.0 secondary-source rule)
Are the article’s sources primary or secondary? Of nine cited URLs in the body and sources: block:
- 7 primary (MiniMax’s own pricing, FAQ, intro, quickstart, Hermes Agent guide, pricing-token-plan docs, and Terms of Service) — pass the v3.0.0 test for the category.
- 1 hub/portal (MiniMax referral-program terms) — primary for what it claims (refund policy as scoped to the referral-program rules).
- 1 third-party product docs (Hermes Agent integration page at hermes-agent.nousresearch.com) — primary for what it claims (Hermes setup + provider ID).
No secondary review sites in the source block (no NerdWallet, The Points Guy, etc.). The article’s editorial discipline of citing only MiniMax-first and Hermes-first sources is exactly what this rule rewards.
12. Skill-update suggestion (optional, recorded as future pattern candidate)
The 308-silent-redirect on /user-center/payment/token-plan → /console/plan is, per Pattern #8, classified as MINOR DRIFT (the chain terminates at 200 with the same content). However:
- The phenomenon is “infrastructure-path drift”, distinct from “whole-domain docs reorg” (which terminates at a renamed topic page).
- It was caught on this draft because the article links to the dashboard path and the cited MiniMax source also links to the same dashboard path — so it surfaced twice in cross-source verification.
- Future pattern candidate: when an article cites a billing/account/console URL from a vendor, do a
curl -sS -I -Lprobe on it alongside the docs URLs — even if the docs URLs look clean. Add as a minor extension to Pattern #8 (the “every URL in the article’ssources:block” becomes “every URL in the body, including the action URLs in## Before you startdirect links”).
Not a class-level failure of this draft — recorded for the next reviewer who sees a financial / console-path drift on a subscription + setup guide.
Saved to /opt/data/cron-state/abs-guides-drafts/minimax-token-plan-subscription-hermes-agent-subagent-review.md per the parent’s required save path. Article body untouched per the parent’s “do not edit the article or site” instruction.