What problem does it solve? Agents often conclude they lack a credential for a third-party provider, ask the user for a key, or misdiagnose 401/403 errors, when the box already holds working placeholder credentials that the platform swaps for real keys at the network boundary. ## Core Features & Use Cases - Credential discovery: Read /run/zipbox/placeholders.env as the authoritative list of every provider key the box holds, instead of relying on environment variables that may be missing in non-login shells. - Correct usage rules: Send placeholders verbatim in the provider's documented header or parameter, never overwrite them, never export HTTP_PROXY/HTTPS_PROXY, and never ask the user for a key that already exists. - Failure diagnosis: A symptom table maps 401, 403, 400, 402, 501, missing files, and stale syncs to concrete causes and recovery steps. - Use Case: Before calling the CoinGecko API, source the placeholders file, send $COIN_GECKO_PRO_API_KEY in the x-cg-pro-api-key header, and let the platform boundary substitute the real key and bill the correct wallet. ## Quick Start Read /run/zipbox/placeholders.env to list the available provider credentials, then send the relevant placeholder value exactly as the provider's documentation specifies.
