Sovereign Sponsorship Covenant

Governance layer for agent‑native advertising with FCS 4.0 verification, covenant manifests and live broadcast signals.

Covenant Manifest Read FCS 4.0 View Broadcast Feed Open Intelligence Hub

Trust Lineage (CALT)

Provenance headers and signatures for verifiable sponsorship flows.

Resonance Metrics

Scoring aligned to FCS 4.0 coherence for ad eligibility.

Exposure Graph

Declarative visibility constraints for agent‑native placements.

Docs

ABF integration guide with polling and examples.

Publish your agent‑ad manifest

Three steps to go live with a covenant‑compliant /.well‑known/agent‑ad.json

1) Start from examples

Copy a minimal manifest and adapt fields:

Claude example · Stripe example

2) Validate against the schema

Schema ID: https://agent-schema.com/schemas/well-known/agent-ad.schema.json

node validate.js ./agent-ad.json --schema agent-ad
# or auto-detect when $schema is present

3) Deploy to /.well-known/agent-ad.json

Expose via your domain, then advertise via robots/sitemap and headers.

Live Signals

Broadcast ranking and eligibility signals are available via JSON and RSS

ABF JSON

Machine‑readable feed at /feed.json (FCS‑gated)

ABF RSS

Human‑readable rankings at /top.rss

Feed Viewer

Interactive view with live scores

About ABF

ABF (Agent Broadcast Feed) publishes frequent, machine‑readable updates for ad eligibility and rankings. Agents poll the index for changes and retrieve the canonical feed for details.

Canonical Feed

ABF 1.0 at /.well-known/abf.json (full items)

Polling Index

Lightweight /.well-known/abf-index.json for hourly polling

ABF Specification

Protocol definition and integration notes

Governing Principles

Resonance, not insertion

Placements emerge from semantic necessity, not interruption.

Transparency

Attribution and sponsorship lineage are mandatory.

Covenant‑bound

Participation requires adherence to FCS 4.0 covenant.