Agent Tools Overview
Let Claude Code, Codex, Cursor and other AI tools generate images and videos on Aibubu, or read these docs to write integration code.
Aibubu offers three ways to connect AI tools. Pick by use case; you can use all three together.
| Option | Best for | Needs | Limits |
|---|---|---|---|
| Agent Skill | Command-line coding agents such as Claude Code and Codex; repeatable generation workflows | Node.js (to install), curl, jq, an API key | Only agents that support skills; rerun the install command to update |
| Remote MCP | Claude, ChatGPT, Cursor, VS Code and day-to-day creation | The MCP URL; sign in with your Aibubu account, no API key and nothing to install | The client must support MCP; only the tools we expose |
| AI docs | Letting an AI read the docs, answer questions and write integration code | Nothing | Docs only; real calls still need an API key |
Get an API key
Remote MCP uses account sign-in and needs no API key. The Agent Skill and direct API calls need one: create it on the API Keys page and keep it in an environment variable, never in project files or screenshots:
export AIBUBU_API_KEY=sk_aibubu_your_api_keyKeys belong to a team workspace; tasks, charges and outputs are recorded there. See Team Workspaces and API Access.
Keep spending under control
AI tools may submit several generation tasks in a row. We recommend:
- When connecting MCP with your account, set a daily credit limit on the authorization page (300 by default).
- When using an API key, create a separate key for AI tools and set a daily credit limit on it.
- Have the AI quote and check the balance before generating. The skill and MCP instructions already require this.
- Disable or delete the key on the API Keys page when you no longer need it.