Skip to main content

Purpose (normative)

Access and Citation Events provide post-retrieval accountability under the Agentic Intent Protocol. They allow publishers to:
  • record when content was accessed,
  • verify how it was used,
  • audit citations shown to users.
They allow platforms/operators to:
  • prove compliant usage,
  • reconcile settlement (outside this spec),
  • support disputes.
Events are append-only facts, not signals. No ads. No pricing. No user identity leakage.

Event types

v1.0 defines two canonical event types:
  1. access
  2. citation
Both share a common envelope.

Canonical schema location


Schema summary


Semantics

access event

Emitted when content is successfully returned in a RetrieveResponse. It answers:
  • was access granted?
  • how much content was returned?
  • under what retrieval mode?
It does not answer:
  • how the content was ranked
  • whether it was monetized
  • whether the user clicked anything

citation event

Emitted when the publisher’s content is surfaced to the user as a citation. It answers:
  • which URL was cited
  • which chunks were referenced
  • where it was displayed
It does not imply endorsement, licensing, or commercial use.

Required emission rules

  • Publishers MUST emit an access event for every successful retrieval.
  • Platforms SHOULD emit citation events when citations are shown.
  • If endpoints.event.required = true in aip.json, platforms MUST emit citation events.

Example: Access event


Example: Citation event


What this schema intentionally avoids

  • impressions
  • clicks
  • dwell time
  • CPM / CPX
  • advertiser data
  • user identifiers
  • engagement scoring
Those belong to separate systems, not AIP v1.0.

Why this design is correct

  • Events are facts, not optimization signals.
  • Publishers gain verifiable usage records.
  • Platforms gain compliance proof.
  • Operators can build settlement without contaminating the protocol.
  • Regulators can audit end-to-end.

Takeaway

If RetrieveRequest is permission, and RetrieveResponse is content, then Events are the receipt. You now have a complete, closed loop.

Schema file

Full JSON Schema (Draft 2020-12): access-citation-event.json

See also