peekpandaAuthentication
Use a PeekPanda API credential or the shared OAuth issuer without exposing internal secrets.
Download Markdown ↓Bearer credentials
Send a PeekPanda API credential in the Authorization header. Credentials are owner scoped and the backend resolves their entitlement; a browser supplied actor ID or tenancy header cannot grant access.
OAuth and MCP
MCP clients connect to the remote server and complete consent with the shared issuer for the PeekPanda resource. Tokens are audience pinned. Never put an internal actor signing secret in an MCP configuration.
API keys
Create an API key on /account under API keys. The secret is shown once, so store it in a credential manager, and revoke a key there as soon as you stop trusting it. Every request made with a key, and every MCP call, counts toward the plan's daily allowance: 30 calls a day on Peek and 1,000 on Panda, reset at 00:00 UTC. Extra keys share that one allowance.
Manage API keys →AI agent or LLM? Read this page as markdown