--- id: PX-SPEC-1RR4LU8M type: spec title: MiniMax M Plan Capabilities research: - PX-RESEARCH-TQLVNIM7 --- ## Intent Make current MiniMax M Plan capabilities usable from Pi without switching applications or requiring pay-as-you-go credentials. Preserve built-in LLM behavior; complete missing capabilities and repair affected existing integrations. Use Explore as the primary acceptance account; respect actual Go/Build entitlements without assuming endpoint parity. Remove superseded MiniMax compatibility paths within the affected scope. ## Scope Required: capability/access discovery, subscription usage visibility, web search, image generation, H3 video generation, speech synthesis, and image understanding. Supported operations are callable by Pi's agent, codemode workflows, and configured PiPi children, regardless of the active chat provider. Images participate in Pi's existing image-generation conventions rather than requiring a competing generation interface. Video/audio results are inspectable or retrievable artifacts with truthful task status. Quota remains available through existing quota surfaces; search remains available through the existing web tool, with explicit MiniMax selection possible. Conditional: reference-image generation, video references/regeneration, video understanding, transcription, voice cloning/design/management, music/lyrics/cover, and supporting file operations. Expose conditional operations only after their current integration route and M Plan eligibility are established; otherwise report the specific unsupported or unverified capability. Documented inclusion without verified account execution is not completed capability support. Out: PAYG access or fallback, superseded Coding/Token Plan product compatibility, provider-wide rewrites, arbitrary image-editing parity, a replacement MiniMax application, and a new dashboard. Current M Plan interfaces remain in scope even when route or field names retain Coding/Token Plan terminology. Live hands-free Voice remains owned by its existing external speech service; media generation does not bypass that boundary. ## Behavior Every operation passes a subscription-specific access and spending boundary before execution. ```mermaid flowchart TB request["Requested capability"] --> support{"Current M Plan route supported?"} support -->|no| unavailable["Report unsupported or unverified capability"] support -->|yes| auth{"M Plan credentials match region?"} auth -->|no| blocked["Report credential or region blocker"] auth -->|yes| access{"Account entitlement known?"} access -->|blocked| blocked access -->|unknown| unknown["Report unverified access before any consuming probe"] access -->|eligible| spending{"Spending boundary satisfied?"} unknown --> approved{"Explicit operation or probe approval?"} approved -->|no| stopped["Do not execute"] approved -->|yes| spending spending -->|no| stopped spending -->|yes| run["Execute requested operation"] run --> outcome{"Upstream outcome"} outcome -->|pending| pending["Expose owned task and current status"] outcome -->|completed| result["Return artifacts, provenance, usage when known"] outcome -->|failed| failure["Report actionable failure"] outcome -->|uncertain| uncertain["Report unknown completion without duplicate submission"] ``` ### Access and spending Reuse Pi's credential resolution; do not create a parallel credential store or silently edit user configuration. Resolve credential, service region, endpoint, and billing identity coherently; never send a credential to another region or an unrelated configured host. Reject known PAYG credentials for these operations; an ambiguous credential is not represented as subscription-backed access. M Plan API-key authentication is valid; an OAuth-only subscription flag must not reject a known M Plan key or classify it as PAYG. Credential identity, account tier, per-operation access, and spending authorization remain distinct; a credential prefix or catalog entry alone establishes none of the latter three. Missing authentication, unverified access, confirmed entitlement failure, exhausted allowance, temporary rate limiting, and incompatible upstream behavior remain distinguishable. Automatic discovery and quota inspection issue no consuming capability probes, including search or understanding requests. An explicitly requested operation or separately approved verification probe may establish previously unknown access after disclosure of uncertainty and expected allowance consumption. Live acceptance calls require approval before consuming allowance; approval authorizes execution, not a claim of verified support. Successful execution establishes observed access for that operation, model, account, and region at that time, not universal entitlement or included-allowance-only billing. M Plan credentials can automatically consume purchased Credits after included allowance. Prefer an enforceable included-allowance-only boundary; if it cannot be enforced, disclose possible Credits consumption and require explicit approval covering that risk before execution. Do not claim quota preflight prevents overflow, especially with concurrent requests. No rejected, unsupported, cancelled, timed-out, or rate-limited operation silently changes credential, provider, region, or billing class. ### Capability and artifact contracts Declare each supported operation's accepted inputs, output forms, upstream limits, and known account restrictions. Validate locally knowable unsupported options before submission; preserve truthful upstream rejection otherwise. Reference-image generation must not be advertised as arbitrary editing or inpainting. Use normal chat vision where it already provides the required understanding; additional understanding operations must declare their distinct access route. Return image artifacts in a form Pi and the requesting agent can inspect and reuse. Audio/video results identify format, location, originating operation, and any retrieval expiry; do not label submission acknowledgments as finished media. Write persistent artifacts only to caller-authorized destinations; never overwrite existing files without approval. Downloads and remote file operations remain bounded by authorization, cancellation, response size, and the owning request. Permit narrowly validated upstream artifact-storage destinations, including third-party storage; provider-domain ownership is not a requirement for an artifact host. Retrieve artifacts over HTTPS without forwarding API credentials; validate every redirect destination or reject redirects. An HTTP artifact URL is not permission for cleartext retrieval; HTTPS upgrading must preserve successful retrieval or fail explicitly, never silently downgrade. Reject destinations that would expose credentials or access local/private resources, including through redirects or address resolution. Treat signed artifact URLs as sensitive download access; redact signatures and query credentials from diagnostics and ordinary status output. Unknown retrieval expiry remains unknown rather than receiving an invented lifetime. ### Long-running work Expose pending, completed, failed, cancelled, and unknown-completion outcomes without blocking unrelated Pi work. Retain sufficient task identity to inspect or retrieve an acknowledged remote job after a local wait is interrupted, without resubmitting generation. Requests and artifacts retain session ownership under concurrent agent and PiPi use. Cancellation of one operation does not cancel unrelated work. Distinguish local cancellation, confirmed upstream cancellation, and deletion of a terminal task record; never promise refunded usage. Never automatically repeat a consuming submission whose upstream completion is unknown. Partial artifacts remain distinguishable from a complete requested result. ### Search, quota, and accounting Explicit MiniMax search requests either use MiniMax or report its failure; they never silently succeed through another provider. Preserve existing non-MiniMax search behavior outside explicit MiniMax requests. Show non-video five-hour and weekly allowance, video-relevant weekly allowance, and reset times only to the extent supplied reliably by upstream. Represent shared allowance without double counting per-model views; do not invent a five-hour video limit or separate video allowance when upstream supplies only a general pool. Treat an established shared/general pool as account-wide, not model-specific. The footer selects the most-consumed applicable account-wide window; higher weekly usage remains visible even when five-hour usage is lower, with five-hour preference only on equal usage. Keep model-specific and video-only limits out of account-wide comparisons when they do not constrain every applicable request. Keep included quota, purchased Credits, and request-rate admission distinct. Missing measurements are unknown, not zero; ambiguous zero absolute counts must not render as known zero capacity or zero remaining allowance. Preserve independently reported percentages and reset times; a positive measured total can still establish a genuine exhausted allowance with zero remaining. Unknown tier, absolute capacity, or Credits balance does not block displaying reliable supplied quota measurements. Stale observations retain their observation age; quota deltas alone do not attribute consumption to an operation or distinguish included allowance from purchased Credits. Account for media operations as well as chat wherever existing session/footer/history usage surfaces claim coverage. Distinguish catalog-price estimates, provider-reported charges, and subscription quota/Credits consumption. Do not interpret subscription access or absent token counts as free usage. Use actual billing units where known, including images, characters, duration, and requests; unknown charge amounts remain unknown. Requested settings, provider-reported usage, artifact metadata, projected catalog value, and actual monetary/Credits charges remain separately labeled observations. Do not equate requested or provider-reported seconds with exact encoded media duration or a settled charge. Preserve upstream media/token-equivalent usage with provenance; do not infer chat pricing from media token fields. Count one consuming operation once, including across task polling, downloads, parent/child orchestration, and resumed observation. ## Cleanup and constraints Support current M Plan interfaces only; remove demonstrably superseded endpoints, schema branches, fallback chains, settings, fixtures, and documentation encountered within this change. Historical route or field naming alone does not establish obsolescence; retain current interfaces such as `coding_plan/search`, `coding_plan/vlm`, and `token_plan/remains` while supported. Do not add old-to-new compatibility shims or obsolete-route retries. When an obsolete MiniMax configuration is detected, report the required replacement rather than silently migrating or ignoring it. Retain current global/CN service distinctions only where the current M Plan route is established; unsupported regions fail explicitly rather than routing through old APIs. Preserve unrelated providers, dirty work, and established workflows; cleanup is not permission for a repository-wide rewrite. Preserve root installation, isolated sibling extensions, generated settings, and diagnostic contracts. Do not replace or duplicate Pi's built-in MiniMax chat catalog, authentication, or streaming implementation. Do not require Pi core modifications for declared capabilities. Optional integrations degrade explicitly when unavailable; no sibling runtime imports. Diagnostics remain off by default, nonfatal, and free of credentials, prompts, reference media, and complete provider payloads. No new UI layout is required; reuse existing interaction, status, confirmation, and artifact conventions. ## Acceptance criteria - [ ] An eligible Explore account can search, generate an image, generate H3 video, synthesize speech, and request image understanding inside Pi using M Plan credentials without separately billed API credentials. - [ ] Agent invocation, codemode orchestration, and configured PiPi children receive their own usable results, including when another provider supplies chat. - [ ] Image generation uses Pi's existing image-model conventions while built-in MiniMax chat selection, reasoning, tool calls, and authentication remain usable. - [ ] Conditional capabilities distinguish verified support, unsupported routes, unverified entitlement, and confirmed account rejection; public API catalog presence alone never enables them as confirmed support. - [ ] Go's lack of included H3 and Explore/Build's differing usage allowances are respected without invented endpoint parity or restrictions. - [ ] Missing or mismatched credentials, region mismatch, PAYG credentials, quota exhaustion, dynamic throttling, and malformed upstream responses fail explicitly without fallback billing. - [ ] Automatic discovery makes no consuming capability request; separately approved access probes and live acceptance calls disclose uncertainty and consumption before execution. - [ ] Known M Plan API-key authentication remains usable even when Pi's OAuth-only subscription flag is false; credential presence, prefix, and catalog entries are not misrepresented as operation entitlement. - [ ] Possible automatic Credits overflow is either enforceably prevented or explicitly approved; quota preflight alone is never presented as spending enforcement. - [ ] Explicit MiniMax searches report MiniMax provenance or failure; unrelated search behavior remains intact. - [ ] Quota surfaces truthfully distinguish supplied five-hour/weekly limits, video weekly usage, Credits, reset times, unknown values, and stale observations without inventing absent pools or balances. - [ ] Ambiguous zero absolute quota fields display no fabricated capacity; independently supplied percentages/reset times remain visible, while genuine measured exhaustion remains distinguishable. - [ ] Shared/general windows participate in account-wide footer selection: weekly 3% used outranks five-hour 1% used, without promoting unrelated model/video-only scopes. - [ ] Long-running operations stay responsive, preserve remote task identity, recover observation without duplicate submission, and report cancellation and unknown completion truthfully. - [ ] Artifacts are inspectable or retrievable, attributable to the requesting session, and persisted only to approved destinations without unintended overwrites or credential leakage. - [ ] Validated third-party artifact storage works over HTTPS with bounded downloads, safe redirect/address handling, no forwarded API credentials, and redacted signed URLs; unsafe retrieval fails without resubmitting generation. - [ ] Media usage is represented truthfully in affected accounting surfaces, without repeated charges from polling/downloads or fabricated zero-cost/token figures. - [ ] Requested duration, provider usage, artifact duration, projected value, and actual charges remain distinct, including when upstream reports media token-equivalent counts. - [ ] Demonstrably superseded MiniMax compatibility paths and their settings/tests/docs are removed within affected scope, without deleting current routes merely because their names contain Coding/Token Plan terminology; obsolete configuration receives actionable guidance, not a compatibility shim. - [ ] Existing Voice service ownership and unrelated provider workflows remain unchanged. ## Evidence boundary [MiniMax M Plan research](../../research/PX-RESEARCH-TQLVNIM7-minimax-m-plan-capabilities-and-apis/index.md) records current capability promises, APIs, Explore comparisons, and unresolved entitlement/billing details. Minimal global-service probes on 2026-11-09 established operation-specific access with the supplied M Plan key: structured search results, correct red-image understanding, a retrieved/inspected 512×512 generated JPEG, decodable speech MP3, and completed/retrieved/decoded H3 video. The current quota endpoint returned a general pool with zero absolute counts and independently reported five-hour/weekly percentages and resets; no tier or Credits balance was supplied. A signed HTTP image-storage URL retrieved successfully over HTTPS; this demonstrates that artifact, not universal signed-URL rewrite compatibility. H3 requested/provider-reported duration was four seconds while encoded container duration was approximately 4.46 seconds; neither measurement establishes actual charges. These probes establish endpoint feasibility, not complete Pi integration acceptance, Explore tier, speech fidelity, universal entitlement, or included-allowance-only billing. International quota regressions cover current endpoint/key resolution, preserved percentages/resets, unknown zero-count placeholders, and shared-window footer selection through registered `/quota`; updated extension/account execution remains unverified. Automatic Credits controls, conditional-operation access, CN routes, lifecycle/concurrency behavior, and remaining native integration/accounting acceptance still require verification. Unresolved upstream access blocks acceptance of the affected capability rather than weakening the M Plan-only boundary.