Developer API & integrations · AI agents & automation
Connect your own AI agent to your platform
Prefer your own external AI agent over the built-in assistant? Point an open-source generator like CLI Printing Press at the public spec to produce a command-line tool, agent skill, or MCP server — powered by a scoped key you control.
Built-in assistant vs. your own agent
Your admin already includes an AI assistant (Benny by default — you can rename it) that makes changes for you in plain language with no setup. That's the right choice for most creators. This guide is for admins who want their own external agent — a coding assistant, a personal automation bot, or a custom agent — to operate the platform through the API.
How the connection works
Your platform publishes a machine-readable OpenAPI spec and an agent manifest describing all 170+ tools. An open-source generator such as CLI Printing Press reads those and produces a clean command-line tool, an agent skill, and an MCP server for your platform. Your agent then calls those commands using a per-platform API key you create — and can carry out requests like "publish the new videos in the Mobility collection" or "generate a blog post from yesterday's class."
You stay in control
The key you hand your agent is limited to the scopes you pick and locked to your platform. Don't want an agent deleting or publishing? Don't grant those scopes. Start read-only and expand only when you're comfortable. You can edit a key's scopes or revoke it instantly at any time, and every call the agent makes appears in your API activity log.
One caution: third-party agent tools aren't built or operated by AutoCreator, and a capable agent can make large changes quickly. Use narrow keys, keep destructive scopes off unless needed, and review what your agent does — the activity log makes that easy.
Step by step
- In your admin, go to Integrations → API and create a key with only the scopes your agent needs (start with read-only).
- Set your environment values: AUTOCREATOR_API_KEY (your ac_ key), AUTOCREATOR_TENANT (your platform's name), and AUTOCREATOR_BASE_URL (your site's address).
- Point your generator (for example CLI Printing Press) at https://your-domain.com/openapi.json and the agent manifest at /.well-known/autocreator-tools.json.
- Follow the generator's instructions to produce the CLI, skill, or MCP server, then connect it to your agent.
- Test with a harmless read command, review the result in the activity log, then widen scopes as needed.
Good to know
- Rotate agent keys regularly and give each agent its own key so you can cut one off without breaking the others.
- The full walkthrough lives at autocreator.ai/developers/printing-press.
Related articles
Machine-readable specs: OpenAPI, agent manifest, and tool catalog
Three public, always-current endpoints describe the entire API for machines: an OpenAPI 3.1 spec, a rich agent manifest with safety flags, and a plain tool catalog. Discovery is open; execution still needs your key.
Help AI assistants discover your site with llms.txt
Your site automatically publishes llms.txt and llms-full.txt — a concise, AI-friendly map of your public pages, programs, collections, and blog articles — so AI assistants can find and reference your content. No setup needed.