There is nothing to configure and no documentation for you to read. You paste one line, your agent does the rest, and it asks you only for the things it cannot get itself.
The one-line setup
Open Integrations in Subscribr, copy the line under Agents, and paste it into your agent. It looks like this:
Fetch https://subscribr.ai/agent-setup/prompt.md and follow it to set up Subscribr.
That is the whole thing. Your agent reads our setup guide, installs the tools it needs, and asks you for anything only you can provide — like an access token.
You can paste the same line anywhere you talk to an agent: a terminal, an editor, a chat window, or a task description.
What your agent actually does
The page it fetches is written for agents, not people, so you do not need to read it. For the curious, it tells the agent to:
- Install the Subscribr CLI and API skill from npm. The skill teaches it every operation, the required fields for each, and the rules it must follow.
- Run
subscribr doctor, which confirms the token works and reports which team, role, and plan it is connected to. - List your channels, because nearly every other operation needs a channel ID.
- Ask you before anything that spends credits or changes your production pipeline.
The setup guide is public at subscribr.ai/agent-setup/prompt.md. You can read it, and so can an agent that has not signed up yet.
What your plan needs
Nothing. The API is available on every plan, including free, so any account can create a token and connect an agent.
What is limited is the work, not the access. Generating a script or a batch of ideas spends credits exactly as it does inside the app, some research features depend on your plan, and every endpoint is rate limited. An agent that runs out of credits gets a clear error and should tell you rather than retry.
| What you want | What you need |
|---|---|
| An agent using the CLI or REST API | Any plan. A team admin creates the token |
| A chat assistant connected by signing in | Any plan, including free — see Use Subscribr with AI Clients |
Setting it up by hand
You do not need this if you used the pasted line, but the same setup is three commands:
npm install --global @giltotherescue/subscribr-cli
subscribr-install-skill
export SUBSCRIBR_API_TOKEN=...
subscribr doctor
To run it once without installing globally:
npx -p @giltotherescue/subscribr-cli subscribr-install-skill
subscribr-install-skill installs the skill. subscribr runs the CLI. They are two separate commands from the same package — running npx @giltotherescue/subscribr-cli on its own starts the CLI and installs nothing.
subscribr-install-skill writes the skill into both .agents/skills/ (Codex, Cursor, OpenClaw) and .claude/skills/ (Claude Code) in the current project. The package is also a portable Agent Plugins 1.0 package for plugin-capable clients.
Create your access token on the Integrations page, under Your own code. Give it to your agent as an environment variable or a secret — never paste a token into a chat window, and never commit one.
Letting your agent explore
Once the skill is installed, your agent can learn any operation without guessing or making a test call:
subscribr help # which areas exist
subscribr channels help # actions, and their required flags
subscribr scripts create-channel-script --help # every field, its limits, and an example
All three run locally and make no network request. If an agent ever tells you a Subscribr request failed because a field was missing, pointing it at --help is usually the fix.
Checking it worked
Open Integrations in Subscribr. The Connected panel at the top lists everything with access to your workspace, labelled by kind, with when it last made a request. A new access token appears there as soon as your agent uses it.
Which path should I use?
- Coding agent — use this page. Fastest setup, complete API access, best for automation and repeated work.
- Chat assistant like Claude or ChatGPT — see Use Subscribr with AI Clients. Nothing to install, works on any plan including free.
- Your own scripts — see the API reference. Same token as the CLI.
You can use all three at once. They enforce the same permissions.
Troubleshooting
"It says the token is not bound to a team." The token was not created through the Integrations page. Delete it and create a new one there.
"It says payment is required." The account is out of credits. That is a credit limit, not an access problem — top up and the same request will work.
"It cannot reach Subscribr." The only API host is https://subscribr.ai. If your agent is pointing anywhere else, correct it — and update the CLI, since older versions shipped with a wrong default.
"It keeps getting rejected when creating a script." It is guessing the request body. Have it run subscribr scripts create-channel-script --help, which prints the required fields.
"Nothing appears under Connected." The token has not been used yet. Ask your agent to run subscribr doctor.
Next Steps
- Install the free YouTube Production skill — the full playbook from idea to rendered video
- Connect a chat assistant too: Use Subscribr with AI Clients
- Read the API reference for everything the API exposes
- Learn about Intel research, which is what makes agent output specific to your niche