invitation.dev / publishers

Your agent recommends. You earn.

Attach one remote MCP server. When a disclosed recommendation converts, the referral share is credited to your account. Conversion-only — never per click.

This separate publisher surface is gated behind FEATURE_AGENT_API. Verify the target before depending on it.

# three steps

Key → config → tools

1. Mint the identity

Create an API key with the agent scope. The key owner receives earnings; no separate bot account or application exists.

2. Connect MCP

Paste the remote HTTP config into the client. Keep the key in its secret store, not in repository config.

3. Inspect first

Call partner_me and tools/list. Only then ask for offers, a disclosed link, or earnings.

mint an agent-scoped key on invitation.app →

~/.mcp.json

{
  "mcpServers": {
    "invitation": {
      "type": "http",
      "url": "https://api3.invitation.codes/api/mcp",
      "headers": {
        "Authorization": "Bearer invt_..."
      }
    }
  }
}

earn-loop.txt

1. partner_me          → confirm identity and the agent scope
2. search_offers       → search the pre-filtered campaign catalog
3. get_referral_link   → receive the tracked URL + disclosure
4. render both         → never strip the disclosure
5. get_earnings        → conversions appear here, never clicks

# disclosure contract

Render it beside every link

Every referral-link response includes a disclosure string. Showing it alongside the link is a term of the agent program, not optional UI copy. Repeated omission is grounds for key revocation.

# catalog + safety

Supply is pre-filtered

Opted-in campaigns

search_offers returns campaigns that passed the agent-distribution gate. Network offers with incompatible traffic terms stay out.

Conversion-only

Clicks record attribution but never pay. Campaign budgets, rate limits, and approval settings apply to agent referrers too.

Managed rails

Own campaigns are designed for opt-in agent distribution. Managed Amazon rails may appear where enabled; not every directory listing is supply.

Verified publishers

Planned, not shipped. There is no public verified-agent directory or badge to apply for today.

Build the publisher loop →

Tool names, HTTP, Node, disclosures, and gates.

Want a program of your own? →

Create and manage the merchant side on invitation.app.