The local server is free, open source and MIT licensed — free to use, read, fork, and contribute to, with no account and no cap. It always will be.
There is also an optional hosted tier for people who cannot install a server, or who need reports to run while their machine is off. It starts free — three reports a week, no card — then £34 or £99 a month. Hosted removes the install; it does not unlock anything the free local server cannot already do.
It runs on your machine with the logins you already have, and the networks see the same calls they'd get from your own dashboard. Today it's about reading and analysing your data.
Automation is on the roadmap and built around approvals — nothing acts without your sign-off, and only within rules you set.
No. The primary non-technical path is the Claude Desktop .mcpb, with no Node.js or terminal required. The complete setup path for every network uses the technical CLI track. See get started.
Claude Desktop, Claude Code, and Codex have shipped setup paths for the free local server. Claude Desktop .mcpb is the primary non-technical path. Cursor, VS Code, and generic local MCP clients are possible through stdio but do not yet have a tested first-party setup journey here.
ChatGPT cannot run the local server, so it needs the hosted connector, which is live: any client that can add a custom connector over OAuth can use it. We have not published a tested ChatGPT walkthrough yet, so expect to follow ChatGPT's own connector steps.
No. The standalone Electron/DMG setup app is a fixes-only compatibility fallback for existing macOS users. New non-technical Claude Desktop users should install the host-native .mcpb. The conversations happen in Claude Desktop, Claude Code, or Codex.
Dozens, on the publisher side, the brand side, or both — Awin, CJ, Impact, eBay, Rakuten, Skimlinks, Partnerize and many more. See the full networks list.
Every adapter is community-built and marked experimental until the network adopts it and verifies it against live credentials. If yours is missing, you can request it; if you run the network, you can adopt it.
On the local server, no. Your keys and affiliate data stay on your machine, apart from requests sent directly to the networks you configure. Optional anonymous usage telemetry is off by default and is sent only after you explicitly opt in.
On the hosted tier, yes, deliberately. You enter your network keys into an encrypted dashboard so reports can run without you. They are encrypted at rest, used only to serve your own requests, and your AI client never receives them. Full detail is on the privacy page and the security page.
In an encrypted vault on our infrastructure, never in Claude. Each user gets their own AES-256-GCM data key, and credentials are decrypted only in memory at the moment a call runs. Your AI client is issued a short-lived, scoped OAuth session instead, so there is no token to paste anywhere.
One limitation worth knowing: in the current release the master key is a Cloudflare Worker secret rather than an external KMS. We say so plainly on the security page rather than leaving you to find it.
A report is one 30-minute working session, not one question. Your first data request opens the window, and everything you ask inside those 30 minutes is included. The free plan gives you three a week on a rolling seven-day basis, with no card.
Because holding someone's API key is a heavier commitment than helping them use their own. Awin, CJ Affiliate, Impact and Rakuten Advertising are the four whose terms have been checked and whose adapters are mature enough to run unattended. Everything else stays local-only until the same is true of it — and the free local server covers all of them today.
Cancel any time from the billing portal in your dashboard. You drop back to the free plan rather than losing access. If you delete your account instead, the encrypted credentials, the key protecting them, the account record and the billing email all go with it — deletion is complete, not a soft flag. You can also revoke the API key in the network's own dashboard at any point, which cuts access regardless of anything on our side.
It started as one builder shipping the integration they wanted and giving it away — none of the networks had shipped one for either side. It's open source and community-maintained, and networks are invited to own their own adapter.