# AffiliateLauncher

AffiliateLauncher (by CNR Consulting) is affiliate marketing software for brands and merchants who run partner programs. Manage affiliates, track attributed sales, calculate commissions, and pay partners.

Company site: https://cnrcode.com
Product home: /
Sign in: /user/login
Register: /user/email-verification
Reset password: /user/forgot-password
Human company signup (no Shopify): /pub/onboarding
Sitemap: https://directsales.software/sitemap.xml

## Capabilities

- Affiliate roster, tracking links, and listings
- Real-time commission plans (percentage and product rules)
- Sales reports and commission ledger
- Payouts: mark as paid and PayPal mass-payment file export
- 1099 prep export (payee totals for tax records; does not file taxes)
- Storefront affiliate lookup widget
- Shopify store connection (optional): order sync and tracking-link / storefront attribution
- WooCommerce / WordPress plugin: https://wordpress.org/plugins/affiliatelauncher/ (create a company here, then open WooCommerce → AffiliateLauncher in WordPress to connect)
- Non-store / custom: Public REST API sales writes + MCP automation after paid SaaS plan
- Plus: events and campaigns, affiliate onboarding/enrollment, REST API and MCP automation

## Contact

- Sales: sales@directsales.software
- Support: affiliatelauncher@directsales.software
- Other platforms: email sales@directsales.software to discuss options

## Zero-human signup (agents, no Shopify, no browser)

When Stripe SaaS billing is enabled on this deployment:

1. Create company + owner + API key (unauthenticated):
   POST /BillingSaas/CreateTenant
   Content-Type: application/json
   { "email": "agent@example.com", "password": "…", "clientName": "Acme Co", "planId": "core" }
   → { clientId, apiKey, siteId, planId, checkoutUrl?, actions[] }

2. Pay without a human (Machine Payments / MPP), when configured:
   POST /BillingSaas/MachinePay
   Body: { "clientId": <id>, "planId": "core" }
   → HTTP 402 + Payment challenge if no Shared Payment Token yet
   Retry with Authorization: Payment <SPT>
   → plan active (Core → Plus entitlements; Network → MLM when enabled)

3. Automate with the returned API key:
   Authorization: Bearer <apiKey>
   REST: /api/v1
   MCP: /mcp (Streamable HTTP)

Human Checkout alternative: open checkoutUrl from CreateTenant, or POST /BillingSaas/Checkout with a user JWT after login.
Shopify-installed companies must not use Stripe SaaS / MachinePay (use Shopify billing).
Webhook (SaaS, not Connect): POST /BillingSaas/Webhook

## Automation (Plus / MLM tiers)

Machine-to-machine access uses a company API key as Bearer token (not a user JWT).
Obtain or rotate under Settings → Company Config → API & integrations (or from CreateTenant).
Starter / unpaid SaaS: no API or MCP access (403 / 402).

| Surface | URL |
| ------- | --- |
| REST API | /api/v1 |
| MCP (Streamable HTTP) | /mcp |
| OpenAPI 3.1 (canonical REST contract) | GET /api/v1/openapi.json |
| Swagger UI + integrator guide | GET /api/v1/docs |
| API index (plain text) | GET /api/v1/llms.txt |

Auth header: Authorization: Bearer YOUR_API_KEY

REST is the canonical contract for data operations (31 endpoints). MCP is supplementary:
get_company_context, find_distributor, list_distributors, get_sale, get_commission_overview,
get_distributor_earnings, explain_workflow, search_help, get_help_topic. Same API key for both.

Recommended: fetch GET /api/v1/openapi.json for full schemas and operationIds.

## Service

- Health check: GET /health (includes links to API documentation and MCP)
- Example MCP client config: docs/mcp-cursor-example.json (in repo)