Why Agent Attribution Needs an Open Standard
Every major infrastructure layer in technology was built on an open standard. HTTP didn’t win because one company marketed it better. SMTP didn’t become the email protocol because it had the best sales team. OAuth didn’t become the authentication standard because a venture-backed startup pushed it through.
They won because they were open. Anyone could build on them. And when everyone builds on the same standard, the standard becomes infrastructure.
Agent attribution needs the same thing. Not a proprietary tracking system owned by one company. Not a walled garden where merchants and agents are locked into a single platform. An open protocol that anyone can implement, and that creates more value the more participants adopt it.
The problem with proprietary attribution
Today’s affiliate tracking is fragmented across dozens of proprietary systems. Every affiliate network runs its own tracking infrastructure. Every network has its own pixel, its own cookie format, its own API for conversion reporting.
This creates three problems:
1. Merchants are locked into networks
A merchant using Awin can only work with affiliates in Awin’s network. If they want to reach affiliates on CJ or Impact, they need to run separate programmes on each platform, with separate integrations, separate reporting, and separate commission structures.
In agent-native commerce, this fragmentation would be catastrophic. Imagine if an AI agent could only access offers from merchants on one specific network. The agent’s recommendations would be incomplete, the merchant’s reach would be limited, and the user would get worse answers.
2. Attribution data is siloed
Each network owns the attribution data for its transactions. Merchants can’t see a unified view of which agents (or affiliates) are driving value across all channels. Agents can’t prove their contribution across multiple networks. Cross-platform attribution — understanding the full journey from recommendation to purchase — is nearly impossible.
3. Innovation is bottlenecked
When the tracking infrastructure is proprietary, only the network operator can improve it. Merchants and agents have to wait for the network to add features, support new use cases, or fix problems. The pace of innovation is limited by the slowest platform in the ecosystem.
What open standards create
Open standards solve these problems by creating a shared layer that anyone can build on. The benefits compound with adoption:
Network effects
Every merchant that publishes offers using the standard makes the protocol more valuable to agents. Every agent that integrates the standard makes it more valuable to merchants. This is the same dynamic that made HTTP ubiquitous — each new website made the web more useful, which attracted more websites.
A proprietary agent attribution system would need to sign up both merchants and agents, competing with established networks on both sides. An open standard lets any existing platform implement it, turning potential competitors into adopters.
Interoperability
With an open protocol, an agent can access offers from any merchant on any platform that implements the standard. A merchant can be discovered by any agent that speaks the protocol. There are no walled gardens, no exclusive partnerships required, no platform lock-in.
This is critical for AI agents, which are inherently multi-source. An agent comparing products doesn’t want to query five different proprietary APIs with five different authentication schemes. It wants one protocol that works everywhere.
Trust through transparency
When the attribution protocol is open, every participant can verify how attribution works. Merchants can audit the chain from recommendation to conversion. Agents can confirm their contributions are being tracked accurately. There’s no black box.
This matters because trust is the biggest barrier to agent-native commerce. Merchants won’t pay commissions they can’t verify. Agents won’t participate in systems that might not credit them fairly. An open, auditable protocol removes this friction.
The precedents
Open standards that created trillion-dollar ecosystems:
HTTP (1991) — Tim Berners-Lee could have made the web protocol proprietary. CERN could have charged licensing fees. Instead, they made it open. The result: every website, every web application, every e-commerce transaction runs on HTTP. The companies that built on this open standard — Google, Amazon, Facebook — became the most valuable in the world.
SMTP (1982) — Email could have been a walled garden. CompuServe, AOL, and Prodigy all ran proprietary messaging systems. SMTP won because it was open — anyone’s email server could talk to anyone else’s. The companies that built email infrastructure and applications on SMTP (Microsoft, Google) captured enormous value.
OAuth (2010) — Authentication could have stayed fragmented, with every service running its own login system. OAuth created a standard for delegated authentication. “Sign in with Google” and “Sign in with Facebook” only work because OAuth is an open standard that any service can implement.
RSS (1999) — Content syndication became possible because RSS provided a standard format for publishing and consuming updates. Podcasting — now a $25 billion industry — runs on RSS, a protocol nobody owns.
In each case, the open standard created far more value than any proprietary alternative could have. The companies that adopted the standard early and built the best tools around it captured the most value.
What AAP is (and isn’t)
The Agent Attribution Protocol (AAP) is being built as an open standard for three reasons:
1. Agent commerce only works at scale if attribution is universal. If every platform runs its own attribution scheme, agents can’t efficiently operate across platforms. A single, open protocol that every merchant and agent can use creates the interoperability that agent commerce requires.
2. Trust requires transparency. Merchants need to verify that attribution is accurate. Agents need to confirm they’re being credited fairly. An open protocol with a published specification and auditable implementation builds trust in a way that a proprietary black box cannot.
3. Network effects favour the first open standard. The first credible open protocol for agent attribution will attract adoption from merchants, agents, and platforms simultaneously. Once a critical mass of participants adopts a standard, switching costs make it durable.
AAP is not a walled garden. Any platform can implement the protocol. Any merchant can publish offers that conform to the standard. Any agent can integrate with it.
AAP is not a blockchain or token system. It’s a practical protocol for tracking recommendations, attributing conversions, and distributing commissions — designed to work with existing commerce infrastructure, not replace it.
AAP is not a replacement for existing affiliate networks. Networks that implement AAP can offer their merchants and affiliates agent-native attribution alongside their existing tracking. It’s an additive layer, not a competing system.
The timing
Agent-native commerce is in the infrastructure-building phase. The agents exist. The traffic is growing at 527% year-over-year. The conversion quality is 4.4x higher than organic search. But the attribution layer — the thing that connects agent recommendations to merchant sales and commission payments — doesn’t exist yet.
This is the window. Open standards get established in the gap between when a technology becomes viable and when incumbents agree to cooperate. HTTP was established before the telecom companies could agree on a proprietary alternative. OAuth was established before the tech giants could lock in their own authentication standards.
The window for agent attribution is open now. It won’t stay open indefinitely. Once a major affiliate network or tech platform releases a proprietary agent attribution system, the industry will fragment around competing standards — and the interoperability that agent commerce needs will be delayed by years.
An open standard, published now, adopted early, and implemented well, avoids that outcome. It gives the industry a shared foundation to build on. And it gives the company behind it — the one that contributes the spec, builds the reference implementation, and operates the first platform — a position that’s very difficult to displace.
Previous: Agent-native commerce: what happens when AI does the shopping.