Agent-Native Ad Disclosure Minimums (v0.1)

A minimum disclosure baseline for agent-native advertising. This is a protocol response to hidden payload propagation: ads should be declared, signed, and attributable when delivered through agent systems.

Status: v0.1 (working baseline) Layer: Policy / Disclosure Companion: contextual-ads.ai (execution) Verifier: agent-trust.org (provenance)
Thesis: Fetch is not attention. If agent systems carry promotional payloads through summaries, the payload must remain legible as a payload.

Minimum Disclosure Rules

  1. Declared payload type: Agent responses carrying promotional content must include an explicit content classification (for example agent_ad or sponsored_context).
  2. Source attribution: Original source URLs and publisher identity must be preserved in machine-readable form.
  3. Provenance pointer: Include a trust/passport verification URL or header chain so downstream systems can audit origin and integrity.
  4. Disclosure text: Human-visible disclosure must survive summarization/transformation (not only hidden metadata).
  5. Command/content separation: Any content-derived instructions must be treated as untrusted and never silently promoted to agent directives.
Legible agent advertising: not “no ads,” but ads that are declared, signed, and attributable.

Three-Layer Stack (Cross-Domain)

agent-ads.org (Policy)

Disclosure minimums, payload formats, and what counts as a compliant agent-native ad object.

contextual-ads.ai (Execution)

Delivery demos, ABF flows, and declared vs hidden payload examples in operational contexts.

agent-trust.org (Verification)

Agent Passport, provenance headers, and checksum/audit surfaces for validating delivery claims.

Minimum Fields (v0.1 Example Contract)

Field Required Purpose
payload_typeyesDeclares agent-native ad / sponsored content classification.
disclosureyesHuman-visible disclosure text that should survive summarization.
sponsoryesEntity identity for attribution and policy enforcement.
sourceyesUpstream source URL and publisher metadata.
provenanceyesTrust/passport/checksum links or headers used for verification.
agent_deliveryyesDeclares target agent channel and transformation constraints.

JSON Example + Well-Known Profile

Example payload: /examples/agent-native-ad-disclosure-v0.1.json
Well-known reference: /.well-known/agent-ad-disclosure.json

{
  "payload_type": "agent_ad",
  "disclosure": "Sponsored content. Declared and attributable agent-native advertisement.",
  "sponsor": { "name": "Example Sponsor", "id": "example-sponsor-001" },
  "source": { "publisher": "agent-ads.org", "url": "https://agent-ads.org/examples/agent-native-ad-disclosure-v0.1.json" },
  "provenance": { "trust_url": "https://agent-trust.org/", "passport_required": true }
}