API keys
Agents and scripts authenticate with an API key sent as Authorization: Bearer myn_live_…. Keys are created in the app under Agents & API.
Two presets
- Agent: scopes
posts:read,posts:write,channels:read,media:write. Its posts land in your approval queue. The agent can draft, schedule and ask for approval, but can't approve. - Publisher: the Agent scopes plus
posts:publishandvoice:write. It can schedule directly without approval and update the brand voice. Use it for your own trusted scripts.
Neither preset can decide approvals. Only a person signed in to Mynahcast can approve a post, and the server refuses approval decisions that come from an agent or over MCP.
Shown once
The full key is shown only in the response that creates it. Mynahcast stores a hash and a short prefix, so it can't show you the key again. If you lose it, revoke it and make a new one.
Revoking
Revoke a key from the same page. It stops working immediately. You can have up to 20 active keys per workspace.
Treat a key like a password. Don't paste it into a URL, a public repo or a shared prompt. Prefer environment variables in agent configs.