Subscription keys & package tiers

SpiderGate now understands two different kinds of paid LLM key, and meters them differently.

Two kinds of paid key

• Metered (paid) — an API key billed per token or per credit (OpenAI, Anthropic, xAI, fal, kie…). You pay for exactly what you use.

• Subscription — a flat-monthly coding plan (MiniMax, Z.ai/GLM, Qwen, Claude, Codex, Gemini). You pay a fixed fee and get an allowance inside a rolling window.

Until now the vault could only tell these apart by provider. You can now mark any key as a subscription — including a pasted API key, not just an OAuth login.

Marking a key as a subscription

In Dashboard → Gate → Vault, open a key (Add or Edit) and set Billing to Subscription, then choose the package that matches your plan — for example MiniMax Coding — Max or Claude Max 20×. The package tells the vault the size of your window.

A key marked Subscription is always private to your brand — it is never shared into the pool, because a coding plan is tied to one account.

The capacity meter

Once a package is set, the vault shows a live capacity meter — for example 312 / 900 — measuring your usage against that plan's real window (a 5-hour rolling window for most coding plans, plus a weekly cap where the plan has one). Before you pick a package the meter shows a dash, because there is no window to measure against yet.

Doing it from the CLI or an agent

The same controls are available headlessly:

• CLI: spideriq gate subscription-tiers --brand <id> --provider minimax to list packages, then spideriq gate keys update <id> --billing-mode subscription --subscription-tier minimax_max.

• MCP: get_subscription_tiers to discover packages, then update_brand_integration (or gate_key_update) with billing_mode + subscription_tier.