API keys let external tools act on your behalf in Anything. They’re tied to your account, not to any individual project, so a key can work across all your apps. The Anything CLI, CI pipelines, and AI coding agents all use them.
Create a key
Go to Settings in your dashboard and find the API Keys section.
- Click Create key.
- Give it a name you’ll recognize — “Skydive agent” or “GitHub Actions” works.
- Choose an expiry, or leave it set to Never.
- Copy the key. It is only shown once.
Keep it somewhere safe. If you lose it, revoke it and create a new one.
What you can do with a key
CLI and scripting. The Anything CLI can authenticate with a key instead of a browser login, which is what you want for scripts and automated workflows.
CI and GitHub Actions. Set ANYTHING_API_KEY as a secret in your CI environment and the CLI picks it up automatically. No browser, no interactive login.
AI coding agents. Claude Code, Codex, Cursor, and similar tools can drive Anything on your behalf using the CLI. Hand them a key and they can generate apps, send follow-up prompts, check builds, and publish — all from inside their own workflow.
Skydive agents. A Skydive agent with access to the CLI can build and iterate on your Anything apps. Give the agent a key and it can create, generate, and publish without any browser interaction.
Revoke a key
Go to Settings > API Keys and click the menu next to the key, then Revoke. Revoked keys stop working immediately.
Revoke a key any time you think it may have been exposed, or when the tool that used it no longer needs access.
Anything API keys start with anything_. If a key doesn’t start with that prefix, it isn’t an Anything API key.
Set keys as environment variables rather than passing them inline in commands. It keeps them out of your shell history and makes rotation easier later.