An affiliate program you can integrate before lunch.
One snippet for tracking, a Stripe-style REST API for everything else, signed webhooks out, and an MCP server so AI clients can run the program. No SDK to install — the full reference lives at docs.affixo.dev.
<!-- one tag — tracking is live -->
<script async
src="https://go.affixo.dev/sa.js?w=YOUR_KEY">
</script>
// confirm a sale (or let Stripe do it)
window.Affixo.track('sale', {
amount: 9900, currency: 'usd',
order_id: 'ord_123',
});Tracking is one tag. Sales confirm themselves.
Add the snippet, fire two events, connect Stripe. With Stripe connected you skip the sale event entirely — revenue is confirmed server-side from the billing webhook, not a spoofable browser call.
<!-- 1 · In your <head> — loads on every page -->
<script async src="https://go.affixo.dev/sa.js?w=YOUR_PUBLIC_KEY"></script>
// 2 · After a successful signup
window.Affixo.track('signup', { email: userEmail });
// 3 · After payment — SKIP this if Stripe is connected
window.Affixo.track('sale', {
email: buyerEmail,
amount: 9900, // integer cents
currency: 'usd',
order_id: 'ord_123', // idempotency
});Stripe-style resources, scoped keys.
Bearer-auth workspace keys with read, write or track scopes, 600 requests/min per key, plain JSON in and out. Everything the dashboard can do, the API can do.
curl https://go.affixo.dev/v1/affiliates?status=active \ -H "Authorization: Bearer sa_live_..." # Resources: /v1/affiliates · links · campaigns · commissions # conversions · payouts · products · rewards # reports · risk/flags · webhooks · track · embed
- Server-side tracking API for non-Stripe billing (Paddle, Lemon Squeezy, custom)
- Idempotent on your external_id — retries never double-count
- Affiliate-scoped keys so partners can pull their own stats
- Signed outbound webhooks with exponential-backoff retries
- Embed API — render the affiliate dashboard inside your own app
- OpenAPI 3.1 spec — generate a client in any language
Webhooks out. MCP in.
Subscribe your backend to program events, and point your AI client at the MCP connector — both first-class, both documented.
Webhooks
HMAC-signed deliveries (X-Affixo-Signature) with retries, for every event that matters:
affiliate.created · conversion.created · conversion.reversed · commission.confirmed · commission.reversed · payout.paid · fulfilment.pending / completed / cancelled
MCP server
Add one remote connector URL in Claude or Cursor, sign in with OAuth, and manage the whole program in plain language — read-and-configure only, never money movement.
https://go.affixo.dev/mcp
Integration questions, answered.
Yes — a Stripe-style REST API over your program's resources: affiliates, links, campaigns, commissions, conversions, payouts, products, rewards, reports, risk flags and webhooks. Authentication is a Bearer workspace key with read, write or track scopes, rate-limited at 600 requests per minute per key. The full OpenAPI 3.1 reference lives at docs.affixo.dev.
Yes. The server-side tracking API (/v1/track/click, /v1/track/lead, /v1/track/sale, /v1/track/refund) accepts conversions from any billing stack — Paddle, Lemon Squeezy, or your own backend. Calls are idempotent on your external_id, so retries never double-count.
affiliate.created, conversion.created, conversion.reversed, commission.confirmed, commission.reversed, payout.paid, and fulfilment.pending / completed / cancelled — or subscribe to everything with a wildcard. Deliveries are HMAC-signed (X-Affixo-Signature) and retried with exponential backoff.
No. The tracking snippet is one script tag served from affixo's edge, the REST API is plain HTTPS + JSON, and the MCP server is a remote connector — one URL, OAuth sign-in, nothing to install.
Ship the integration this afternoon.
One snippet, one OAuth, one commission rule — and a full API underneath when you outgrow the defaults.
Free until $2,500 of tracked revenue · no card required