ZenMux · Builder Plan
How an agent gets a ZenMux · Builder Plan key through KeyKeeper, what to choose on zenmux.ai, and how KeyKeeper verifies it.
| Template id | zenmux-builder (also zenmux-subscription) |
|---|---|
| Field | zenmux-api-key → ZENMUX_API_KEY · secret |
| Key looks like | whether it can be viewed again is unconfirmed |
| Created at | zenmux.ai |
| Verified by KeyKeeper | not verified |
| Template checked | 2026-09-17 |
What the agent does
keykeeper providers show zenmux-builder
keykeeper save --provider zenmux-builder --from-clipboard --create --purpose "what this task does"
keykeeper run -c zenmux-builder -- <your command>--provider zenmux-builder fills in the credential id and the field. The environment
variable is the one ZenMux's own tools read, so nothing has to be mapped.
What only you can do
What to choose
Only save a subscription-specific Builder Plan API key here. It consumes the plan's quota rather than pay-as-you-go balance; do not reuse a pay-as-you-go key.
The agent is told the same thing. It opens the page for you and says what to pick; it never logs in, passes 2FA or pays on your behalf.
What KeyKeeper checks
- Before writing: the value must look like a ZenMux · Builder Plan key (whether it can be viewed again is unconfirmed). A wrong paste is refused before anything is stored, and the agent is told why — without the value.
- After saving: ZenMux · Builder Plan offers no read-only endpoint KeyKeeper can use, so the first real call is the test.
Endpoints
The key is a bearer token for these endpoints. keykeeper run sets only the variables above;
point your client at the base URL yourself.
- OpenAI compatible —
https://zenmux.ai/api/v1 - Anthropic Messages —
https://zenmux.ai/api/anthropic - Google Vertex AI compatible —
https://zenmux.ai/api/vertex-ai
Rotation and expiry
未确认统一有效期;以创建页面显示的实际日期为准,未知时不要猜测。 Rotate or revoke at zenmux.ai.