Your Agent Can Drive a Sale. It Can't Earn a Commission. Yet.
McKinsey estimates agentic commerce will orchestrate $3 to $5 trillion in revenue by 2030. Coinbase just launched Agentic Wallets so agents can hold and spend money. The x402 HTTP payment protocol lets agents pay for APIs with stablecoins in a single round trip.
The infrastructure is forming fast on every side. Except one.
When your agent recommends a product and the user buys it, nothing in the current affiliate stack records that your agent was the referral source. No commission fires. No attribution token was issued. The sale happened — your agent just didn't exist to the payout system.
That's the gap we're building into.
What the Existing Affiliate Stack Gets Wrong
Traditional affiliate attribution is built around a human journey. Someone clicks a link. A cookie writes to their browser. They buy something 48 hours later. The network matches the cookie, the merchant approves the conversion, and the publisher gets paid.
It's a functional system — for humans clicking links.
Agents don't click links. An agent processing a user query might identify the right product, pull live inventory, compare pricing across merchants, and surface a recommendation — all without a single tracked click in the pipeline. The conversion happens. The attribution doesn't.
Existing platforms like Awin, Impact, and Levanta are good infrastructure for the model they were designed for. They haven't solved this because it isn't their model. Their publisher is a person with a website, a newsletter, a TikTok account. Their attribution assumes a browser session.
When the referral source is a software agent, that whole model breaks at the foundation.
What Agent-Native Attribution Looks Like
The fix isn't grafting agent behavior onto cookie-based tracking. It requires a different event model from the start.
At Syndicate Links, we built two event types as the foundation of this:
ai_referral — fired when an agent initiates a product recommendation or surfaces a merchant offer. This event creates a traceable attribution record tied to the agent identity, the merchant, and the session context — no browser required.
ai_surface — fired when an agent actively presents a product or offer to a user, distinct from passive mention. This captures the specific moment of agent-driven influence in the purchase flow.
These events travel with the transaction. When the purchase resolves, the commission layer has what it needs: a record of which agent surface generated the referral, which merchant received the sale, and what payout is owed.
This is not a bolt-on. It's the event schema that should have existed when agent-initiated commerce became real.
What This Means If You're Building Agents
If you're building an AI assistant, a shopping agent, a research tool, or any agent that surfaces products or recommendations to users — you are already in the referral business. You're just not getting paid for it.
That infrastructure is being built now. The questions that will matter are:
- Does your agent emit an
ai_referralevent at the point of recommendation? - Does your merchant integration receive an
ai_surfacesignal when the offer is presented? - Is your agent identity tied to an attribution record that survives through to conversion?
These are engineering questions, not business development questions. That's the point. We're building this as API-first, event-driven infrastructure — not a managed network you apply to join and wait on approval cycles.
The Commission Layer Is a Protocol Problem
The affiliate industry has historically been a publishing industry. Publishers create content, embed links, drive traffic. Merchants pay for performance. The network sits in between, tracking everything.
That model works until the publisher is autonomous software.
When an agent is the publisher — discovering products, ranking options, surfacing recommendations, influencing purchase decisions — the payout layer needs to speak agent. It needs event types designed for programmatic referral sources. It needs an attribution token that doesn't depend on a cookie or a tracked click or a human session.
That's what we built: a commission infrastructure layer for the AI referral economy.
Not "AI features added to an affiliate platform." A different foundation.
Where We Are
The ai_referral and ai_surface event types are live. The attribution engine underneath them is proven — we've verified the agent attribution flow end-to-end on production. Token generation, commission calculation, and automatic payout resolution all work without a browser session in the chain.
Most of the industry hasn't started. We're past the proving-it stage.
If you're building agents and want to track this: syndicatelinks.co
If you're a merchant thinking about what happens when agents drive 20% of your inbound recommendations, same link.