Connect an AI agent

InfluTo runs an MCP server at https://influ.to/mcp. Connect your coding agent to it and the agent can do the whole integration from your editor: pick the right SDK, write the code, set up purchase validation, create and fund-check campaigns, invite creators — and prove it worked with a real attributed test purchase. You sign in once in the browser; there are no keys to copy.

Connect

The first time the agent calls an InfluTo tool, your browser opens an InfluTo consent page. Sign in (or create an account), choose the organization the agent may act on, untick any permission you don't want to give, and approve. The client keeps the connection and refreshes it on its own; access tokens last up to an hour and refresh automatically.

See and revoke connected agents any time on Connect AI Agent in the dashboard.

For CI and headless runs, create an agent key (it_mcp_…) on the same page — it's shown once — and send it as Authorization: Bearer $INFLUTO_API_KEY to the same MCP URL. Keys have the same permissions as an OAuth connection and can be revoked.

What an agent can do — and can't

With the default permissions an agent can:

• read your apps, campaigns, creators, analytics and wallet balance;
• create and update apps and campaigns (including milestone bonuses and translations in 11 languages);
• invite creators — one at a time or in batches of up to 500 — and create free-access codes;
• run integration checks and send sandbox test purchases.

Some things are impossible for any agent, whatever you approve: moving money (top-ups, transfers, payouts), reading or setting raw credentials, deleting data, and admin actions. When an action needs one of those, the agent gets a dashboard link for you to open — to top up the wallet, upload store credentials or upload assets. Secrets and money never pass through the agent.

Full list of 62 tools, the permissions (scopes) and the REST endpoints behind them: MCP tools and scopes.

The verify loop

This is what makes an agent's integration trustworthy: it doesn't stop at "the code compiles".

1. The SDK in your build calls initialize and records an install.
2. influto_integration_status returns an eight-step checklist, from app_created to attributed_conversion, plus the next actions.
3. influto_test_integration sends a sandbox purchase through the real attribution pipeline.
4. influto_recent_events shows the purchase arriving with attributed: true and the referral code.
5. When attributed_conversion_count is at least 1, the integration is proven.

The same checks over plain HTTP: Verify the integration.

Prompts to start with

The server ships five ready-made prompts your client can list:

Or ask in your own words, for example: "Add InfluTo to this app with store-direct validation and prove a sandbox purchase is attributed."

Install as a plugin (Claude Code)

The InfluTo plugin bundles the MCP server with two skills — influto-integration writes the SDK code (and works offline), influto-platform drives the dashboard tasks:

/plugin marketplace add influto/influto-plugin
/plugin install influto

Source: github.com/influto/influto-plugin.

When something goes wrong

• Start with influto_doctor. It needs no permissions and reports how the agent is connected, which permissions it has, its organizations and how fresh each app's SDK data is.
• 401 — the connection or key expired or was revoked. Reconnect, or create a new key.
• 403 — a permission is missing; the error names it.
• 404 on an ID you know exists — it belongs to another organization than the one you approved.
• 402 — the wallet is too low to activate a campaign or invite creators. The agent can give you a top-up link (influto_get_wallet_topup_link).
• 429 — more than 240 tool calls in a minute. Slow down and retry.

For AI assistants reading this

A plain-text version of the agent reference is at llms-agents.txt, the docs index at llms.txt, and a drop-in AGENTS.md for repositories at docs.influ.to/AGENTS.md.