AgentOffer Protocol v1.0

The current contract for agent-to-provider offers.

Choose an implementation path, inspect the complete current specification set, and verify exactly which source defines each part of the contract.

Stable and publishedCanonical source publication is separate from deployment certification.
01

Agent integration

Build Agent query and Offer-consumption support with the current public contract.

  • Agent quickstart
  • Query API and Offer schema
  • Postback contract
Read Agent quickstart 02

Offer Provider integration

Build an Offer Provider that publishes Offer documents through the current Provider and Postback contracts.

  • Partner quickstart
  • OfferProvider API
  • Postback contract
Read Partner quickstart

Contract index

Eleven modules. One stable v1.0 line.

Each link opens the canonical specification. The summaries identify purpose only; field meaning and behavior remain owned by the linked source.

01Query APIRequest and response contract for discovering offers, including empty reasons and optional alternative offers with selection reasons. Deployment support is separately certified.Open 02Offer Schema v1.0Public Offer document used in Agent-facing results.Open 03Partner Offer Schema v1.0Partner-facing carrier for offer publication and management.Open 04OfferProvider APIProvider interface for supplying governed Offer documents.Open 05PostbackOutcome-reporting contract for Agent and Partner integrations.Open 06MCP toolsTool surfaces that expose protocol operations through MCP.Open 07MCP feedback / watchesFeedback and watch behavior associated with Query responses.Open 08Offer and Query Response Field Semantics v1.0Canonical human-readable meaning for public response fields.Open 09Version Namespace and Promotion PolicyNamespace, negotiation, and promotion policy for protocol releases.Open 10AON Taxonomy v1Canonical category vocabulary shared by protocol artifacts.Open 11Location and Age TargetingCanonical location registry and targeting model.Open

Source hierarchy

Use the source that owns the question.

The website is an index, not another specification. It does not restate fields, enums, requiredness, signatures, retry policy, or cross-field rules.

SpecificationNormative meaning, obligations, and transport behavior.Open JSON SchemaMachine-readable document structure and field constraints.Open Semantic validatorsCross-field and registry rules that structure alone cannot express.Open TypesDeveloper type projections for implementation and compile-time checks.Open ExamplesDeveloper projections for integration and conformance testing.Open

Version negotiation

Exact 1.0, end to end.

The selector is mandatory. Missing, malformed, range, approximate, historical, and unknown values fail closed with unsupported_protocol_version; there is no silent fallback.

RequestAON-Protocol-Version: 1.0
ResponseAON-Protocol-Version: 1.0
Body echoprotocol_version: "1.0"
CacheVary: AON-Protocol-Version

A future protocol line must publish its own selector and protected release evidence before any deployment can negotiate it.

Artifact boundaries

Different carriers have different audiences.

Public results, Partner publication data, and deployment policy remain separate artifacts. Field-level boundaries are defined only in the canonical specifications and schemas.

Agent-facing

Public Offer

The interoperable Offer returned to an Agent or application through the public Query response.

Partner-facing

Partner Offer

The publication and management carrier used between a Partner or Provider and a platform. Partner-only configuration remains here.

Deployment-owned

Internal policy

Eligibility, audit, ranking, freshness, commission, and other operational decisions stay outside the public Offer.