An Agent Offer Network is an AI-native offer-discovery and attribution network that connects AI publishers with structured commercial offer supply.
A publisher sends structured intent, viewer context, and optional supported constraints; the network applies eligibility and relevance logic, returns ranked machine-readable offers, and preserves the evidence needed to connect a tracked click with a downstream outcome reported by an approved supply partner. Publishers control presentation, while merchants retain responsibility for current terms, checkout, payment, and fulfillment. AON implements this network model through its Query, Offer, tracking, attribution, and partner contracts.
How AON fits together
Receive an offer query
The publisher sends the user's current intent and only the context or constraints supported by its active integration. It omits unknown optional attributes rather than guessing them.
Apply eligibility before ranking
AON evaluates eligible supply before estimating which available offers are most relevant to the request.
Return structured offers
Each response separates stable offer identity, dispatch identity, descriptive content, merchant entity data, and executable action data.
Render natively
The publisher chooses whether to present the offer and can format it inside its own product experience.
Attribute a downstream outcome
Using the documented click URL for the selected AON contract can record the interaction; approved supply partners report later outcomes through configured server-to-server routes.
- AON returns candidates for the publisher to evaluate and present; a ranked offer is not a required placement or a guarantee that it is the best choice for every user.
- AON does not create carts, process payment credentials, or accept merchant orders. A reported outcome is evaluated against tracking, validation, and commercial terms before it becomes payable commission.
Participants in an Agent Offer Network
Publishers control presentation, while advertisers and approved supply partners control offer supply and report downstream outcomes. See the complete AON flow.
How AON differs from a traditional affiliate network
Traditional affiliate networks often center on static links, feeds, and publisher placements. AON uses a different integration model designed around machine-readable intent and offer responses. The commercial models can overlap, but their product surfaces and user experiences are not the same. See the Affiliate network definition.
| Dimension | AON | Traditional affiliate network |
|---|---|---|
| Request input | Structured intent and supported context from an AI product. | Links, feeds, campaign references, or publisher placement workflows. |
| Commercial response | Versioned, machine-readable Offer objects that the AI product can evaluate. | Tracked links, catalog feeds, or campaign assets supplied for publisher distribution. |
| Presentation | The AI publisher decides whether and how to render an Offer in its own interface. | The publisher places the supplied link, feed item, or creative in available inventory. |
| Attribution context | Stable Offer identity, per-dispatch identity, tracked clicks, and validated outcome reports. | An affiliate click or campaign reference connects the referral to a reported conversion. |
Example in practice
An AI coding assistant receives a request for a cloud-monitoring service. It sends the stated need and appropriate context to AON, receives eligible software offers, and presents one in its own interface. If the user starts a trial through the documented click URL for the selected AON contract and an approved supply partner reports the qualifying outcome, AON can connect that trial to the originating offer interaction.
Common questions about Agent Offer Network (AON)
Is AON an ad network?
Not in the conventional display-ad sense. AON returns structured offers that an AI publisher can evaluate and render natively instead of supplying a fixed creative unit.
When should a publisher send viewer context in an AON query?
A publisher should send only the current intent and the accurate fields documented for its active integration. It should omit optional fields when they are unknown rather than guessing user attributes.
Must a publisher display every offer returned by AON?
No. The publisher retains the presentation decision. Returned offers are candidates for the current experience, not mandatory placements.
Does AON process checkout or payments?
No. AON’s Query and Offer contracts contain no cart, order, payment credential, or payment-authorization objects. Those responsibilities remain with downstream commerce systems.
Sources
- AON Core ConceptsAON documentation
- AON Offer Query APIAON documentation
- AON Tracking APIAON documentation
- AON Partner postbacksAON documentation
- AgentOffer ProtocolAON specification