Create and manage API keys
Create Opskeet API keys for scripts, CI and AI agents that can't sign in. Make them read-only, and delete them anytime.
Updated
On this page
API keys let scripts, CI jobs and agents without OAuth use Opskeet. A key acts as you, on every project you're on.
Create a key
- Go to Settings → AI agents.
- Under API keys, click New key.
- Give it a Name, like "GitHub Actions".
- Turn on Read only if it only needs to look.
- Click Create key, then Copy key.
The key starts with opk_. It's shown only once, so keep it somewhere safe, like a password manager or your CI's secrets.
Use a key
Send it as a Bearer token:
curl https://opskeet.com/api/v1/bootstrap \
-H "Authorization: Bearer opk_…"
With the command line tool, set it as an environment variable:
OPSKEET_API_KEY=opk_… npx opskeet list_projects
Delete a key
Click Delete next to it. Anything using it stops working right away.
Lost a key? It can't be shown again. Delete it and create a new one.
Good to know
- Keys belong to you, not to a project. They can do what you can do.
- The list shows when each key was last used.
- Keys can't create other keys, change billing or manage the team. See What AI agents can and can't do.
Did this help?
Related articles
- Connect Claude, ChatGPT, Cursor and other AI agentsConnect Claude, ChatGPT, Cursor, Claude Code, VS Code or Codex to Opskeet with MCP to answer chats, write articles and read reports.
- What AI agents can and can't doThe permissions, limits and safety rules for AI agents and API keys connected to Opskeet, and how to keep them to notes only.
- Use Opskeet from the command lineInstall and use the Opskeet CLI to work with your inbox, contacts, help center and analytics from the terminal, scripts and CI.
- Use the REST APIOpskeet's REST API covers almost everything the app does. Authenticate with an API key, find the reference, and handle errors.