Script your traffic.
Or just ask for it.
Everything the dashboard does, Babylon Traffic also exposes as a versioned REST API and as a remote MCP server. Build campaigns from your own code, or hand the whole account to Claude, ChatGPT or any other MCP client and describe what you want in plain English.
Pick the one that fits the job
Both speak to the same account, the same quotas and the same campaigns. One credential type covers both, and revoking it kills both at once.
For your own code
A versioned JSON API under /api/v1, authenticated
with a bearer token you create yourself. Predictable envelope,
cursor-free pagination, filtering and sorting on every list.
For AI assistants
A remote MCP server at /mcp, added by URL alone.
The assistant discovers the tools itself, asks you to approve
the connection in the browser, and then works the account the
way you would.
Three front doors, one implementation
The API is not a wrapper bolted onto the app. The dashboard, the REST controllers and the MCP tools all call the same action classes, so a rule that holds in the browser holds identically over the wire.
Same ownership checks, same plan quotas, same abuse filter — whichever door you came through.
Three steps, and none of them is "find your API key"
Paste the URL
In Claude, ChatGPT or any MCP client, add a custom connector and give it the address below. There is no client ID, no secret and no API key to find first.
Approve it here
The client registers itself and sends you to a Babylon Traffic consent screen. Sign in, tick read only or read and write, and confirm. That is the whole handshake.
Revoke any time
The connection lands in your account as an ordinary API token. Delete it there and the assistant loses access immediately, mid-conversation.
https://www.babylontraffic.com/mcp
24 tools the assistant can reach for
Each one is scoped to your own account and checked against your plan before it runs. A read-only connection simply never sees the rest.
Projects
- list_projects
- get_project
- create_project
- update_project
- duplicate_project
- toggle_project_active
- delete_project
Campaigns
- list_campaigns
- get_campaign
- create_campaign
- update_campaign
- duplicate_campaign
- move_campaign
- toggle_campaign_active
- delete_campaign
Action trees
- get_campaign_actions
- add_campaign_action
- update_campaign_action
- replace_campaign_actions
- delete_campaign_action
Reporting
- get_traffic_stats
- list_runs
- get_run
- get_account
read and write, picked per token
Everything under /api/v1
Reads need the read scope, writes need write.
Lists accept ?per_page=, ?page=,
?q=, ?sort= and ?filter[field]=.
Your first campaign is one sentence away.
Sign in, create a token or connect an assistant, and you are talking to the same engine that runs every campaign in the dashboard.