Operate Ambassly from an AI Agent

An AI agent can operate Ambassly today through the live MCP server at /api/mcp, using scoped company or affiliate API keys. For Claude Code, Claude Desktop, and Cursor setup, see the MCP server guide. Agents can also assist operators through the authenticated dashboard and the public install docs.

What works today

Machine-to-machine (MCP) — connect an agent with a scoped API key:

• Company keys: list programs, program stats, pending commissions, approve/reject commissions, invite affiliates, prepare payout batches.
• Affiliate keys: creator stats, links, and per-content link creation.
• Full Claude / Cursor config and tool list: docs/mcp.

Dashboard-assisted workflows — agents can also:

• Read the install docs and produce merchant-specific implementation steps.
• Help a merchant add the tracking snippet to a site or app.
• Prepare Stripe Checkout code that passes client_reference_id and metadata.ambassly.
• Walk through the Stripe webhook setup checklist.
• Explain commission states, hold periods, clawbacks, and payout export status from the dashboard.
• Draft affiliate invite emails and per-content link labels for review before sending.

The operator should still verify any payment, payout, webhook, or ledger action inside Ambassly and Stripe. Ambassly is a money product, so agent-assisted operation should be observable and reversible wherever possible.

Dashboard operations

The dashboard remains a primary control surface. A signed-in operator can create a program, invite affiliates, view attributed revenue, review commission states, export payout batches, and mark payouts paid. Mint and revoke MCP API keys from Dashboard or Portal settings.

For an agent workflow, treat the ledger and dashboard as the source of truth for money movements. The agent should not claim a payout, clawback, or approval happened unless the product shows it.

API and documentation surface

The current public integration surface is documented in these guides:

• MCP server — Claude Code, Claude Desktop, and Cursor config with scoped API keys.
• Install the Ambassly tracking snippet.
• Pass Ambassly referrals into Stripe Checkout.
• Set up the Stripe webhook.
• Understand Ambassly attribution rules.

These docs are enough for an agent to generate implementation instructions, connect via MCP, and produce code patches for a merchant app. Authenticated product permissions still apply.