Use PromoterAI anywhere

One tool registry, four front doors: the in-app agent, Claude (MCP), your terminal, and REST. Auth for everything outside the app = your API key — mint it in the agent (“create my API key”) or POST /api/keys.

Add to Claude (MCP)

PromoterAI speaks MCP over Streamable HTTP. In Claude, add a custom connector:

URL:    https://<your-promoterai-domain>/api/mcp
Auth:   Bearer pk_promoter_...   (your API key)

Claude gets the tools enabled for the authenticated workspace and API-key scopes, including research, audiences, monitoring, and outreach preparation.

CLI

export PROMOTER_API_KEY=pk_promoter_...
npx promoterai tools                       # list tools
npx promoterai run find_speakers '{"niche":"Marketing","min_followers":20000}'
npx promoterai run usage '{}'

REST

POST https://<domain>/api/v1/run
Authorization: Bearer pk_promoter_...
{ "tool": "enrich_person", "args": { "linkedin": "https://linkedin.com/in/..." } }

GET the same endpoint for the full tool registry with JSON schemas. Rate limits follow your plan tier.

API keys use least-privilege scopes. Operational dashboard data requires dashboard:read; a default platform:read key cannot read campaign, contact, sender, queue, or review details.

Async tools

find_team and build_audience start jobs — poll with check_team / check_audience_job every ~30–60s until done. The in-app agent does the polling for you.