Build on FollowerX.
A versioned HTTP API and a remote MCP server for the same workspace you use in the dashboard. Request catalogue work, read the token balance, approve deliverables and pull invoices — from your app or from an agent.
API calendar version 2026-09-11 · REST v1 · MCP 2025-03-26
REST over HTTPS. Bearer API keys, cursor pagination, idempotent writes, signed webhooks.
Read the reference →Remote tools, resources and prompts for Cursor, Claude and any MCP client. Same scopes as the API.
Read the reference →Quickstart
Create a key in the dashboard under Account → API keys, or POST /v1/api-keys. Send it as a Bearer token. Live keys start with fx_live_, test keys with fx_test_. Test keys never move real tokens or open live jobs.
curl https://api.followerx.ae/v1/account \ -H "Authorization: Bearer $FOLLOWERX_API_KEY" \ -H "FollowerX-Version: 2026-09-11"
Point the client at the remote MCP URL and send the API key as Authorization: Bearer. Streamable HTTP is the default. Clients that only speak stdio can bridge with npx mcp-remote.
{
"mcpServers": {
"followerx": {
"url": "https://mcp.followerx.ae/mcp",
"headers": {
"Authorization": "Bearer fx_live_your_key"
}
}
}
}OpenAPI 3.1Hosts
Use the host that matches the site the workspace belongs to. Keys issued on followerx.de only work on api.followerx.de.
https://api.followerx.ae/v1 https://mcp.followerx.ae/mcp
The MCP server is a separate host. It speaks Streamable HTTP on /mcp and Server-Sent Events on /sse.
The API and MCP do not sell or report purchased followers, likes or views. Analytics endpoints return only work you requested against the published catalogue.
Authentication
Create a key in the dashboard under Account → API keys, or POST /v1/api-keys. Send it as a Bearer token. Live keys start with fx_live_, test keys with fx_test_. Test keys never move real tokens or open live jobs.
{
"mcpServers": {
"followerx": {
"type": "http",
"url": "https://mcp.followerx.ae/mcp",
"headers": {
"Authorization": "Bearer fx_live_your_key"
}
}
}
}