← ClaudeAtlas

sales-affiliatebaselisted

AffiliateBase platform help — Stripe-only affiliate software for SaaS with the deepest self-serve automation surface in the budget cohort: a public OpenAPI 3.1 spec, 51 REST endpoints on app.affiliatebase.io/api/v1, svix-signed webhooks, a hosted MCP server, and REST API on every tier including the free plan. Use when wiring attribution through Stripe Checkout, Payment Links, Buy Buttons or Pricing Tables, passing the generated referral ID rather than the ?via token as client_reference_id, verifying svix HMAC webhook signatures, connecting the MCP server to Claude or Cursor, driving payout runs and PayPal/Wise exports, or judging its revenue-capped pricing. Do NOT use for commission structures or program strategy (use /sales-affiliate-program), or for Tolt, Affonso, PromoteKit, Rekomi or Endorsely (use /sales-tolt, /sales-affonso, /sales-promotekit, /sales-rekomi, /sales-endorsely).
sales-skills/sales · ★ 96 · API & Backend · score 76
Install: claude install-skill sales-skills/sales
# AffiliateBase Platform Help AffiliateBase is affiliate-program software for **Stripe-billed SaaS**. Against the rest of the budget Stripe-native cohort its wedge is the automation surface: a complete **OpenAPI 3.1 contract anyone can download without an account**, 51 REST endpoints, svix-signed webhooks, and a hosted MCP server — with **REST API access on every tier, including the free one**. Two facts shape most real questions. **Stripe is not a preference, it is the boundary** — there is no `POST /commissions`, so revenue that does not settle through the connected Stripe account cannot be tracked at all. And **the value Stripe needs is the generated referral ID, not the `?via` token** — confusing the two is the integration bug that silently zeroes out attribution. ## Step 1 — Gather context If `references/learnings.md` exists, read it first. **Skip-ahead rule:** if the user's prompt already has enough context, go straight to Step 2. 1. **What are they trying to do?** Install tracking · fix attribution · build an API integration · handle webhooks · set up MCP · run payouts · pick a plan · migrate in or out 2. **Which checkout path?** Payment Link, Buy Button/Pricing Table, custom Checkout Session, or promo codes only — this decides whether they write any code at all. And **is money already moving?** A live program constrains what can change, and plan caps count *affiliate-attributed* revenue. ## Step 2 — Route or answer directly If the question is not actua