APIs, tokens & MCP

Everything on InfoEmu is an API. This page is the reference for the credentials you use and the API families available. For the safety model and a ready-to-paste agent brief, see Run InfoEmu with AI agents.

Credential types

Credential	Looks like	Used for	Where to get it
Deploy token	dpl_<id>.<secret>	Publishing to one static/docs site	Console → your site → deploy tokens (shown once)
Forum API token	per-user token	The community REST API as a specific member	Your forum account (Pro and above)
CMS / platform API key	blu_sk_...	The content (CMS) and help-desk APIs, with scopes	Your forum/site admin, as a scoped key
Purchase API key	pk_...	The machine-facing purchase/workspace API	Purchase API registration

Tokens are shown once and stored only as a hash — save them immediately and revoke/rotate from the console when needed. A deploy token works for exactly one site.

API-key scopes

Platform API keys carry scopes that bound what they can do, e.g. cms-read, cms-write, and admin (for reading global settings). Give each integration the narrowest scope it needs.

Deploy API

Base: https://portal.infoemu.com/api/deploy/{instance_id} · Auth: Authorization: Bearer <deploy token>

Call	Purpose
POST /api/deploy/{id}	Upload a built site (multipart archive, tar.gz) → new release
POST /api/deploy/{id}/source	Upload raw content → sandboxed build → new release
GET /api/deploy/{id}/builds	Build status + logs
GET /api/deploy/{id}/releases	Releases, preview hostnames, stage + live pointers
POST /api/deploy/{id}/promote	Make a release production ({"release": "<id>"})
PUT / DELETE /api/deploy/{id}/stage	Point / clear the stage-- alias
POST /api/deploy/{id}/rollback	Revert production to the previous release
PUT /api/deploy/{id}/github	Connect a GitHub repo (push-to-build)

Upload limits: 200 MiB compressed, 512 MiB uncompressed, 50,000 files; archives must contain plain files at the root (no symlinks, absolute paths, or ..). Full guide: Deploy a static or docs site and Build from Markdown or GitHub.

Community (forum) API

Base: https://your-forum.infoemu.com/api/forum/v1 · Auth: the Authentication-Token header, or anonymous read when the forum enables public read.

Read forums, topics, and threaded posts; create topics and replies. Included on Pro and above. Anonymous public read (for embeds) is a per-forum opt-in. The embeddable React comments component (@infoemu/react) is built on this API.

Content (CMS) API

Base: https://your-site.infoemu.com/api/cms/v1 · Auth: Authorization: Bearer blu_sk_... (scoped) or an admin session.

• Content types — GET /content-types, GET /content-types/{slug}. The built-in types are articles, topics, posts, forums, categories.
• Entries — GET/POST /entries/{type}, GET/PUT/DELETE /entries/{type}/{id-or-slug} (scopes cms-read / cms-write).
• Globals — GET /globals/{slug} (read forum settings groups; admin scope).
• AI drafting — POST /ai-content/generate drafts content with your own Anthropic key. Off by default.

This is the API the docs starter’s CMS pull uses. Included on Pro and above.

Help-desk API

Base: https://your-site.infoemu.com/api/helpdesk/v1 · Auth: scoped API key or session.

Tickets and replies, categories, agents (assignment + workload), and reports (tickets, agents, categories, SLA, trends). An inbound-email endpoint turns mail into tickets when the email channel is configured (Connect a support inbox), and POST /api/helpdesk/v1/tickets/{id}/draft-reply produces an AI draft for a human to send. Included on Pro (help desk) and Business (shared inbox + AI).

Waitlist API

Forums expose an endpoint to add an email to a named waitlist from an external landing page or marketing tool, keyed by a service_key you choose. Consult your instance’s live API reference (below) for the exact path and payload. See Collect sign-ups with a waitlist.

The MCP server

@infoemu/mcp gives MCP-capable agents (Claude Code, Claude Desktop) typed tools across deploy, forum, content, and help desk — with the safety model built in: destructive tools (promote, rollback, production deploys, GitHub config) require an explicit confirm flag. Setup and the full tool list are in Run InfoEmu with AI agents.

Machine-readable entry points

• https://infoemu.com/llms.txt — a plain-text map of the platform for agents.
• Each tool serves its own OpenAPI description for its REST API — the authoritative, always-current endpoint reference for your instance.