Your agent decides what to promote.
We handle the networks.
Connect your own Awin, Impact, CJ, Rakuten and Amazon accounts to Claude, ChatGPT or any AI assistant. It finds programs, builds your tracked links, and shows you exactly which link earned what — all from a normal chat.
Set up in about two minutes
In the Claude desktop app or claude.ai — no terminal, no API key.
- 1Open Settings, then Connectors.
- 2Choose "Add custom connector".
- 3Name it affiliateos and paste the URL below.
- 4Click Connect and sign in when the popup appears. That is it.
Connector URL
https://api.affiliateos.dev/mcpCustom connectors are available on Claude’s paid plans.
Nothing to install and no keys to paste — signing in through the popup is the whole setup.
Five networks · one schema · your own accounts
Bring your own credentials. Programs, links, transactions and commissions from every account land in one schema, and we never sit in the commission flow.
Prerequisites
What you’ll need
before you start.
AffiliateOS runs on your own network accounts. Here’s exactly what that means, including the part that isn’t instant.
A publisher account with at least one network
You sign up with Awin, Impact, CJ, Rakuten or Amazon directly, under your own name and your own terms. We do not resell or broker access to any of them, and we cannot get you approved by one.
If you do not have an account with any network yet, AffiliateOS is not the right starting point. Apply to a network first, then come back. See what each network covers.
API credentials from that network’s dashboard
Each network issues its own. You fetch them from that network’s dashboard and enter them once. Nothing is shared between networks, and you can connect one and add the rest later.
| Network | What you’ll need | Where to get it |
|---|---|---|
| Awin | API Token | Awin UI, in the user menu at the top right under API Credentials, or go straight to https://ui.awin.com/awin-api |
| Publisher ID | The numeric ID for your Awin publisher account, shown in the dashboard URL | |
| Impact | Account SID | impact.com, under Settings, Technical, API |
| Auth Token | impact.com, under Settings, Technical, API | |
| CJ (Commission Junction) | Personal Access Token | developers.cj.com, under Authentication, Personal Access Tokens |
| Company ID (CID) | Shown in the CJ Account menu | |
| Website ID (PID) | CJ, under Account and then Websites; the PID for the site you promote from | |
| Rakuten Advertising | Client ID | Rakuten Advertising Developer Portal, under Application |
| Client Secret | Rakuten Advertising Developer Portal, under Application | |
| Site ID (SID) | Your Rakuten publisher site ID | |
| Amazon Associates | Creators API Credential ID | Associates Central, under Tools, Creators API (primary account owner only) |
| Creators API Credential Secret | Shown once when creating the Creators API application | |
| Partner Tag (Store ID) | For example yourtag-20, from Associates Central | |
| Marketplace | For example www.amazon.com | |
| Credential Version | Shown in Associates Central when creating the app; usually 3 |
- Two things catch people out on Amazon: the Creators API is available to the primary account owner only, and the credential secret is shown once, when you create it. Copy it then.
- Amazon supports product search and links only. It has no earnings API, so earnings by tag does not cover Amazon.
Approval for at least one program
This is the slow part, and the queue is the network’s, not ours. Networks approve publishers per advertiser, not once globally, so connecting an account does not join you to the programs in it.
Until an advertiser approves you, search_programs returns that program as not_joined and create_link cannot mint against it. Approval usually takes days, sometimes longer, and it varies by advertiser. We have no say in it, so we will not quote you a number.
Everything except approval takes a few minutes. The free tier needs no card, connecting Claude is one command, and no keys are pasted into your assistant.
Connect your networksThe closed loop
Agents don’t just create links.
They learn what earns.
Discover search_programs
Your agent searches every connected network at once. Commission rates, cookie windows and approval status come back in one normalized response, sized for a context window.
Mint create_link
It mints a tracked deep link on your own account, stamped with an attribution tag for the exact campaign, placement or conversation that produced it.
Learn get_earnings_summary
Conversions flow back tagged. The agent reads earnings by tag, sees what actually converts, and reallocates. That's the loop. Most tooling stops at step two.
Why
Existing tooling is human-shaped.
Yours shouldn’t be.
Agent-native, not agent-compatible
A first-class MCP server you add from your assistant’s connector settings — paste a URL, sign in, done. No keys to paste, and tools shaped for agent reasoning with responses budgeted to fit a context window.
BYOC means you keep the money
Your network accounts, your merchant relationships, your commissions. We never sit in the payment flow, never rewrite your links through our accounts, never take a percentage.
The loop closes
Every link carries an attribution tag and every conversion syncs back tagged. Earnings-by-tag is the primary abstraction, so agents can measure and reallocate instead of just publishing.
Developers
Infrastructure, not another dashboard.
21 MCP tools
search_programs, create_link, get_earnings_summary, list_transactions and 12 more. The whole surface, tool by tool.
REST parity
Everything MCP does, over REST with API keys. n8n, cron jobs and custom stacks get the exact same surface.
Attribution tags
One sub-ID convention across five networks. Tag per campaign, placement or conversation; read earnings grouped by tag.
Webhooks
Diff-based events on every sync: commission.created, approved, reversed, paid. Delivered with retries.
Sealed credential vault
Network credentials sealed with libsodium before storage, decrypted only in worker memory at call time. Never logged.
ToS-clean by design
Official APIs, your own accounts, documented sub-ID usage per network. You stay the accountable publisher.
claude mcp add --transport http affiliateos https://api.affiliateos.dev/mcpFor the terminal. Not a terminal person? Add the same URL as a custom connector in your assistant's settings — see the connect guide. Either way an OAuth popup handles auth, so no API keys end up in agent config.
The field
Built for a human at a dashboard?
We’re built for an agent in a loop.
Multi-network dashboards
Strackr · Wecantrack · Affilimate
Unify the data for a human at a screen. No agent surface, APIs gated behind custom plans, attribution an afterthought.
Auto-monetizers
Sovrn · Skimlinks
Rewrite your links through their accounts. They own the merchant relationship, keep the data, and take a cut of every commission.
AffiliateOS
BYOC · MCP + REST
Your accounts, agent-native surface, attribution loop as the core abstraction. Keep 100% of commissions and all of your data.
Pricing
Priced like infrastructure.
Never a cut of your commissions.
Auto-monetizers are free because they take a percentage of everything you earn. We charge for the rails and stay out of the money: your accounts, your merchant relationships, 100% of every commission.
Free
The full surface with capped volume. Enough to close your first loop and prove it works.
- 2 connected network accounts
- 250 links per month
- All 21 MCP tools + full REST API
- 1 webhook endpoint
- Every earnings and attribution feature
Pro
For publishers running agents in production. Same surface, production volume.
- 25 connected network accounts, across all five networks
- 10,000 links per month
- All 21 MCP tools + full REST API
- 10 webhook endpoints
- Priority support
both tiers get the whole product · limits cap volume, not capability
FAQ
Straight answers
Do I need to know how to code?+
No, and you never need to open a terminal. Connecting is a settings screen in Claude or ChatGPT: add a custom connector, paste one URL, sign in through the popup. After that you talk to your assistant in plain English — "find me a running-shoe program I'm approved for and make me a link" — and it does the work. The command line and the API are there for people who want them, not because setup requires them.
Do you take a cut of commissions?+
No. Commissions flow from the networks to you exactly as they do today, because we're not in the payment path. Pricing is on infrastructure (networks connected, volume), never a percentage of earnings.
What do I need to get started?+
Existing affiliate network accounts. That's what BYOC means: you connect your assistant from its settings screen, then paste API credentials from each network dashboard once (there's a step-by-step guide per network). We can't get you accepted into networks or programs.
Which networks are supported?+
Awin, Impact, CJ and Rakuten with full program, link and transaction sync. Amazon Associates works for established accounts via the Creators API. Amazon requires roughly ten qualifying sales in the trailing 30 days for API access, and exposes product search and links but no earnings feed.
Is this compatible with network terms of service?+
That's the design goal: official APIs only, your own credentials, sub-ID usage documented per network, no cross-account pooling or link brokering. Standard affiliate disclosure rules (FTC and equivalents) still apply wherever your links get published, agent-placed or not.
What if I don’t use MCP?+
The entire surface has REST parity with API keys and webhooks. MCP is how agents connect; it is not a dependency. n8n workflows, cron jobs and custom code are first-class.
Stop reconciling five dashboards.
Start closing the loop.
free tier · no revenue share · your accounts stay yours