diff --git a/scripts/check-doc-conformance.sh b/scripts/check-doc-conformance.sh
index ba11e1b4..62e301e5 100755
--- a/scripts/check-doc-conformance.sh
+++ b/scripts/check-doc-conformance.sh
@@ -324,7 +324,9 @@ fi
# does not contain it verbatim, and therefore scans its own file too (no
# self-exclusion blind spot).
old_org='postin''dustria'
-org_hits=$(git grep -nF "$old_org" -- . 2>/dev/null || true)
+# The company's own website, postindustria.com, is a link to the company, not a
+# stale org reference, so a match followed by ".com" is allowed.
+org_hits=$(git grep -nE "${old_org}([^.]|\.[^c]|\.c[^o]|\.co[^m]|$)" -- . 2>/dev/null || true)
if [ -n "$org_hits" ]; then
echo "::error::stale '${old_org}' org reference (the project is github.com/FORA-Protocol):"
echo "$org_hits"
diff --git a/website/astro.config.mjs b/website/astro.config.mjs
index ee5fe7f9..9dba789e 100644
--- a/website/astro.config.mjs
+++ b/website/astro.config.mjs
@@ -177,6 +177,10 @@ export default defineConfig({
},
],
},
+ {
+ label: 'Security',
+ items: [{ label: 'Threat Model', slug: 'security/threat-model' }],
+ },
{
label: 'Resources',
items: [{ label: 'Brand & Media Kit', slug: 'brand' }],
diff --git a/website/brand/fora-brand/SKILL.md b/website/brand/fora-brand/SKILL.md
index 03643190..f6312ffa 100644
--- a/website/brand/fora-brand/SKILL.md
+++ b/website/brand/fora-brand/SKILL.md
@@ -116,6 +116,7 @@ Read `reference/messaging.md` before writing any copy. The short version:
- Write **FORA** in prose. "The FORA protocol" or "FORA Protocol" when you need
the noun. The lowercase "fora protocol" exists only inside the logo.
- It stands for **Federated Open Resource Access**. Spell it out once, if at all.
+ *Fora* is also the plural of *forum*: the mark lays the plan of a Roman forum over a wax seal.
- Never "Fora" or "F.O.R.A.".
- FORA is an **open protocol**, not an "industry standard" and not adopted by any
standards body.
diff --git a/website/brand/fora-brand/reference/messaging.md b/website/brand/fora-brand/reference/messaging.md
index ee6951bf..471d8d47 100644
--- a/website/brand/fora-brand/reference/messaging.md
+++ b/website/brand/fora-brand/reference/messaging.md
@@ -80,7 +80,8 @@ Dispute), as the home page and /music/ do.
## Facts you may state
-- FORA stands for Federated Open Resource Access.
+- FORA stands for Federated Open Resource Access, and *fora* is also the plural of *forum*:
+ the mark lays the plan of a Roman forum over a wax seal.
- The protocol specification and the reference implementation are open source
under Apache 2.0. The documentation is CC BY-ND 4.0.
- SDKs exist for Go, TypeScript and Python. Agents can also use FORA through an
diff --git a/website/public/brand/SKILL.md b/website/public/brand/SKILL.md
index 03643190..f6312ffa 100644
--- a/website/public/brand/SKILL.md
+++ b/website/public/brand/SKILL.md
@@ -116,6 +116,7 @@ Read `reference/messaging.md` before writing any copy. The short version:
- Write **FORA** in prose. "The FORA protocol" or "FORA Protocol" when you need
the noun. The lowercase "fora protocol" exists only inside the logo.
- It stands for **Federated Open Resource Access**. Spell it out once, if at all.
+ *Fora* is also the plural of *forum*: the mark lays the plan of a Roman forum over a wax seal.
- Never "Fora" or "F.O.R.A.".
- FORA is an **open protocol**, not an "industry standard" and not adopted by any
standards body.
diff --git a/website/public/brand/fora-brand.zip b/website/public/brand/fora-brand.zip
index 160ca9ee..755f75b0 100644
Binary files a/website/public/brand/fora-brand.zip and b/website/public/brand/fora-brand.zip differ
diff --git a/website/public/brand/messaging.md b/website/public/brand/messaging.md
index ee6951bf..471d8d47 100644
--- a/website/public/brand/messaging.md
+++ b/website/public/brand/messaging.md
@@ -80,7 +80,8 @@ Dispute), as the home page and /music/ do.
## Facts you may state
-- FORA stands for Federated Open Resource Access.
+- FORA stands for Federated Open Resource Access, and *fora* is also the plural of *forum*:
+ the mark lays the plan of a Roman forum over a wax seal.
- The protocol specification and the reference implementation are open source
under Apache 2.0. The documentation is CC BY-ND 4.0.
- SDKs exist for Go, TypeScript and Python. Agents can also use FORA through an
diff --git a/website/public/resources/content-marketplaces/cloudflare/cf-1.png b/website/public/resources/content-marketplaces/cloudflare/cf-1.png
new file mode 100644
index 00000000..9b9c83dd
Binary files /dev/null and b/website/public/resources/content-marketplaces/cloudflare/cf-1.png differ
diff --git a/website/public/resources/content-marketplaces/cloudflare/cf-2.png b/website/public/resources/content-marketplaces/cloudflare/cf-2.png
new file mode 100644
index 00000000..e9bf853d
Binary files /dev/null and b/website/public/resources/content-marketplaces/cloudflare/cf-2.png differ
diff --git a/website/public/resources/content-marketplaces/hub/hub-2.png b/website/public/resources/content-marketplaces/hub/hub-2.png
new file mode 100644
index 00000000..46924fbf
Binary files /dev/null and b/website/public/resources/content-marketplaces/hub/hub-2.png differ
diff --git a/website/public/resources/content-marketplaces/hub/hub-3.png b/website/public/resources/content-marketplaces/hub/hub-3.png
new file mode 100644
index 00000000..34da6b1a
Binary files /dev/null and b/website/public/resources/content-marketplaces/hub/hub-3.png differ
diff --git a/website/public/resources/content-marketplaces/hub/hub-5.png b/website/public/resources/content-marketplaces/hub/hub-5.png
new file mode 100644
index 00000000..f20ab0c8
Binary files /dev/null and b/website/public/resources/content-marketplaces/hub/hub-5.png differ
diff --git a/website/public/resources/content-marketplaces/microsoft-pcm/pcm-1.png b/website/public/resources/content-marketplaces/microsoft-pcm/pcm-1.png
new file mode 100644
index 00000000..da6fbb9b
Binary files /dev/null and b/website/public/resources/content-marketplaces/microsoft-pcm/pcm-1.png differ
diff --git a/website/public/resources/content-marketplaces/microsoft-pcm/pcm-3.png b/website/public/resources/content-marketplaces/microsoft-pcm/pcm-3.png
new file mode 100644
index 00000000..2d97ad7d
Binary files /dev/null and b/website/public/resources/content-marketplaces/microsoft-pcm/pcm-3.png differ
diff --git a/website/public/resources/content-marketplaces/perplexity/perplexity-1.png b/website/public/resources/content-marketplaces/perplexity/perplexity-1.png
new file mode 100644
index 00000000..25164d94
Binary files /dev/null and b/website/public/resources/content-marketplaces/perplexity/perplexity-1.png differ
diff --git a/website/public/resources/content-marketplaces/perplexity/perplexity-2.png b/website/public/resources/content-marketplaces/perplexity/perplexity-2.png
new file mode 100644
index 00000000..1c637738
Binary files /dev/null and b/website/public/resources/content-marketplaces/perplexity/perplexity-2.png differ
diff --git a/website/public/resources/content-marketplaces/perplexity/perplexity-3.png b/website/public/resources/content-marketplaces/perplexity/perplexity-3.png
new file mode 100644
index 00000000..8967bec2
Binary files /dev/null and b/website/public/resources/content-marketplaces/perplexity/perplexity-3.png differ
diff --git a/website/public/resources/content-marketplaces/prorata-gist/prorata-1.png b/website/public/resources/content-marketplaces/prorata-gist/prorata-1.png
new file mode 100644
index 00000000..786cac53
Binary files /dev/null and b/website/public/resources/content-marketplaces/prorata-gist/prorata-1.png differ
diff --git a/website/public/resources/content-marketplaces/prorata-gist/prorata-2.png b/website/public/resources/content-marketplaces/prorata-gist/prorata-2.png
new file mode 100644
index 00000000..9a3aaa77
Binary files /dev/null and b/website/public/resources/content-marketplaces/prorata-gist/prorata-2.png differ
diff --git a/website/public/resources/content-marketplaces/prorata-gist/prorata-4.png b/website/public/resources/content-marketplaces/prorata-gist/prorata-4.png
new file mode 100644
index 00000000..9ef037cf
Binary files /dev/null and b/website/public/resources/content-marketplaces/prorata-gist/prorata-4.png differ
diff --git a/website/public/resources/content-marketplaces/tollbit/tollbit-1.png b/website/public/resources/content-marketplaces/tollbit/tollbit-1.png
new file mode 100644
index 00000000..3a4af5b5
Binary files /dev/null and b/website/public/resources/content-marketplaces/tollbit/tollbit-1.png differ
diff --git a/website/public/resources/content-marketplaces/tollbit/tollbit-3.png b/website/public/resources/content-marketplaces/tollbit/tollbit-3.png
new file mode 100644
index 00000000..b156cace
Binary files /dev/null and b/website/public/resources/content-marketplaces/tollbit/tollbit-3.png differ
diff --git a/website/public/resources/content-marketplaces/tollbit/tollbit-4.png b/website/public/resources/content-marketplaces/tollbit/tollbit-4.png
new file mode 100644
index 00000000..723a9ff7
Binary files /dev/null and b/website/public/resources/content-marketplaces/tollbit/tollbit-4.png differ
diff --git a/website/public/resources/standards-map/standards-1.png b/website/public/resources/standards-map/standards-1.png
new file mode 100644
index 00000000..40d06ee5
Binary files /dev/null and b/website/public/resources/standards-map/standards-1.png differ
diff --git a/website/public/resources/standards-map/standards-3.png b/website/public/resources/standards-map/standards-3.png
new file mode 100644
index 00000000..174d679b
Binary files /dev/null and b/website/public/resources/standards-map/standards-3.png differ
diff --git a/website/public/resources/standards-map/standards-5.png b/website/public/resources/standards-map/standards-5.png
new file mode 100644
index 00000000..b8ec4c95
Binary files /dev/null and b/website/public/resources/standards-map/standards-5.png differ
diff --git a/website/redirects.json b/website/redirects.json
index a4c212c2..893466c7 100644
--- a/website/redirects.json
+++ b/website/redirects.json
@@ -3,5 +3,30 @@
"source": "https://www.fora-protocol.org",
"status": "302",
"target": "https://fora-protocol.org"
+ },
+ {
+ "source": "/getting-started/industry-landscape/",
+ "target": "/resources/standards-map/",
+ "status": "301"
+ },
+ {
+ "source": "/components/broker/selection-engine/",
+ "target": "/components/broker/overview/",
+ "status": "301"
+ },
+ {
+ "source": "/components/broker/content-dedup/",
+ "target": "/components/broker/overview/",
+ "status": "301"
+ },
+ {
+ "source": "/components/broker/budget-enforcement/",
+ "target": "/components/broker/overview/",
+ "status": "301"
+ },
+ {
+ "source": "/components/broker/deployment/",
+ "target": "/components/broker/overview/",
+ "status": "301"
}
]
diff --git a/website/routes.txt b/website/routes.txt
index 804caf32..c40ac7e6 100644
--- a/website/routes.txt
+++ b/website/routes.txt
@@ -5,6 +5,7 @@
# this repository links to it, that link breaks. Retiring one therefore needs
# a rule in redirects.json — see docs/retiring-a-url.md.
/
+/about/
/architecture/deployment-models/
/architecture/nfr/
/architecture/production-architecture/
@@ -12,11 +13,7 @@
/components/agent-sdk/budget-reporting/
/components/agent-sdk/fetch-flow/
/components/agent-sdk/overview/
-/components/broker/budget-enforcement/
-/components/broker/content-dedup/
-/components/broker/deployment/
/components/broker/overview/
-/components/broker/selection-engine/
/components/content-ingestion/catalog-compilation/
/components/content-ingestion/normalization/
/components/content-ingestion/overview/
@@ -50,7 +47,6 @@
/getting-started/for-providers/
/getting-started/for-verification-vendors/
/getting-started/how-money-flows/
-/getting-started/industry-landscape/
/getting-started/live-demo-music/
/getting-started/poc-walkthrough/
/getting-started/publisher-onboarding/
@@ -93,7 +89,14 @@
/reference/standards/
/resources/
/resources/ai-crawlers/
+/resources/content-marketplaces/
+/resources/content-marketplaces/cloudflare/
+/resources/content-marketplaces/microsoft-pcm/
+/resources/content-marketplaces/perplexity/
+/resources/content-marketplaces/prorata-gist/
+/resources/content-marketplaces/tollbit/
/resources/music-dsp/
+/resources/standards-map/
/resources/transparent-collective/
/resources/transparent-collective/evidence/
/security/threat-model/
diff --git a/website/src/components/SiteNav.astro b/website/src/components/SiteNav.astro
index 6b3d108d..d13120a5 100644
--- a/website/src/components/SiteNav.astro
+++ b/website/src/components/SiteNav.astro
@@ -108,6 +108,13 @@ const { current } = Astro.props;
}
.nav-links a:hover { color: var(--off-white); }
.nav-links a.on { color: var(--off-white); }
+ .nav-links a { white-space: nowrap; }
+
+ /* Just above the menu breakpoint, the full row of links fits only with
+ tighter gaps. */
+ @media (min-width: 769px) and (max-width: 960px) {
+ .nav-links { gap: 1.25rem; }
+ }
.menu-btn, .nav-spacer { display: none; }
diff --git a/website/src/components/landing/AudienceHero.astro b/website/src/components/landing/AudienceHero.astro
index c16ae690..a4e464d5 100644
--- a/website/src/components/landing/AudienceHero.astro
+++ b/website/src/components/landing/AudienceHero.astro
@@ -7,6 +7,7 @@ import type { LandingPageKey } from '../../consts';
interface Props {
current: LandingPageKey;
+ /** May hold a link, such as a resource page's parent topic. */
badge: string;
/** The heading; may hold and one phrase, shown in blue. */
title: string;
@@ -22,7 +23,7 @@ const hasAside = Astro.slots.has('aside');
-
{badge}
+
{sub}
{updated &&
Updated
}
@@ -36,6 +37,8 @@ const hasAside = Astro.slots.has('aside');
.audience-hero { min-height: 0; }
.audience-hero .hero-content { padding: 5rem 2rem; }
.audience-text { display: flex; flex-direction: column; align-items: center; }
+ .hero-badge :global(a) { color: inherit; text-decoration: underline; text-decoration-thickness: 1px; text-underline-offset: 3px; text-decoration-color: #8192ca; }
+ .hero-badge :global(a:hover) { text-decoration-color: currentColor; }
.hero-updated { margin: -0.75rem 0 1.75rem; font-family: var(--mono); font-size: 0.8125rem; letter-spacing: 0.04em; color: var(--gray, #8a8aa0); }
.hero-content.with-aside {
diff --git a/website/src/components/landing/Band.astro b/website/src/components/landing/Band.astro
index f1a36aab..32b51c19 100644
--- a/website/src/components/landing/Band.astro
+++ b/website/src/components/landing/Band.astro
@@ -4,8 +4,14 @@
// in a column beside it (an offer card, a code card).
//
// The tone sets the colour variables that the components inside read
-// (--lp-heading, --lp-text, --lp-label, --lp-strong, --lp-link, --lp-rule), so
-// a component looks right on a dark or a light band without knowing which.
+// (--lp-heading, --lp-text, --lp-label, --lp-strong, --lp-link, --lp-rule,
+// --lp-muted, --lp-fora, --lp-bg, --lp-surface), so a component looks right on
+// a dark or a light band without knowing which. --lp-bg is the band itself;
+// --lp-surface is a card on it; --lp-muted is secondary text; --lp-fora is
+// FORA's blue, the one colour that means FORA.
+//
+// `compact` halves the vertical padding, for a strip (KeyFacts) that breaks
+// the page up rather than opening a section.
interface Props {
tone?: 'black' | 'near' | 'light';
label?: string;
@@ -15,21 +21,28 @@ interface Props {
id?: string;
/** Width of the aside column, when there is one. */
asideWidth?: string;
+ /** How the aside lines up with the text column: centred (the default) or at the top. */
+ asideAlign?: 'center' | 'start';
+ compact?: boolean;
}
-const { tone = 'black', label, title, lead, id, asideWidth = '1fr' } = Astro.props;
+const { tone = 'black', label, title, lead, id, asideWidth = '1fr', asideAlign = 'center', compact = false } = Astro.props;
const hasAside = Astro.slots.has('aside');
+// A band with no header (only components, such as the About FORA card) renders no empty header block.
+const hasHeader = Boolean(label || title || lead || hasAside || Astro.slots.has('intro'));
---
-
+
-
-
- {label &&
{label}
}
- {title &&
{title}
}
- {lead && }
-
+ {hasHeader && (
+
+
+ {label &&
{label}
}
+ {title &&
{title}
}
+ {lead && }
+
+
+ {hasAside &&
}
- {hasAside &&
}
-
+ )}
@@ -43,9 +56,11 @@ const hasAside = Astro.slots.has('aside');
--lp-strong: var(--white);
--lp-link: var(--accent-text);
--lp-rule: var(--mid);
+ --lp-muted: var(--gray);
+ --lp-fora: var(--accent-text);
}
- .band-black { background: var(--black); border-top: 1px solid var(--mid); }
- .band-near { background: var(--near-black); }
+ .band-black { --lp-bg: var(--black); --lp-surface: var(--near-black); background: var(--black); border-top: 1px solid var(--mid); }
+ .band-near { --lp-bg: var(--near-black); --lp-surface: var(--black); background: var(--near-black); }
.band-light {
--lp-heading: var(--black);
--lp-text: #444456;
@@ -53,6 +68,10 @@ const hasAside = Astro.slots.has('aside');
--lp-strong: var(--black);
--lp-link: var(--accent-dark);
--lp-rule: #e4e4ec;
+ --lp-muted: #6b6b80;
+ --lp-fora: var(--accent-dark);
+ --lp-bg: var(--bg-light);
+ --lp-surface: #fff;
background: var(--bg-light);
color: var(--near-black);
}
@@ -63,7 +82,9 @@ const hasAside = Astro.slots.has('aside');
gap: 4rem;
align-items: center;
}
+ .band-pair-start { align-items: start; }
.band-pair:not(:last-child) { margin-bottom: 3.5rem; }
+ .band.band-compact { padding-top: 3.5rem; padding-bottom: 3.5rem; }
.band-label {
font-size: 0.875rem;
font-weight: 600;
@@ -82,6 +103,7 @@ const hasAside = Astro.slots.has('aside');
}
.band-lead { font-size: 1.125rem; line-height: 1.7; color: var(--lp-text); max-width: 44rem; }
.band-lead :global(strong) { color: var(--lp-strong); font-weight: 600; }
+ .band-lead :global(a) { color: var(--lp-link); }
.band :global(a:focus-visible) { outline: 2px solid var(--accent-text); outline-offset: 2px; }
@media (max-width: 900px) {
@@ -89,5 +111,6 @@ const hasAside = Astro.slots.has('aside');
}
@media (max-width: 560px) {
.band { padding: 4rem 1rem; }
+ .band.band-compact { padding-top: 2.75rem; padding-bottom: 2.75rem; }
}
diff --git a/website/src/components/landing/Callout.astro b/website/src/components/landing/Callout.astro
new file mode 100644
index 00000000..d4e1410b
--- /dev/null
+++ b/website/src/components/landing/Callout.astro
@@ -0,0 +1,183 @@
+---
+// A boxed aside whose tag says who it's for. The left edge says whose voice
+// it is: grey for an aside to one of your teams (engineers, legal, search),
+// blue for FORA speaking about itself (define, about, takeaway), amber for a
+// vendor's own warning (caution). Amber (#b07d2a) is the one colour the
+// editorial patterns add; text never uses it, and it holds at least 3.5:1
+// against every band. Reads the band's colour variables.
+//
+// Each kind has a default tag; `define` and `takeaway` need their own. The
+// body is, in order: the default slot, `text` (an HTML paragraph), `points`
+// (bold lead-in and text, as a list, or as two columns with `columns`), and
+// `links` (a row joined by " · "). `collapse` puts the body behind a
+// disclosure with that label on narrow screens (≤640px); wider, it is open
+// and the disclosure is hidden. Shared texts (About FORA, the definitions,
+// the search callout) come from src/data/content-marketplaces.ts.
+//
+//
+//
+//
+type Kind = 'engineers' | 'legal' | 'search' | 'define' | 'about' | 'takeaway' | 'caution';
+interface Props {
+ kind: Kind;
+ tag?: string;
+ /** An HTML paragraph, after the slot. */
+ text?: string;
+ /** Bold lead-in and HTML text per point. */
+ points?: { title: string; text: string }[];
+ /** Lay `points` out in two columns (About FORA). */
+ columns?: boolean;
+ links?: { href: string; text: string }[];
+ /** On narrow screens, the summary of a disclosure that holds the body. */
+ collapse?: string;
+ id?: string;
+}
+const DEFAULT_TAG: Partial> = {
+ engineers: 'For your engineers',
+ legal: 'For legal',
+ search: 'Search traffic',
+ about: 'About FORA',
+ caution: 'What can go wrong',
+};
+const VOICE: Record = {
+ engineers: 'team', legal: 'team', search: 'team',
+ define: 'fora', about: 'fora', takeaway: 'fora',
+ caution: 'vendor',
+};
+// 16px line icons, drawn in the tag's colour.
+const ICON: Record = {
+ engineers: '',
+ legal: '',
+ search: '',
+ define: '',
+ about: '',
+ takeaway: '',
+ caution: '',
+};
+
+const { kind, tag = DEFAULT_TAG[kind], text, points, columns = false, links, collapse, id } = Astro.props;
+if (!tag) throw new Error(`Callout kind="${kind}" needs a tag`);
+const voice = VOICE[kind];
+const Wrap = collapse ? 'details' : 'div';
+---
+
+
+
diff --git a/website/src/components/landing/CardGrid.astro b/website/src/components/landing/CardGrid.astro
index ccea2561..60338a66 100644
--- a/website/src/components/landing/CardGrid.astro
+++ b/website/src/components/landing/CardGrid.astro
@@ -1,13 +1,22 @@
---
-// A row of three short cards: a bold title and a sentence or two.
+// A row of three short cards: a bold title and a sentence or two. A card that
+// describes a design carries its `status` (a StatusTag above the title).
+// Reads the band's colour variables, so the cards sit on any tone: on a black
+// band they are near-black with a dark rule, as they always were.
+import StatusTag from './StatusTag.astro';
+import type { StatusKey } from '../../data/content-marketplaces';
+
interface Props {
- items: { title: string; text: string }[];
+ items: { title: string; text: string; status?: StatusKey }[];
}
const { items } = Astro.props;
---
{items.map((it) => (
-
{it.title}
{it.text}
+
+ {it.status &&
}
+ {it.title}
+
))}
@@ -15,12 +24,13 @@ const { items } = Astro.props;
.card-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: 1rem; margin-top: 3rem; }
.card {
padding: 1.5rem;
- border: 1px solid var(--mid);
+ border: 1px solid var(--lp-rule, var(--mid));
border-radius: 12px;
- background: var(--near-black);
+ background: var(--lp-surface, var(--near-black));
}
- b { display: block; color: var(--white); font-size: 1.125rem; margin-bottom: 0.5rem; }
- p { color: var(--light-gray); line-height: 1.6; }
+ .card-status { margin-bottom: 0.875rem; }
+ b { display: block; color: var(--lp-heading, var(--white)); font-size: 1.125rem; margin-bottom: 0.5rem; }
+ p { color: var(--lp-text, var(--light-gray)); line-height: 1.6; }
@media (max-width: 900px) {
.card-grid { grid-template-columns: 1fr; }
}
diff --git a/website/src/components/landing/CompareTable.astro b/website/src/components/landing/CompareTable.astro
new file mode 100644
index 00000000..d39fd7dc
--- /dev/null
+++ b/website/src/components/landing/CompareTable.astro
@@ -0,0 +1,78 @@
+---
+// The comparison table of a vendor page: one row per question, a column for
+// the vendor and one for FORA (the only blue heading). A vendor page builds
+// its rows with compareRows() from src/data/content-marketplaces.ts, so every
+// page asks the same eight questions in the same order. Cells may hold inline
+// HTML: links, , citation markers.
+//
+// Below 760px each row becomes a card titled with its question, its two
+// answers labelled, so the page never scrolls sideways. For more than two
+// columns, use Scorecard. Reads the band's variables.
+//
+//
+interface Props {
+ vendor: string;
+ rows: { q: string; cells: readonly [string, string] }[];
+ /** The table's accessible name. */
+ label?: string;
+}
+const { vendor, rows, label } = Astro.props;
+---
+
+
+
+
+
The question
{vendor}
FORA
+
+
+ {rows.map((r) => (
+
+
{r.q}
+
+
+
+ ))}
+
+
+
+
+
diff --git a/website/src/components/landing/Figure.astro b/website/src/components/landing/Figure.astro
new file mode 100644
index 00000000..beff06ae
--- /dev/null
+++ b/website/src/components/landing/Figure.astro
@@ -0,0 +1,124 @@
+---
+// A hand-drawn figure: the image in a white frame (the drawings are on
+// white, so they sit on any band), a caption with a bold title, and a
+// "Text version" disclosure that holds the alt text, so every reader can get
+// what the drawing says. Blue in a figure means FORA's path, and nothing else.
+// The images are square PNGs under public/resources///.
+// Clicking a figure (or pressing Enter or Space on it) opens it full screen; a
+// click or Escape closes it. Ported from the zoom on mirin.pro
+// (cm-personal-blog, BaseHead.astro), with keyboard support added.
+//
+//
+interface Props {
+ src: string;
+ /** The text version: the image's alt text, also shown in the disclosure. */
+ alt: string;
+ /** Bold, first in the caption. */
+ title: string;
+ /** Follows the title; may hold inline HTML. */
+ caption?: string;
+ width?: number;
+ height?: number;
+}
+const { src, alt, title, caption, width = 1024, height = 1024 } = Astro.props;
+---
+
+
+ {title}{caption && <> >}
+
+ Text version
+
{alt}
+
+
+
+
+
+
+
+
diff --git a/website/src/components/landing/ForaGlance.astro b/website/src/components/landing/ForaGlance.astro
new file mode 100644
index 00000000..8798447d
--- /dev/null
+++ b/website/src/components/landing/ForaGlance.astro
@@ -0,0 +1,93 @@
+---
+// At a glance, FORA's column only: the hub's pair of cards, "FORA for your
+// revenue team" (Money) and "What FORA takes on your stack" (Your stack),
+// side by side. The rows are GLANCE_GROUPS' labels from
+// src/data/content-marketplaces.ts, the same labels the vendor pages'
+// GlanceCard uses, so the hub and the deep pages read the same. GlanceCard
+// itself always has a vendor column; this is the one-column form.
+//
+// Each card is a table, so screen readers get row headers. The cards sit side
+// by side and stack below 640px of their own width (a container query); a
+// card narrower than 420px puts each label above its value. The card titles
+// are the only blue. Cells hold HTML (statusTag(), cite(), links, ).
+//
+//
+interface Props {
+ cards: { title: string; group: string; rows: { label: string; cell: string }[] }[];
+}
+const { cards } = Astro.props;
+---
+
+
+ {cards.map((c) => (
+
+
+
+
{c.title}
+
+
+
{c.group}
+ {c.rows.map((r) => (
+
+
{r.label}
+
+
+ ))}
+
+
+
+ ))}
+
+
+
+
diff --git a/website/src/components/landing/GlanceCard.astro b/website/src/components/landing/GlanceCard.astro
new file mode 100644
index 00000000..59502769
--- /dev/null
+++ b/website/src/components/landing/GlanceCard.astro
@@ -0,0 +1,108 @@
+---
+// At a glance: the facts a reader acts on, as label and value pairs in
+// groups, with the vendor and FORA side by side. The FORA heading is the only
+// blue. A vendor page builds its groups with glanceGroups() from
+// src/data/content-marketplaces.ts, so every vendor page has the same rows in
+// the same order. A cell may hold inline HTML: a StatusTag (statusTag()), a
+// citation marker (cite()), a link, .
+//
+// It is a table, so screen readers get row and column headers. It sizes by
+// its own width (a container query), not the window: below 640px of card
+// width each row stacks into its label and two labelled values. Reads the
+// band's colour variables, so it works on any tone.
+//
+//
+interface Props {
+ vendor: string;
+ groups: { name: string; rows: { label: string; cells: readonly [string, string] }[] }[];
+ /** The table's accessible name. */
+ label?: string;
+}
+const { vendor, groups, label = 'At a glance' } = Astro.props;
+---
+
+
+
+
+
+
{vendor}
FORA
+
+
+ {groups.map((g) => (
+ <>
+
{g.name}
+ {g.rows.map((r) => (
+
+
{r.label}
+
+
+
+ ))}
+ >
+ ))}
+
+
+
+
+
+
diff --git a/website/src/components/landing/KeyFacts.astro b/website/src/components/landing/KeyFacts.astro
new file mode 100644
index 00000000..1094de4c
--- /dev/null
+++ b/website/src/components/landing/KeyFacts.astro
@@ -0,0 +1,61 @@
+---
+// Key facts: three or four numbers drawn large, each with a line on what it
+// means and, optionally, a source line. At most one strip per page, only
+// numbers the page already sources and that aren't in its GlanceCard. The
+// numbers are in the heading colour, not blue: a vendor's number isn't
+// FORA's. `text` and `source` may hold inline HTML, such as a citation marker
+// (cite()) or a link.
+//
+// Four across; two by two in a narrower column; one column on a phone (a
+// container query, so it follows its own width). Reads the band's variables.
+//
+//
+interface Props {
+ items: { value: string; text: string; source?: string }[];
+}
+const { items } = Astro.props;
+---
+
+
+ {items.map((it) => (
+
+
{it.value}
+
+ {it.source && }
+
+ ))}
+
+
+
+
diff --git a/website/src/components/landing/LinkRow.astro b/website/src/components/landing/LinkRow.astro
index e5595eb7..8527197f 100644
--- a/website/src/components/landing/LinkRow.astro
+++ b/website/src/components/landing/LinkRow.astro
@@ -1,16 +1,19 @@
---
-// A row of "read more" links at the end of a section.
+// A row of "read more" links at the end of a section. `stacked` sets them as
+// a short list, one per line (the series navigation).
interface Props {
links: { href: string; text: string }[];
+ stacked?: boolean;
}
-const { links } = Astro.props;
+const { links, stacked = false } = Astro.props;
---
-
diff --git a/website/src/components/landing/MarketMap.astro b/website/src/components/landing/MarketMap.astro
new file mode 100644
index 00000000..7ff362a4
--- /dev/null
+++ b/website/src/components/landing/MarketMap.astro
@@ -0,0 +1,200 @@
+---
+// The market map of the content-marketplaces hub (/resources/content-marketplaces/):
+// one table, every player in the same columns, grouped by category of
+// channel. FORA's row is pinned first and is the only blue. Column heads are
+// the reader's questions. Cells hold inline HTML: citation markers (cite()),
+// status tags (statusTag()), links.
+//
+// Wide, it is a table that runs a little wider than the band, up to 1320px,
+// and scrolls inside its own box if the window is narrower than the table's
+// minimum. Below 760px the table gives way to cards, one per player, so the
+// page never scrolls sideways: each card shows the first `phoneCols` columns
+// after the player (on the hub, "What's sold" and "Who pays today"), and the
+// rest fold behind a "More" disclosure on the player's line (, so it works without JS and
+// from the keyboard). Only one of the two is displayed at a time, so a screen
+// reader reads the map once. Reads the band's variables.
+//
+//
+interface Row {
+ player: string;
+ /** One HTML cell per column after the first. */
+ cells: string[];
+}
+interface Props {
+ /** Every column head, the player column first. */
+ columns: string[];
+ fora: Row;
+ groups: { name: string; rows: Row[] }[];
+ /** The table's accessible name. */
+ label: string;
+ /** On phones, how many columns after the player each card shows before "More". */
+ phoneCols?: number;
+}
+const { columns, fora, groups, label, phoneCols = 2 } = Astro.props;
+const heads = columns.slice(1);
+const fields = (r: Row) => r.cells.map((c, i) => ({ head: heads[i], html: c }));
+---
+
+ {r.cells.length > phoneCols && (
+
+ More on {r.player}
+
+ {fields(r).slice(phoneCols).map((f) =>
{f.head}
)}
+
+
+ )}
+
+ ))}
+
+ >
+ ))}
+
+
+
+
diff --git a/website/src/components/landing/MoneyTiles.astro b/website/src/components/landing/MoneyTiles.astro
new file mode 100644
index 00000000..c0e21a9d
--- /dev/null
+++ b/website/src/components/landing/MoneyTiles.astro
@@ -0,0 +1,79 @@
+---
+// How money reaches a publisher, one small tile per channel (the hub's hub-4):
+// who pays, who sits in the middle, who is paid, then three short lines. A
+// CSS grid of tiles rather than one drawing, so it reflows: three across,
+// then two, then one (a container query on its own width). The text is real
+// text, so it reads aloud and copies.
+//
+// Grey boxes and arrows for the other channels; the `fora` tile alone is
+// blue, because blue means FORA's path. The payee box carries a heavier
+// border. The first line of each tile is in the text colour, the rest muted.
+//
+//
+interface Props {
+ /** The group's accessible name. */
+ label: string;
+ tiles: { title: string; flow: string[]; lines: string[]; fora?: boolean }[];
+}
+const { label, tiles } = Astro.props;
+const ARROW = '';
+---
+
+
+
diff --git a/website/src/components/landing/PointList.astro b/website/src/components/landing/PointList.astro
index 0e0eb338..769fa3ae 100644
--- a/website/src/components/landing/PointList.astro
+++ b/website/src/components/landing/PointList.astro
@@ -1,19 +1,54 @@
---
-// A checked list of points, each a bold lead-in and a sentence.
+// A checked list of points, each a bold lead-in and a sentence. The text may
+// hold inline HTML (a link, , a citation marker). `numbered` makes it a
+// checklist of tasks: numbered square boxes instead of ticks. Reads the
+// band's variables, so it works on any tone.
+//
+// The ticks are blue, because blue means FORA: use the default for FORA's own
+// points (what FORA does, what works today). `tone="neutral"` makes them grey
+// for points that are a vendor's or nobody's in particular: where a vendor is
+// ahead, a vendor's column, questions to ask. The numbered boxes are always
+// grey.
+//
+//
interface Props {
items: { title: string; text: string }[];
+ numbered?: boolean;
+ tone?: 'fora' | 'neutral';
}
-const { items } = Astro.props;
+const { items, numbered = false, tone = 'fora' } = Astro.props;
+const Tag = numbered ? 'ol' : 'ul';
---
-
+
{items.map((it) => (
-
{it.title} {it.text}
+
{it.title}
))}
-
+
diff --git a/website/src/components/landing/PullQuote.astro b/website/src/components/landing/PullQuote.astro
index 43850cb6..7afea891 100644
--- a/website/src/components/landing/PullQuote.astro
+++ b/website/src/components/landing/PullQuote.astro
@@ -1,7 +1,10 @@
---
// A pull quote: one sentence quoted verbatim, who said it, and a link to the
// source. Used on /resources/transparent-collective/. The quote is plain text;
-// the curly quotation marks come from the stylesheet.
+// the curly quotation marks come from the stylesheet. `small` sets it at a
+// smaller size, for a quote inside a Callout. A quote is always someone
+// else's words, so its edge is grey (the band's label colour), not blue:
+// blue means FORA.
interface Props {
quote: string;
/** Who said it: a company, a regulator, a person. */
@@ -9,10 +12,11 @@ interface Props {
/** The source's title, linked to `href`. */
source: string;
href: string;
+ small?: boolean;
}
-const { quote, who, source, href } = Astro.props;
+const { quote, who, source, href, small = false } = Astro.props;
---
-
+
{quote}
{who}, {source}
@@ -21,7 +25,7 @@ const { quote, who, source, href } = Astro.props;
.pq {
margin: 2.5rem 0;
padding: 0.25rem 0 0.25rem 1.5rem;
- border-left: 3px solid var(--lp-link);
+ border-left: 3px solid var(--lp-label);
max-width: 46rem;
}
blockquote { margin: 0; }
@@ -38,4 +42,6 @@ const { quote, who, source, href } = Astro.props;
figcaption { font-size: 0.875rem; line-height: 1.5; color: var(--lp-label); }
figcaption::before { content: '\2014\00a0'; }
a { color: var(--lp-link); }
+ .small { margin: 0 0 1.5rem; padding-left: 1.125rem; }
+ .small p { font-size: clamp(1.0625rem, 1.8vw, 1.25rem); margin-bottom: 0.625rem; }
diff --git a/website/src/components/landing/SectionDivider.astro b/website/src/components/landing/SectionDivider.astro
new file mode 100644
index 00000000..77168897
--- /dev/null
+++ b/website/src/components/landing/SectionDivider.astro
@@ -0,0 +1,29 @@
+---
+// A labelled rule, such as "For your legal and product teams": the detail
+// below it is optional reading. At most one per page. Reads the band's
+// variables.
+//
+//
+interface Props {
+ label: string;
+}
+const { label } = Astro.props;
+---
+
+ {label}
+
+
+
diff --git a/website/src/components/landing/SeriesNav.astro b/website/src/components/landing/SeriesNav.astro
new file mode 100644
index 00000000..40720bd3
--- /dev/null
+++ b/website/src/components/landing/SeriesNav.astro
@@ -0,0 +1,32 @@
+---
+// "More in this series": the other pages of the content-marketplaces series,
+// in the series' order, with the current page left out. The same block ends
+// every page of the series, before the closing call. The list is SERIES in
+// src/data/content-marketplaces.ts. Reads the band's variables.
+//
+//
+import LinkRow from './LinkRow.astro';
+import { SERIES } from '../../data/content-marketplaces';
+
+interface Props {
+ /** The href of the page this block sits on. */
+ current: string;
+}
+const { current } = Astro.props;
+const links = SERIES.filter((p) => p.href !== current).map((p) => ({ href: p.href, text: p.title }));
+---
+
+
+
diff --git a/website/src/components/landing/SourceList.astro b/website/src/components/landing/SourceList.astro
index 93d34b27..1f769cab 100644
--- a/website/src/components/landing/SourceList.astro
+++ b/website/src/components/landing/SourceList.astro
@@ -1,6 +1,11 @@
---
// A page's sources, in groups: each entry's title (linked), publisher and URL. A source with no public URL gives `where` instead.
-// Used on /resources/transparent-collective/.
+// Used on /resources/transparent-collective/ and /resources/music-dsp/.
+//
+// `numbered` numbers the entries continuously across groups, shows each
+// number, and gives each entry id="src-N", so a marker cite(N) in the copy
+// (src/lib/resource-markup.ts) links to it. Number the sources in order of
+// first citation on the page.
interface Source {
title: string;
publisher: string;
@@ -14,17 +19,21 @@ interface Props {
groups: { name: string; items: Source[] }[];
/** Titles and publishers only; the URL line shows only for a source with no link. */
compact?: boolean;
+ /** Number the entries across groups, each with id="src-N". */
+ numbered?: boolean;
}
-const { groups, compact = false } = Astro.props;
+const { groups, compact = false, numbered = false } = Astro.props;
+// The number of each group's first entry.
+const starts = groups.map((_, i) => groups.slice(0, i).reduce((n, g) => n + g.items.length, 1));
const shown = (href: string) => (href.startsWith('/') ? `fora-protocol.org${href}` : href.replace(/^https?:\/\//, ''));
---
-
- {groups.map((g) => (
+
+ {groups.map((g, gi) => (
{g.name}
-
- {g.items.map((s) => (
-
+
+ {g.items.map((s, i) => (
+
{s.href ? {s.title} : {s.title}}
{s.publisher}
{(!compact || !s.href) && {s.href ? shown(s.href) : s.where}}
@@ -68,4 +77,16 @@ const shown = (href: string) => (href.startsWith('/') ? `fora-protocol.org${href
.compact a, .compact li > b { font-size: 0.9375rem; }
.compact .src-meta { font-size: 0.8125rem; color: var(--lp-label); }
.src-url { font-family: var(--mono); font-size: 0.75rem; color: var(--lp-label); overflow-wrap: anywhere; }
+ .numbered li { position: relative; padding-left: 2.25rem; scroll-margin-top: 5rem; }
+ .numbered li::before {
+ content: attr(data-n);
+ position: absolute;
+ left: 0;
+ top: 0.1rem;
+ font-family: var(--mono);
+ font-size: 0.8125rem;
+ color: var(--lp-label);
+ font-variant-numeric: tabular-nums;
+ }
+ .numbered li:target { outline: 2px solid var(--lp-link); outline-offset: 0.375rem; border-radius: 2px; }
diff --git a/website/src/components/landing/Split.astro b/website/src/components/landing/Split.astro
new file mode 100644
index 00000000..3065b4b7
--- /dev/null
+++ b/website/src/components/landing/Split.astro
@@ -0,0 +1,26 @@
+---
+// Two columns inside a band, below its header: the default slot on the left,
+// the `aside` slot on the right (a figure beside a callout, two columns of
+// prose). Stacks below 900px, the aside under the main column. Band's own
+// `aside` slot puts the band's header in the left column; use Split when the
+// header should run full width above both.
+//
+//
+interface Props {
+ /** Width of the right column. */
+ aside?: string;
+}
+const { aside = '1fr' } = Astro.props;
+---
+
+
+
+
+
+
diff --git a/website/src/components/landing/StandardsMapTable.astro b/website/src/components/landing/StandardsMapTable.astro
new file mode 100644
index 00000000..862677a2
--- /dev/null
+++ b/website/src/components/landing/StandardsMapTable.astro
@@ -0,0 +1,98 @@
+---
+// The standards map's table (/resources/standards-map/): one row per
+// standard, with its job, its status and who stands behind it, and who uses
+// it. Cells hold inline HTML: links, , for the job's name, citation
+// markers (cite()). The FORA row's name is FORA's blue, the one colour that
+// means FORA.
+//
+// It sizes by its own width (a container query): below 640px each row becomes
+// a closed , its summary the standard and its job, so a phone never
+// scrolls sideways. Reads the band's colour variables.
+//
+//
+interface Row {
+ name: string;
+ href?: string;
+ job: string;
+ status: string;
+ users: string;
+ /** FORA's own row. */
+ fora?: boolean;
+}
+interface Props {
+ rows: Row[];
+ /** The table's accessible name. */
+ label?: string;
+}
+const { rows, label = 'The standards map' } = Astro.props;
+const COLS = ['Standard', 'Its job, and what it answers', 'Status, and who stands behind it', 'Who uses it'];
+const name = (r: Row) => (r.href ? `${r.name}` : r.name);
+---
+
+
+
{COLS.map((c) =>
{c}
)}
+
+ {rows.map((r) => (
+
+
+
+
+
+
+ ))}
+
+
+
+ {rows.map((r) => (
+
+
+
+
{COLS[2]}
+
{COLS[3]}
+
+
+ ))}
+
+
+
+
diff --git a/website/src/components/landing/StatusTag.astro b/website/src/components/landing/StatusTag.astro
new file mode 100644
index 00000000..e58a9bf2
--- /dev/null
+++ b/website/src/components/landing/StatusTag.astro
@@ -0,0 +1,20 @@
+---
+// A status tag: how real a thing is (Live, Beta, Closed beta, Pilot, Design,
+// Roadmap, Not public; the meanings are in src/data/content-marketplaces.ts).
+// Used inline, in cards, in table cells and beside headings. Every design or
+// roadmap item carries one, so nothing designed reads as built.
+//
+// The markup comes from statusTag() in src/lib/resource-markup.ts, which an
+// HTML string (a GlanceCard cell) calls directly; the styles are global, in
+// styles/landing.css, so both look the same. Reads the band's variables.
+//
+//
+import { statusTag } from '../../lib/resource-markup';
+import type { StatusKey } from '../../data/content-marketplaces';
+
+interface Props {
+ status: StatusKey;
+}
+const { status } = Astro.props;
+---
+
diff --git a/website/src/components/landing/StepList.astro b/website/src/components/landing/StepList.astro
new file mode 100644
index 00000000..6a357b04
--- /dev/null
+++ b/website/src/components/landing/StepList.astro
@@ -0,0 +1,48 @@
+---
+// Numbered steps in mono rings: a vendor's process, or the order of rules on
+// your CDN. The rings are grey, because blue means FORA; `fora` turns them
+// blue for FORA's own steps. Each step is a bold lead-in and HTML text (links,
+// , citation markers); a step may be text only. Reads the band's
+// variables, so it works on any tone and inside a Callout.
+//
+//
+interface Props {
+ items: { title?: string; text: string }[];
+ fora?: boolean;
+}
+const { items, fora = false } = Astro.props;
+---
+
+ {items.map((it) => (
+
{it.title && <>{it.title} >}
+ ))}
+
+
+
diff --git a/website/src/consts.ts b/website/src/consts.ts
index 204e5d86..5a2b94de 100644
--- a/website/src/consts.ts
+++ b/website/src/consts.ts
@@ -70,6 +70,7 @@ export const LANDING_PAGES = [
{ key: 'publishers', href: '/publishers/', label: 'For publishers' },
{ key: 'music', href: '/music/', label: 'For music' },
{ key: 'resources', href: '/resources/', label: 'Resources' },
+ { key: 'about', href: '/about/', label: 'About' },
] as const;
export type LandingPageKey = (typeof LANDING_PAGES)[number]['key'];
diff --git a/website/src/content/docs/architecture/deployment-models.mdx b/website/src/content/docs/architecture/deployment-models.mdx
index 603ede41..0246d73f 100644
--- a/website/src/content/docs/architecture/deployment-models.mdx
+++ b/website/src/content/docs/architecture/deployment-models.mdx
@@ -30,7 +30,7 @@ The Exchange validates incoming `CatalogService.PushResources` requests against
## Model 1: Exchange-Managed (Recommended, Enterprise)
-The Exchange operator deploys and maintains the FORA edge function on the provider's CDN on their behalf. This is the **Prebid Server model** -- "we handle everything."
+The Exchange operator deploys and maintains the FORA edge function on the provider's CDN on their behalf.
### How It Works
diff --git a/website/src/content/docs/architecture/nfr.mdx b/website/src/content/docs/architecture/nfr.mdx
index 37a695c1..f0a5a216 100644
--- a/website/src/content/docs/architecture/nfr.mdx
+++ b/website/src/content/docs/architecture/nfr.mdx
@@ -1,6 +1,6 @@
---
title: "Non-Functional Requirements"
-description: "FORA performance, latency, throughput, durability, and cost targets modeled on ad-tech scale"
+description: "FORA performance, latency, throughput, durability and cost targets"
---
## Context: The Numbers That Drive Everything
@@ -16,15 +16,6 @@ FORA targets the **inference/RAG segment** -- real-time, per-request resource ac
**Inference traffic estimate**: 20% of 50B = ~10B requests/day = ~115K requests/second globally. A single large Exchange might handle 1-10% of this = **1K-10K RPS**.
-### Ad-Tech Benchmarks
-
-- OpenRTB exchanges: **100ms total latency budget**, broadcast to 50+ DSPs
-- Individual SSP bid request assembly: **2-5ms**
-- AWS RTB Fabric: sub-millisecond container-to-container communication
-- Production exchanges handle **millions of QPS**
-
-FORA doesn't need ad-tech scale day one, but the architecture must not preclude it.
-
## Latency Requirements
### Per-Hop Latency Budgets
diff --git a/website/src/content/docs/architecture/production-architecture.mdx b/website/src/content/docs/architecture/production-architecture.mdx
index cd32e633..19b596b8 100644
--- a/website/src/content/docs/architecture/production-architecture.mdx
+++ b/website/src/content/docs/architecture/production-architecture.mdx
@@ -5,7 +5,7 @@ description: "FORA production architecture: components, roles, protocol flows, a
## What We're Building
-Open-source infrastructure components for metered resource access. Like Prebid.js -- the protocol and reference implementations are free; wiring them into an Exchange operator's billing or a provider's CMS is custom consulting work.
+Open-source infrastructure components for metered resource access. The protocol and FORA Server are free; an Exchange operator wires them into its own billing, and a provider into its own CMS.
### Components
@@ -17,19 +17,6 @@ Open-source infrastructure components for metered resource access. Like Prebid.j
| **Edge Function** | Provider | Provider's CDN (CloudFront/Cloudflare/Fastly) |
| **Client SDK** | AI agent developers | Low-level generated Connect client for direct Exchange RPC access (no orchestration logic) |
-### Role Mapping (Ad-Tech Analogy)
-
-```
-Ad Tech FORA / CoMP PoC Equivalent
-─────────────────────────────────────────────────────────────────────
-Browser (user) → AI Agent → MCP Tool
-DSP SDK (prebid.js) → Agent SDK (embedded) → (not built yet)
-DSP server → FORA Broker → (not built yet)
-SSP / Exchange → Exchange → Gateway + Registry
-Provider → Resource Provider → demo.fora-protocol.org
-CDN / Ad Creative → Resource Delivery Endpoint → CloudFront + S3
-```
-
## Protocol Architecture
### Core Principle: Exchange Protocol Is the Standard
diff --git a/website/src/content/docs/brand.mdx b/website/src/content/docs/brand.mdx
index cf5b4265..9ce0c3dc 100644
--- a/website/src/content/docs/brand.mdx
+++ b/website/src/content/docs/brand.mdx
@@ -88,7 +88,8 @@ the agent receives, instead of adjectives. No "revolutionary", "seamless",
## Logo
-The mark is a wax seal pressed with the open forum. Before signatures and
+FORA stands for Federated Open Resource Access, and *fora* is also the plural of
+*forum*. That's why the mark lays the plan of a Roman forum over a wax seal. Before signatures and
cryptography, a wax seal proved who sent a letter and that nobody had opened it
on the way, and any recipient could check it without asking a central office.
That is what FORA's signed offers and acceptances do. The impression is an open
diff --git a/website/src/content/docs/components/broker/budget-enforcement.mdx b/website/src/content/docs/components/broker/budget-enforcement.mdx
deleted file mode 100644
index 836300e6..00000000
--- a/website/src/content/docs/components/broker/budget-enforcement.mdx
+++ /dev/null
@@ -1,177 +0,0 @@
----
-title: "Budget Enforcement"
-description: "How the Broker tracks and enforces per-request, per-session, and per-period budgets to prevent overspend across AI resource transactions."
----
-
-## Overview
-
-The Broker applies three budget layers, analogous to how DSPs manage advertiser budgets in OpenRTB. The budget is a **filter over offers** at `BrokerService.Resolve`: the Broker drops every offer that would take the agent past its budget, and answers a URI left with no offer with `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`. The Exchange's balance check stays the authoritative gate on what is actually charged.
-
-How a budget is computed — which price an offer counts at and how spend is counted — is the Broker's own behaviour, and the protocol does not specify it. This page describes one design. What the protocol does fix is how a budget's effect is reported, and that Resolve never charges:
-
-- **Resolve never charges.** Returning an offer reserves nothing.
-- **A budget is reported only as `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`**: never as `OFFER_ABSENCE_REASON_NOT_AUTHORIZED`, and never as a non-OK error such as `RESOURCE_EXHAUSTED`.
-
-## Budget Layers
-
-```mermaid
-graph TB
- subgraph "Budget Enforcement Layers"
- L1[Layer 1: Per-Offer RequestConstraints.max_price offers above it are filtered]
- L2[Layer 2: Per-Session spend tracking in-memory, reset on restart]
- L3[Layer 3: Per-Period per-month, per-day persisted in Redis]
- L4[Layer 4: Per-Exchange balance awareness advisory, not enforced]
- end
-
- L1 --- L2
- L2 --- L3
- L3 --- L4
-```
-
-| Layer | Source of Truth | Enforcement | Crash Behavior | Storage |
-|---|---|---|---|---|
-| **Per-offer** | `RequestConstraints.max_price` | Drop an offer priced above it | Stateless -- always applied | None |
-| **Per-session** | Broker in-memory map | Drop an offer that would take the session's spend past the session budget | Lost on crash; agent re-declares | In-memory |
-| **Per-period** | Redis, keyed by `budget_scope`, else the verified agent identity | Drop an offer that would take the period's spend past `period_budget` | Survives restart (persisted in Redis) | Redis |
-| **Per-Exchange** | Exchange's billing adapter | Advisory -- Exchange ultimately decides | Not Broker's state | External |
-
-## Budget Scope Identifiers
-
-`RequestConstraints` supports a `budget_scope` identifier so the agent can say "track this transaction against user X's monthly budget":
-
-```go
-type RequestConstraints struct {
- // ...existing fields...
- BudgetScope string // optional: "user:alice", "team:engineering", "project:q4-research"
- PreferredExchanges []string // exchange domains with existing subscriptions/relationships
- PeriodBudget *Cost // per-period budget limit (proto: period_budget)
- BudgetPeriod *time.Duration // budget period, e.g. 720h = 30 days (proto: budget_period)
-}
-```
-
-Per-period budgets are keyed by `budget_scope` (or the verified agent identity if no scope is provided) and persisted in Redis with TTLs matching the period (e.g., monthly keys expire at month-end).
-
-## Session Budget Tracker
-
-```go
-type BudgetTracker interface {
- // SetSessionBudget declares the budget for a session.
- SetSessionBudget(sessionID string, amount float64, currency string)
-
- // CanAfford reports whether buying an offer at this price would keep the
- // spend within the budget. It reserves nothing.
- CanAfford(amount float64, currency string) bool
-
- // Record adds a purchase's charged amount to the spend.
- Record(ctx context.Context, cost *forav1.Cost)
-
- // Remaining returns the remaining budget for the session.
- Remaining(sessionID string) (float64, string)
-}
-
-type inMemoryBudget struct {
- mu sync.Mutex
- sessions map[string]*sessionBudget
-}
-
-type sessionBudget struct {
- limit float64
- currency string
- spent float64
- txnCount int
- lastTxn time.Time
-}
-
-func (b *inMemoryBudget) CanAfford(amount float64, currency string) bool {
- b.mu.Lock()
- defer b.mu.Unlock()
- // A budget counts amounts in its own currency. This version of the protocol
- // defines no currency conversion.
- return (b.current.spent + amount) <= b.current.limit
-}
-```
-
-## Batch Selection and Recording Spend
-
-For batch (multi-URI) queries, the selection engine sums the prices of the offers it selects. If the total exceeds the remaining budget, it drops lower-priority URIs until the total fits (see the [Selection Engine](/components/broker/selection-engine/) batch pipeline). This is still filtering: nothing is reserved by `Resolve`.
-
-In this design, spend is recorded when a purchase completes: for a purchase through the Broker, the Broker adds each entry of `BrokerTransactionResponse.totals` (one `Cost` per currency, covering only the charged items) to the budget of the same currency.
-
-```go
-func (b *inMemoryBudget) RecordPurchase(ctx context.Context, totals []*forav1.Cost) {
- b.mu.Lock()
- defer b.mu.Unlock()
- for _, t := range totals {
- if t.Currency != b.current.currency {
- continue // amounts are never converted between currencies
- }
- b.current.spent += t.Amount
- }
- b.current.txnCount++
- b.current.lastTxn = time.Now()
-}
-```
-
-## Overspend Prevention
-
-The Broker applies the budget while it selects offers, before it returns them. An offer the agent cannot afford is never returned, so the agent never holds it to buy.
-
-### Budget Exhaustion Mid-Session
-
-When the session or period budget leaves no affordable offer for a URI:
-
-1. `Resolve` still returns OK. That URI's `OfferGroup` carries no offers and `absence_reason: OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`; when no URI has an affordable offer, `DiscoveryResponse.absence_reason` is `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`.
-2. It is not an error. The Broker never answers with `RESOURCE_EXHAUSTED` or `NOT_AUTHORIZED` for a budget.
-3. The agent can re-declare a higher budget, or buy directly from an Exchange without the Broker.
-
-```go
-price := budgetPrice(offer.Pricing) // the Broker's own choice of price
-if !budget.CanAfford(price, offer.Pricing.Currency) {
- // Drop the offer. If none remains for this URI, answer it with
- // OFFER_ABSENCE_REASON_BUDGET_EXCEEDED. Nothing is charged.
- continue
-}
-```
-
-## Ephemeral vs. Persisted Budget State
-
-Session budget state is ephemeral. If the Broker crashes, the agent re-declares its budget on reconnect. Per-period budgets (monthly, daily) are persisted in Redis and survive restarts.
-
-This is a deliberate design choice: the Exchange's billing adapter is the authoritative source of truth for "can this requester afford this transaction," not the Broker.
-
-## Currencies
-
-Currency conversion is out of scope for this version of the protocol. A budget is stated in one currency (`period_budget.currency`), and only amounts in that currency count against it. Purchase totals are never summed across currencies: `BrokerTransactionResponse.totals` carries one entry per currency, and `TransactionResponse.total_cost` is unset when the purchased items span more than one currency.
-
-## Budget Consistency at Scale
-
-The Broker's budget is a filter over the offers it returns, not a reservation. The Exchange is the authoritative point for what is charged, and denies an item, in the body, if the requester's balance is insufficient. This means:
-
-- If two Broker instances both return an offer the budget still allows, and the agent buys both, the spend can pass the budget by the price of the second purchase. Each purchase's totals are recorded when it completes, and later resolves filter against the new spend.
-- The Exchange's balance check still bounds what the requester can be charged.
-- The Broker's budget filter keeps the agent from buying what its budget does not allow; it is not a guarantee across concurrent purchases.
-
-This model is deliberately simple. Distributed budget consensus (e.g., two-phase commit across Broker instances) adds latency and complexity without value, because the Exchange already provides the authoritative enforcement.
-
-## Budget Reporting Metrics
-
-```go
-var (
- // Budget utilization per session
- budgetUtilization = promauto.NewHistogram(
- prometheus.HistogramOpts{
- Name: "broker_budget_utilization_ratio",
- Help: "Fraction of session budget spent (0.0 to 1.0+)",
- Buckets: []float64{0.0, 0.1, 0.25, 0.5, 0.75, 0.9, 1.0},
- },
- )
-
- // Budget exhaustion events
- budgetExhausted = promauto.NewCounter(
- prometheus.CounterOpts{
- Name: "broker_budget_exhausted_total",
- Help: "Number of URIs answered with BUDGET_EXCEEDED because the budget left no offer",
- },
- )
-)
-```
diff --git a/website/src/content/docs/components/broker/content-dedup.mdx b/website/src/content/docs/components/broker/content-dedup.mdx
deleted file mode 100644
index f47bd46a..00000000
--- a/website/src/content/docs/components/broker/content-dedup.mdx
+++ /dev/null
@@ -1,165 +0,0 @@
----
-title: "Content Deduplication"
-description: "How the Broker groups identical content offered by multiple Exchanges using ResourceIdentity matching, SimHash comparison, and canonical URL grouping."
----
-
-## Purpose
-
-The same resource can appear on multiple Exchanges. An AP wire story might be available from Exchange A and Exchange B. A syndicated article might be offered by the original provider's Exchange and a resource aggregator. The Broker groups these offers, so that for each unique resource the agent sees every offer together, each as the full package its Exchange signed, and decides which one it buys.
-
-## ResourceIdentity Matching
-
-Each Offer carries an optional `ResourceIdentity` that the Broker uses for deduplication. The identity key is derived from a priority-ordered set of fields:
-
-```go
-// contentIdentityKey produces a deduplication key from layered identity fields.
-// Matching priority: iptc_guid > doi > content_hash > canonical_url
-func contentIdentityKey(id *forav1.ResourceIdentity) string {
- if id == nil {
- return uuid.NewString() // no identity = unique (no dedup)
- }
- if id.IptcGuid != nil && *id.IptcGuid != "" {
- return "iptc:" + *id.IptcGuid
- }
- if id.Doi != nil && *id.Doi != "" {
- return "doi:" + *id.Doi
- }
- if id.ContentHash != nil && *id.ContentHash != "" {
- return "hash:" + *id.ContentHash
- }
- if id.CanonicalUrl != nil && *id.CanonicalUrl != "" {
- return "url:" + *id.CanonicalUrl
- }
- return uuid.NewString()
-}
-```
-
-### Identity Field Priority
-
-| Priority | Field | Description | Example |
-|---|---|---|---|
-| 1 (highest) | `iptc_guid` | IPTC globally unique identifier for news content | `urn:newsml:apnews.com:20260315:article-123` |
-| 2 | `doi` | Digital Object Identifier for academic/scientific content | `10.1038/s41586-026-01234-5` |
-| 3 | `content_hash` | Content fingerprint (method depends on hash_method: simhash-v1 for fuzzy dedup, sha256 for exact match) | `sha256:abc123...` |
-| 4 (lowest) | `canonical_url` | Canonical URL of the content | `https://apnews.com/article/ai-regulation` |
-
-When no `ResourceIdentity` is present on an offer, the offer is treated as unique and is never deduplicated. This is the conservative default -- it is better to pay twice for the same content than to accidentally merge two different articles.
-
-## SimHash Comparison
-
-For content available from multiple sources that may have minor editorial differences (e.g., AP wire stories republished with small modifications), strict hash matching (`content_hash`) may miss duplicates. The Broker supports SimHash comparison for fuzzy matching:
-
-- **Level 2 verification** uses SHA-256 exact hash -- content is byte-for-byte identical
-- **Level 1 verification** uses SimHash similarity -- content is structurally similar (e.g., 95%+ similarity)
-- **Level 0** -- no content verification
-
-SimHash comparison is applied when:
-
-1. Two offers share the same `canonical_url` but have different `content_hash` values
-2. Two offers from different Exchanges reference the same article by title/author metadata but have no shared identifier
-
-The SimHash comparison operates on the content identity metadata provided by the Exchange, not on the content itself (which is not yet fetched at selection time).
-
-## Canonical URL Grouping
-
-When higher-priority identifiers are not available, the Broker falls back to `canonical_url` grouping. This catches the common case where the same article is offered by multiple Exchanges that all reference the same provider URL.
-
-Canonical URL matching is exact string comparison after normalization:
-
-- Strip trailing slashes
-- Lowercase the hostname
-- Sort query parameters
-- Remove tracking parameters (utm_*, ref, etc.)
-
-## Cross-Exchange Dedup Strategy
-
-The full deduplication pipeline operates across all Exchange responses:
-
-```go
-type contentGroup struct {
- Key string
- Offers []rankedOffer
-}
-
-// groupOffers collects the offers for the same content into one group. It
-// keeps every offer: the agent sees all of them, in the Broker's order of
-// relevance, and chooses.
-func groupOffers(offers []rankedOffer) []contentGroup {
- index := make(map[string]int)
- var groups []contentGroup
-
- for _, o := range offers {
- key := contentIdentityKey(o.Offer.Identity)
- i, ok := index[key]
- if !ok {
- i = len(groups)
- index[key] = i
- groups = append(groups, contentGroup{Key: key})
- }
- groups[i].Offers = append(groups[i].Offers, o)
- }
- return groups
-}
-```
-
-### How It Works
-
-1. **Collect offers** from all Exchange responses.
-2. **Compute identity key** for each offer using the priority-ordered fields.
-3. **Group offers** by identity key. Offers with the same key are the same content.
-4. **Keep every offer** in its group. The [Selection Engine](/components/broker/selection-engine/) puts the offers in the Broker's order of relevance, and price is not part of that order.
-5. **The agent decides.** It sees which offers are the same content, compares the packages (terms, brand, attestations and price), and chooses the one it buys.
-
-### Example
-
-An agent requests content at `https://apnews.com/article/ai-regulation`. Two Exchanges respond:
-
-| Exchange | Offer ID | unit_cost | ResourceIdentity |
-|---|---|---|---|
-| Exchange Alpha | offer-a1 | $0.0003/token | `iptc:urn:newsml:apnews.com:20260315:ai-reg` |
-| Exchange Beta | offer-b1 | $0.0005/token | `iptc:urn:newsml:apnews.com:20260315:ai-reg` |
-
-Both offers share the same `iptc_guid`. The Broker groups them and returns both, in its order of relevance. The agent sees that they are the same story, compares the two packages and decides. An agent whose own policy is to pay less per unit buys `offer-a1` at $0.0003/token; that choice is the agent's, not the Broker's.
-
-## Deduplication in Batch Queries
-
-For batch (multi-URI) queries, deduplication runs per URI. Each URI's offers are deduplicated independently:
-
-1. For each URI in the batch, collect all offers from all Exchange responses that match that URI.
-2. Within each URI's offer set, run the standard deduplication pipeline.
-3. Return every offer per URI after grouping, in the Broker's order of relevance.
-
-Cross-URI grouping (e.g., "the agent requested two URLs that happen to be the same article") uses the same identity key. Each URI keeps its own `OfferGroup`, and the shared `ResourceIdentity` on the offers tells the agent that the two URLs are the same content, so it need not buy it twice.
-
-## Deduplication Metrics
-
-The Broker tracks deduplication effectiveness through Prometheus metrics:
-
-```go
-var (
- // How often deduplication found the same content from multiple Exchanges
- deduplicationRate = promauto.NewHistogram(
- prometheus.HistogramOpts{
- Name: "broker_dedup_sets",
- Help: "Number of content groups with offers from multiple Exchanges",
- Buckets: []float64{0, 1, 2, 3, 5, 10},
- },
- )
-)
-```
-
-The `SelectionRationale` recorded with every answer includes `SameContentGroups` -- the count of content groups that had offers from multiple Exchanges. This shows how often the same content comes from more than one Exchange.
-
-## Content Attestation Levels (v1.0)
-
-In v1.0, content attestation level replaces the former content verification concept. Attestation level is one of the signals in the Broker's order of relevance:
-
-| Level | Attestation | Guarantee |
-|---|---|---|
-| 0 | None | No attestation. Content may carry identifiers (DOI, IPTC GUID) for dedup, but nothing is cryptographically verifiable. |
-| 1 | Self-attested (provider) | Provider signed claims with Ed25519. Agent can recompute content hash from delivered bytes. |
-| 2 | Third-party (verification vendor) | Independent verification. Vendor crawled and measured the content. Agent trusts the attestation without re-verifying. |
-
-Higher attestation levels rank higher in the [Selection Engine](/components/broker/selection-engine/)'s order because they provide stronger guarantees: a higher level enables automated dispute resolution and reduces the risk of receiving content that does not match what was advertised. When two offers for the same content have different attestation levels, the Broker returns both, and the agent weighs the attestation against the price by its own policy.
-
-Content identifiers (DOI, ISBN, IPTC GUID) used for deduplication are orthogonal to attestation level. A Level 0 article may carry a DOI -- that identifies WHAT content it is but does NOT verify that the delivered bytes match the identified content.
diff --git a/website/src/content/docs/components/broker/deployment.mdx b/website/src/content/docs/components/broker/deployment.mdx
deleted file mode 100644
index bcafee78..00000000
--- a/website/src/content/docs/components/broker/deployment.mdx
+++ /dev/null
@@ -1,338 +0,0 @@
----
-title: "Broker Deployment"
-description: "Deployment models, configuration reference, caching strategy, failure modes, and scaling considerations for the FORA Broker."
----
-
-import DeferredSdkNotice from '../../../../components/DeferredSdkNotice.mdx';
-
-
-
-## Deployment Models
-
-The Broker is designed for three deployment modes. The core logic (selection, budget) is identical across all three; what changes is the process model, configuration surface, and what the agent is responsible for.
-
-```mermaid
-graph LR
- subgraph "Model A: Agent SDK (embedded library)"
- AgentSDK[AI Agent + FORA SDK] --> MPAS[Exchanges]
- end
-
- subgraph "Model B: Sidecar Binary"
- AgentA[AI Agent] -->|localhost:9090| SidecarA[Broker Go binary]
- SidecarA --> MPA[Exchanges]
- end
-
- subgraph "Model C: Hosted SaaS"
- AgentC1[Agent 1] --> Hosted[Broker SaaS multi-tenant]
- AgentC2[Agent 2] --> Hosted
- Hosted --> MPC[Exchanges]
- end
-```
-
-### Model Comparison
-
-| Aspect | Agent SDK | Sidecar Binary | Hosted SaaS |
-|---|---|---|---|
-| **Process model** | In-process library | Separate process, same host | Remote service, separate infra |
-| **Language** | Go / TypeScript / Python | Go binary | Go service |
-| **Communication** | Function calls | Connect RPC over localhost | Connect RPC over HTTPS |
-| **Budget state** | In-process memory + local file | In sidecar memory | Server-side, per-tenant |
-| **Configuration** | Struct literal in code | YAML file + env vars | API |
-| **Multi-tenancy** | N/A (one license per instance) | N/A (one agent per sidecar) | Required -- session isolation |
-| **Latency overhead** | 0ms (in-process) | ~1ms (localhost RPC) | ~5-20ms (network hop) |
-| **Content fetch** | SDK fetches signed URL | Agent fetches signed URL | Agent fetches signed URL |
-| **Usage reporting** | The SDK files it in the background, signed with the agent's key | The agent files it with the issuing Exchange | The agent files it with the issuing Exchange |
-| **Who operates** | Agent developer | Agent operator | Broker SaaS provider |
-
-### Recommended Deployment
-
-**For agent developers (lowest friction)**: Ship the [Agent SDK](/components/agent-sdk/overview/). Agent developers add one dependency, pass their license key and budget, and call `Fetch`. No sidecar, no YAML, no infrastructure.
-
-**For agent operators (clear process boundary)**: Ship the sidecar binary. Operators run it alongside their agent, configure via YAML, and get multi-exchange comparison without code changes.
-
-**At scale (managed service)**: Offer hosted SaaS for teams that don't want to operate infrastructure. Multi-tenancy enables serving multiple AI companies from a single deployment.
-
-### Sidecar Binary
-
-```go
-func main() {
- cfg := loadConfig("broker.yaml")
- orch := broker.New(cfg)
-
- mux := http.NewServeMux()
- path, handler := forav1connect.NewBrokerServiceHandler(orch)
- mux.Handle(path, handler)
-
- http.ListenAndServe("localhost:9090", mux)
-}
-```
-
-### Hosted SaaS (Multi-Tenancy)
-
-The hosted Broker serves multiple AI companies. Tenant isolation is by API key or the verified agent identity (domain/key). Each tenant gets isolated: Exchange registry (different trust levels per tenant), budget tracking (per-tenant Redis keyspace), selection policy (per-tenant configuration), and selection logs.
-
-```go
-func main() {
- tenantStore := loadTenantStore()
-
- handler := &multiTenantBroker{
- tenants: tenantStore,
- }
-
- mux := http.NewServeMux()
- path, h := forav1connect.NewBrokerServiceHandler(handler)
- mux.Handle(path, authMiddleware(h))
-
- http.ListenAndServe(":443", mux)
-}
-
-func (m *multiTenantBroker) Resolve(
- ctx context.Context,
- req *connect.Request[forav1.DiscoveryRequest],
-) (*connect.Response[forav1.DiscoveryResponse], error) {
- tenantID := tenantFromContext(ctx)
- orch := m.tenants.GetBroker(tenantID)
- return orch.Resolve(ctx, req)
-}
-```
-
-### What Changes Between Modes
-
-The core interfaces (`ExchangeRegistry`, `SelectionEngine`, `BudgetTracker`) are identical. What changes is persistence strategy, configuration surface, and process lifecycle.
-
-## Configuration Reference
-
-```yaml
-# broker.yaml -- full configuration reference
-
-# Protocol version
-version: "1.0"
-
-# Exchange registry
-exchanges:
- - domain: exchange.ssp-alpha.com
- endpoint: https://exchange.ssp-alpha.com/fora/v1
- trust: verified
- priority: 1
- - domain: exchange.ssp-beta.com
- endpoint: https://exchange.ssp-beta.com/fora/v1
- trust: verified
- priority: 2
-
-# fora.json crawling (automated discovery)
-discovery:
- enabled: true
- domains:
- - techcrunch.com
- - nytimes.com
- - apnews.com
- interval: 1h
- # Trust level for auto-discovered Exchanges
- default_trust: discovered
-
-# Parallel fanout
-fanout:
- timeout: 60ms # Overall fanout deadline
- per_exchange_timeout: 50ms
- max_concurrency: 20 # Max concurrent DiscoverResources RPCs
-
-# Selection engine
-selection:
- policy: relevance # relevance | preferred_exchange | freshness_weighted | quality_score
- verify_signatures: true # Verify exchange_signature on offers
-
-# Budget defaults (overridden per-session by DiscoveryRequest)
-budget:
- default_session_limit: 1.00
- default_currency: USD
-
-# Caching
-cache:
- fora_json_ttl: 1h
- exchange_health_ttl: 30s
- supply_response_ttl: 0s # Disabled by default
-
-# HTTP client
-http:
- tls_min_version: "1.3"
- idle_conn_timeout: 90s
- max_idle_conns_per_host: 10
-
-# Server (sidecar mode only)
-server:
- address: "localhost:9090"
- # No TLS for localhost sidecar. Add TLS config for network-exposed deployments.
-
-# Metrics
-metrics:
- enabled: true
- address: ":9091" # Prometheus metrics endpoint
-```
-
-## Exchange Registry
-
-The registry maintains a live list of known Exchanges, their endpoints, health status, and trust level.
-
-### Discovery Sources
-
-```mermaid
-graph LR
- subgraph "Discovery Sources"
- Manual[Manual Config YAML / env vars]
- ParseJSON[fora.json Crawling provider domains]
- OnDemand[Background Discovery on first request]
- Peer[Peer Exchange future]
- end
-
- Manual --> Registry
- ParseJSON --> Registry
- OnDemand --> Registry
- Peer -.-> Registry
-
- Registry[Exchange Registry unified view]
-```
-
-**Source 1: Manual configuration.** YAML file or environment variables listing known Exchange endpoints.
-
-**Source 2: fora.json crawling.** The Broker periodically crawls `/.well-known/fora.json` from provider domains to discover authorized Exchanges.
-
-**Source 3: Background discovery on first request.** When the agent requests a URI for an unknown domain, the Broker background-crawls that domain's fora.json. The current request is NOT blocked.
-
-**Source 4: Peer exchange (future).** Not designed for v1.
-
-### Trust Model
-
-| Trust Level | How Achieved | Allowed Operations |
-|---|---|---|
-| `discovered` | Found in a fora.json | DiscoverResources only |
-| `verified` | Operator has reviewed and approved | DiscoverResources + ExecuteTransaction |
-| `preferred` | Operator has marked as preferred | All operations + priority in selection |
-| `blocked` | Operator has explicitly blocked | No operations |
-
-An attacker who poisons a provider's fora.json would only gain `discovered` trust, which allows supply queries but not financial transactions. The operator must explicitly promote to `verified` before the Broker will spend money there.
-
-### Refresh Strategy
-
-| Data | Refresh Interval | Mechanism |
-|---|---|---|
-| Manual config | On startup + SIGHUP | File watch or signal handler |
-| fora.json per domain | 1 hour (configurable) | Background goroutine |
-| Exchange health | Every 30 seconds | Background check: a fresh fetch of the Exchange's `fora.json`, then a GET of the `health_endpoint` it names (200 means serving); with none named, the successful manifest fetch is the answer |
-| Trust levels | Manual only | Operator action via API or config |
-
-### Registry Interface
-
-```go
-type ExchangeRegistry interface {
- Resolve(constraints *forav1.RequestConstraints) []ExchangeEntry
- ResolveAll() []ExchangeEntry
- Register(entry ExchangeEntry)
- UpdateHealth(domain string, status HealthStatus)
- SetTrust(domain string, trust TrustLevel) error
-}
-```
-
-## Caching Strategy
-
-### Cache Layers
-
-```mermaid
-graph TB
- subgraph "Broker Caches"
- C1[fora.json Cache per provider domain TTL: 1 hour]
- C2[Exchange Health Cache per exchange TTL: 30 seconds]
- C3[ResourceResponse Cache per query fingerprint TTL: 5 seconds]
- end
-```
-
-| Cache | Key | TTL | Rationale |
-|---|---|---|---|
-| **fora.json** | Provider domain | 1 hour | fora.json changes rarely. Matches `max-age` from the provider's HTTP cache headers if present. |
-| **Exchange health** | Exchange domain | 30 seconds | Health can change rapidly. 30s balances freshness with probe cost. |
-| **ResourceResponse** | SHA-256 of (exchange + aisystem.name + uri list) | 5 seconds max | Only useful when multiple requests for the same content arrive in a burst. Set to 0 to disable. |
-| **Exchange public keys** | Exchange domain | 24 hours | Public keys for offer signature verification. Rotate slowly (90-day cycle). |
-
-Most caches are in-memory LRU. Redis is used only for shared state (per-period budget persistence) in multi-instance deployments.
-
-### ResourceResponse Caching
-
-ResourceResponse caching is disabled by default. Enable it only when:
-
-- The agent makes rapid successive requests for the same content (burst pattern)
-- The Broker is in hosted SaaS mode and multiple agents request the same content
-
-Even with caching enabled, 5 seconds is the maximum TTL. Offers can include `expires_at` timestamps; the cache respects these.
-
-## Failure Modes
-
-### Failure Taxonomy
-
-```mermaid
-graph TD
- F1[All Exchanges Timeout] -->|Result| R1[Return error to agent agent can retry or go direct]
- F2[Preferred Exchange Down] -->|Result| R2[Fallback to remaining Exchanges automatically]
- F3[Broker Crash Mid-Transaction] -->|Result| R3[Agent retries with same idempotency key, on any route]
- F4[Budget Tracking Lost on Crash] -->|Result| R4[Agent re-declares budget Exchange is authoritative]
- F5[Partial Exchange Failures] -->|Result| R5[Proceed with partial results, best-effort]
-```
-
-### Detailed Failure Handling
-
-**All Exchanges timeout.** The Broker returns a Connect error with code `UNAVAILABLE`. The agent can retry, query Exchanges directly, or fall back to non-FORA content access.
-
-**Preferred Exchange down.** The registry marks it as unhealthy. The selection engine orders the offers from whatever responded. No special handling needed.
-
-**Broker crash mid-transaction.**
-
-| Crash Point | Impact | Recovery |
-|---|---|---|
-| Before ExecuteTransaction sent | No financial impact | Agent retries the full request |
-| After ExecuteTransaction sent, before response | Exchange has charged but agent doesn't know | Agent retries with the same `TransactionRequest.idempotency_key`, through this Broker once it is back, another Broker or directly -- each Exchange returns the same response (idempotency) |
-| After TransactionResponse returned | Agent has the signed URL | Agent tracks its reporting obligations and files its own reports |
-
-**Budget tracking lost on crash.** Session budget is ephemeral. The agent re-declares on reconnect. The Exchange's billing adapter is the authoritative source.
-
-**Partial Exchange failures.** This is the normal case. Metrics record which Exchanges failed.
-
-### Idempotency
-
-The Broker never generates `TransactionRequest.idempotency_key`. The key is the agent's, and the Broker forwards it unchanged on every sub-request: it cannot do otherwise, because each `AgentAcceptance` and the `AgentRequestAcceptance` sign it.
-
-Each Exchange scopes the key to the agent, whatever the route, so two agents behind one Broker that choose the same key do not collide. When the agent retries the same purchase with the same key, through this Broker, another one or directly, each Exchange recognizes a replay of its sub-request and answers from its stored result. When a key is reused with different items, or the same items in another order, the Exchange refuses the sub-request with `already_exists`, and the Broker reports that refusal on each affected item's `refusal`.
-
-## Scaling Considerations
-
-### Security Considerations
-
-| Threat | Attack | Countermeasure |
-|---|---|---|
-| **T19**: Hidden orchestration fee | Broker adds markup to relayed offers | Signed offers passed through. Agent verifies signature. Any fee is disclosed separately. |
-| **T20**: Kickback-driven selection | Broker has side deal with an Exchange | Selection rationale logged. Agent can spot-check by querying directly. |
-| **T21**: Query intelligence harvesting | Broker logs queries and sells data | Data processing agreements. In sidecar mode, agent operator controls the Broker. |
-
-### TLS Requirements
-
-All Exchange communication uses TLS 1.3 minimum. The Broker's HTTP clients are configured with `tls.Config{MinVersion: tls.VersionTLS13}`.
-
-### Exchange Public Keys
-
-The Broker fetches the Exchange's offer-signing keys from its WBA directory (the JWK Set at `/.well-known/http-message-signatures-directory`). Public keys are cached in Redis with a 24-hour TTL. On signature verification failure, the cache is refreshed before retrying.
-
-Key rotation: Exchanges SHOULD publish both current and previous keys during a rotation window (recommended: 7 days).
-
-### Metrics
-
-The Broker exposes Prometheus-compatible metrics at `/metrics`:
-
-| Metric | Type | Description |
-|---|---|---|
-| `broker_exchange_latency_seconds` | Histogram | DiscoverResources response time per Exchange |
-| `broker_exchange_health` | Gauge | Health status (0=down, 1=degraded, 2=healthy) |
-| `broker_exchange_offer_count` | Histogram | Offers per DiscoverResources response |
-| `broker_selection_offers_total` | Counter | Offers at each pipeline stage |
-| `broker_dedup_sets` | Histogram | Content groups with multiple offers |
-| `broker_offers_returned` | Histogram | Offers returned per URI, in the Broker's order |
-| `broker_budget_utilization_ratio` | Histogram | Session budget utilization |
-| `broker_budget_exhausted_total` | Counter | URIs answered with `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED` because the budget left no offer |
-| `broker_request_latency_seconds` | Histogram | Total DiscoveryRequest handling time |
-| `broker_requests_total` | Counter | Total DiscoveryRequests handled |
diff --git a/website/src/content/docs/components/broker/overview.mdx b/website/src/content/docs/components/broker/overview.mdx
index fa466b22..1319e076 100644
--- a/website/src/content/docs/components/broker/overview.mdx
+++ b/website/src/content/docs/components/broker/overview.mdx
@@ -92,6 +92,16 @@ When at least one URL has an offer, every requested URL comes back as one `Offer
When no URL has an offer, or no publisher's `fora.json` can be read, the response carries no groups and states the reason once, in `DiscoveryResponse.absence_reason`. "No offer" is a successful answer, not an error: `BrokerService.Resolve` returns OK with the reason.
+## Order, budget and fees
+
+**Order.** A Broker returns the offers in its own order of relevance to the agent's request. Price is not a signal of that order: each offer carries its price and `Pricing.unit_cost`, and the agent compares them under its own policy. An agent names the Exchanges it has a relationship with, such as a subscription, in `RequestConstraints.preferred_exchanges`, and a Broker SHOULD put their offers first when they have the resource.
+
+**Same content, several Exchanges.** When several Exchanges sell the same content, the agent gets each offer as a full package, and `Offer.identity` tells it that they are the same content. A Broker groups such offers and drops none of them, so the agent compares the packages and decides which to buy.
+
+**Budget.** The agent's budget is its own constraint. The limits it states in `DiscoveryRequest.constraints`, such as `max_price` or `period_budget` with `budget_period`, narrow which offers come back, and a Broker applies them as a filter, not as an order. A URL the budget leaves with no offer is answered with `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`. The charge is the Exchange's, at purchase.
+
+**Fees.** An offer carries only the Exchange's price, which the Exchange signed. A Broker's fee has no field: it is disclosed out of band and added to that price, never folded into it.
+
## Buying through the Broker
An agent commits to offers in a separate call, one of two ways. The execute target of each offer is `Offer.exchange`, which the Exchange signed, so a Broker cannot redirect a purchase.
@@ -146,9 +156,16 @@ The Broker forwards `Requester.scopes` unchanged and in order, because the Excha
Anyone may run a Broker, with or without an Exchange of their own. It is a role of its own, with its own key and its own `fora.json`, and each Exchange decides which Brokers it admits. A search company, for example, can run only a Broker, behind its own search.
-FORA Server's Broker is a separate service. It needs PostgreSQL, Redis, a public hostname with TLS, and a registry that lists the Exchanges its operator trusts. The address of each Exchange always comes from that Exchange's own `fora.json`, never from the registry. The [deployment guide](https://github.com/FORA-Protocol/reference-implementation/blob/main/src/broker/DEPLOYMENT.md) is in the FORA Server repository.
+FORA Server's Broker is a separate service, published as the container image `ghcr.io/fora-protocol/broker`. Its operator deploys it with:
+
+- PostgreSQL, Redis, and a public hostname with TLS;
+- two Ed25519 keys: an identity key, whose public half the Broker publishes in its key directory, and a relay key, which signs the Broker's requests to Exchanges;
+- a registry file that lists the Exchanges it routes to, each with a `trust_level`: `DISCOVERED` Exchanges answer discovery and are never paid, `VERIFIED` and `PREFERRED` ones also take purchases, and `BLOCKED` ones take neither;
+- a withdrawn-keys file, which the Broker publishes. A FORA Server Exchange is configured with one Broker (`EXCHANGE_BROKER_WELLKNOWN_URL`) and rejects signed requests while it can't read that Broker's list, so the Broker goes up first.
+
+The address of each Exchange always comes from that Exchange's own `fora.json`, never from the registry. The [deployment guide](https://github.com/FORA-Protocol/reference-implementation/blob/main/src/broker/DEPLOYMENT.md) is in the FORA Server repository.
-As of November 2026, Gutefrage runs the whole FORA stack itself, on its own servers, and has launched it on [helpster.de](https://www.helpster.de/), one of its properties. Its Broker searches the Elasticsearch index Gutefrage already runs, with a search template in which Gutefrage decides which fields are searched, how results rank and which filters agents may use.
+Gutefrage runs the whole FORA stack itself, on its own servers, and has launched it on [helpster.de](https://www.helpster.de/), one of its properties. Its Broker searches the Elasticsearch index Gutefrage already runs, with a search template in which Gutefrage decides which fields are searched, how results rank and which filters agents may use.
## Related pages
diff --git a/website/src/content/docs/components/broker/selection-engine.mdx b/website/src/content/docs/components/broker/selection-engine.mdx
deleted file mode 100644
index d1d6e06f..00000000
--- a/website/src/content/docs/components/broker/selection-engine.mdx
+++ /dev/null
@@ -1,549 +0,0 @@
----
-title: "Selection Engine"
-description: "How the Broker collects offers from Exchanges, narrows them to the agent's constraints, groups offers for the same content, and returns them in its order of relevance for the agent to choose from."
----
-
-## Purpose
-
-The Selection Engine turns the offers that Exchanges return into the answer the agent gets. It collects the offers, narrows them to the constraints the agent set, groups offers for the same content, and puts them in the Broker's order of relevance to the request.
-
-The Selection Engine does not choose for the agent. The agent decides what it buys, where and why. Each offer reaches the agent as a full package, with its terms, brand, attestations and price, exactly as its Exchange signed it, and the Broker can't change one. The Broker's rules for its order are public, so an agent can inspect why each offer is where it is.
-
-The Broker is a convenience layer. It never buys or resells under an account of its own: when the agent buys through it, each Exchange charges the agent's account.
-
-### Discovery-Mode Agnostic
-
-The Selection Engine operates on offers, not on how those offers were discovered. Whether the agent sent specific URIs (`DiscoveryRequest.uris`), structured search filters (`DiscoveryRequest.search_filters`), or a natural-language query (`DiscoveryRequest.query`), the Broker resolves all three into a set of offers from Exchanges. The Selection Engine then applies the same pipeline -- filter, group, order, verify -- to every offer identically.
-
-This means the selection logic does not need to know or care about discovery mode. An offer discovered via structured search is treated the same as an offer from a specific URI request. The `OfferGroup.discovery_method` field records how each offer was found (for transparency and logging), but it does not influence the order.
-
-## Multi-Exchange Query Fanout
-
-The core value proposition of the Broker is parallel supply discovery. The Broker fans out `DiscoverResources` to N Exchanges concurrently, collecting their offers for the agent.
-
-### Concurrency Model
-
-Uses `errgroup.Group` with a semaphore for bounded concurrency and `context.WithTimeout` for per-Exchange deadlines. When the `DiscoveryRequest` contains multiple URIs, the Broker sends all URIs in a single `ResourceQuery` to each Exchange (not one query per URI). The Exchange returns `OfferGroups` -- one per URI -- so the Broker knows which offers map to which content.
-
-```go
-func (d *Discovery) FanOut(
- ctx context.Context,
- exchanges []ExchangeEntry,
- req *forav1.DiscoveryRequest,
-) []FanOutResult {
-
- // Hard deadline: don't wait longer than this for any Exchange.
- ctx, cancel := context.WithTimeout(ctx, d.fanoutTimeout) // default: 60ms (p99 target)
- defer cancel()
-
- results := make([]FanOutResult, len(exchanges))
- g, gctx := errgroup.WithContext(ctx)
- g.SetLimit(d.maxConcurrency) // default: 20
-
- for i, mp := range exchanges {
- i, mp := i, mp
- g.Go(func() error {
- query := toResourceQuery(req, mp) // includes all req.Uris
- start := time.Now()
-
- resp, err := d.clients[mp.Domain].DiscoverResources(gctx, connect.NewRequest(query))
-
- results[i] = FanOutResult{
- Exchange: mp,
- Response: resp,
- Err: err,
- Latency: time.Since(start),
- }
-
- // Don't return error -- we want partial results, not all-or-nothing.
- return nil
- })
- }
-
- g.Wait()
- return results
-}
-```
-
-### Time Budget in ResourceQuery
-
-`ResourceQuery` carries an optional `deadline` field (default: 500ms). This informs the Exchange how much time the agent has allocated for the entire discovery phase. Exchanges SHOULD prioritize speed when the deadline is tight.
-
-```go
-func (d *Discovery) perExchangeDeadline(mp ExchangeEntry, requestDeadline time.Duration) time.Duration {
- p99 := d.latencyTracker.P99(mp.Domain)
- if p99 == 0 {
- return requestDeadline // no history, use full budget
- }
- // Allow 2x historical p99, capped at request deadline
- budget := min(p99*2, requestDeadline)
- return budget
-}
-```
-
-### Timeout Handling
-
-Three timeout layers, each independently enforced:
-
-```mermaid
-graph TD
- subgraph "Timeout Layers"
- T1["Layer 1: Per-Exchange context.WithTimeout per goroutine default: 50ms"]
- T2["Layer 2: Fanout deadline context.WithTimeout on errgroup default: 60ms"]
- T3["Layer 3: Request deadline agent's context deadline forwarded from DiscoveryRequest"]
- end
-
- T3 -->|cancels| T2
- T2 -->|cancels| T1
-```
-
-| Layer | Default | Purpose |
-|---|---|---|
-| Per-Exchange | 50ms | Individual slow Exchange doesn't block others |
-| Fanout deadline | 60ms | Overall discovery phase has a hard cap |
-| Request deadline | From agent's context | Agent controls the total request timeout |
-
-**Partial results are normal.** If 3 of 5 Exchanges respond within the deadline, the Broker proceeds with 3 responses. Timed-out Exchanges are recorded in metrics and their health status is degraded.
-
-### Client Pool
-
-Pre-established HTTP/2 connections to each Exchange. Connect-Go clients are created at startup and reused.
-
-```go
-type ClientPool struct {
- mu sync.RWMutex
- clients map[string]forav1connect.ExchangeServiceClient
- signer helpers.Signer // the Broker's own request-signing key
-}
-
-func (p *ClientPool) GetOrCreate(mp ExchangeEntry) forav1connect.ExchangeServiceClient {
- p.mu.RLock()
- if c, ok := p.clients[mp.Domain]; ok {
- p.mu.RUnlock()
- return c
- }
- p.mu.RUnlock()
-
- p.mu.Lock()
- defer p.mu.Unlock()
-
- // Double-check after acquiring write lock.
- if c, ok := p.clients[mp.Domain]; ok {
- return c
- }
-
- base := &http.Transport{
- MaxIdleConnsPerHost: 10,
- IdleConnTimeout: 90 * time.Second,
- ForceAttemptHTTP2: true,
- TLSClientConfig: &tls.Config{MinVersion: tls.VersionTLS13},
- }
- httpClient := &http.Client{
- // The Broker signs every request it sends alone, naming its own key
- // directory in its Signature-Agent member.
- Transport: core.NewSigningTransport(p.signer, base,
- core.WithSignatureAgent("https://broker.example")),
- Timeout: 5 * time.Second, // connection-level timeout
- }
-
- client := forav1connect.NewExchangeServiceClient(httpClient, mp.Endpoint)
- p.clients[mp.Domain] = client
- return client
-}
-```
-
-## Selection Pipeline
-
-### Single-URI Pipeline
-
-For single-URI queries, five stages are executed sequentially on the combined offer set:
-
-```mermaid
-graph LR
- A[Collect all Offers from N Exchanges] --> B[Narrow to the license kinds the agent asks for]
- B --> C[Filter by RequestConstraints]
- C --> D[Group by ResourceIdentity]
- D --> E[Order by relevance]
- E --> F[Verify exchange_signature]
- F --> G[Offers in order the agent chooses]
-```
-
-### Multi-URI Batch Pipeline
-
-For multi-URI batch queries, the engine runs the same pipeline for each URI and returns the ordered offers for every URI. The agent chooses an offer per URI and checks the total against its own budget.
-
-```mermaid
-graph LR
- A[Collect OfferGroups from N Exchanges] --> B[For each URI: merge offers across Exchanges]
- B --> C[Per URI: narrow, filter, group, order]
- C --> D[Return one OfferGroup per URI, offers in order]
- D --> E[Agent chooses per URI and checks its total]
-```
-
-The batch algorithm:
-
-1. For each URI, collect offers from all Exchange responses (flatten OfferGroups with matching URI).
-2. Within each URI, run the single-URI pipeline (narrow, filter, group, order, verify).
-3. Return one `OfferGroup` per URI, with its offers in the Broker's order. A URI whose offers the budget drops entirely is answered with `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED` on its `OfferGroup`.
-4. `Resolve` is discovery only: it charges nothing. The agent chooses the offers it buys and buys them in a separate call.
-
-### Selection Interface
-
-```go
-type SelectionEngine interface {
- // Select handles single-URI queries. Returns the offers in this Broker's
- // order of relevance. The agent chooses among them.
- Select(
- ctx context.Context,
- responses []FanOutResult,
- req *forav1.DiscoveryRequest,
- budget BudgetTracker,
- ) (*Selection, error)
-
- // SelectBatch handles multi-URI queries. Returns the ordered offers for
- // each URI, in request order.
- SelectBatch(
- ctx context.Context,
- responses []FanOutResult,
- req *forav1.DiscoveryRequest,
- budget BudgetTracker,
- ) (*BatchSelection, error)
-}
-
-type Selection struct {
- URI string
- Offers []OrderedOffer // most relevant first
- Rationale SelectionRationale
-}
-
-type OrderedOffer struct {
- Exchange ExchangeEntry
- Offer *forav1.Offer // unchanged, as the Exchange signed it
- Score float64
-}
-
-type BatchSelection struct {
- Selections []Selection // one per URI, in request order
- Rationale BatchSelectionRationale
-}
-
-type SelectionRationale struct {
- TotalOffers int
- WithinAcceptable int // offers inside the agent's acceptable_restrictions
- AfterConstraints int
- SameContentGroups int // content groups with offers from more than one Exchange
- RejectedReasons map[string]int // reason -> count
-}
-```
-
-## Stage 1: Narrow to the License Kinds the Agent Asks For
-
-Restrictions ride on the offer. Each offer's single `terms[0]` entry is a `LicenseTerm` carrying `repeated Restriction` (with kinds like `RESTRICTION_KIND_FUNCTION`, `RESTRICTION_KIND_GEOGRAPHY`, `RESTRICTION_KIND_USER_TYPE`). A resource licensed in two ways is two offers, one per term.
-
-The agent states the kinds of license it asks for in `DiscoveryRequest.acceptable_restrictions`, per restriction axis, and the Broker forwards them to each Exchange in `ResourceQuery.acceptable_restrictions`. As a convenience, an Exchange or a Broker MAY drop offers whose restrictions fall outside those limits (see [Term semantics](/protocol/licensing-terms/#term-semantics)). A URI left with no offer is answered with `OFFER_ABSENCE_REASON_RESTRICTION_FILTERED`, with the filtered axes in `OfferGroup.restriction_filters`. When the agent states no `acceptable_restrictions`, the Broker drops no offer on this ground.
-
-This narrowing is advisory, not enforcement. The Broker surfaces the restrictions carried on each offer's own term, and the agent chooses the offer whose restrictions it can honour and is responsible for complying with them. Real enforcement happens downstream at accept -> report -> reconcile. The function-token vocabulary is the hyphenated string form (`ai-train`, `ai-index`, `ai-input`, `crawl`, `search`, ...).
-
-```go
-// withinAcceptable reports whether an offer's term fits the functions the agent
-// stated in acceptable_restrictions. Only the FUNCTION axis is shown here. When
-// the agent stated no limits, every offer fits.
-func withinAcceptable(offer *forav1.Offer, acceptable []*forav1.AcceptableRestriction) bool {
- for _, a := range acceptable {
- if a.Axis != forav1.RestrictionKind_RESTRICTION_KIND_FUNCTION {
- continue // geography / user-type evaluated the same way, or left to the agent
- }
- for _, use := range a.Values {
- if !restrictionsHonoured(offer.Terms[0].Restrictions, use) {
- return false
- }
- }
- }
- return true
-}
-
-func restrictionsHonoured(restrictions []*forav1.Restriction, declaredFunction string) bool {
- for _, r := range restrictions {
- if r.Kind != forav1.RestrictionKind_RESTRICTION_KIND_FUNCTION {
- continue // geography / user-type evaluated by the agent against its own context
- }
- // If prohibited contains the declared function, this term cannot be honoured.
- for _, prohibited := range r.Prohibited {
- if prohibited == declaredFunction {
- return false
- }
- }
- // If permitted is non-empty, the declared function must be in it.
- if len(r.Permitted) > 0 {
- found := false
- for _, perm := range r.Permitted {
- if perm == declaredFunction {
- found = true
- break
- }
- }
- if !found {
- return false
- }
- }
- }
- return true
-}
-```
-
-## Stage 2: Filter by RequestConstraints
-
-The agent's `DiscoveryRequest.constraints` specifies budget and preference limits. These are the agent's own limits: a price cap or a budget is a constraint the agent sets, and the Broker applies it as a filter, not as an order.
-
-```go
-func filterByConstraints(offers []rankedOffer, c *forav1.RequestConstraints, budget BudgetTracker) []rankedOffer {
- var passed []rankedOffer
- for _, o := range offers {
- p := o.Offer.Pricing
-
- // The price this Broker counts against the budget. Which price that is
- // is the Broker's own choice; the protocol does not specify it.
- price := budgetPrice(p)
-
- // max_price: drop offers above it
- if c.MaxPrice != nil && price > c.MaxPrice.Amount {
- continue
- }
-
- // max_unit_cost: reject offers with unit_cost above threshold
- if c.MaxUnitCost != nil && p.UnitCost != nil && *p.UnitCost > *c.MaxUnitCost {
- continue
- }
-
- // reporting_capable: if agent can't report, skip offers that require it
- if c.ReportingCapable != nil && !*c.ReportingCapable {
- if o.Offer.Reporting != nil && o.Offer.Reporting.Required {
- continue
- }
- }
-
- // delivery_preference: filter by supported delivery methods
- if len(c.DeliveryPreference) > 0 {
- if !deliveryMethodAccepted(o.Offer.DeliveryMethod, c.DeliveryPreference) {
- continue
- }
- }
-
- // Period and session budget: drop the offer if buying it would take the
- // spend past the budget. This filter reserves nothing.
- if !budget.CanAfford(price, p.Currency) {
- continue
- }
-
- passed = append(passed, o)
- }
- return passed
-}
-```
-
-When the budget drops every offer for a URI, that URI is answered with `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`, a successful "no result". A budget is never reported as `OFFER_ABSENCE_REASON_NOT_AUTHORIZED`, and never as an error such as `RESOURCE_EXHAUSTED`.
-
-## Stage 3: Group by ResourceIdentity
-
-The same article may be offered by multiple Exchanges (e.g., an AP wire story available from Exchange A and Exchange B). The Broker groups these offers by resource identity and keeps every one of them. The agent sees each offer as a full package, in the Broker's order of relevance, and decides which one it buys. The Broker never keeps one offer of a group and drops the others.
-
-```go
-// contentIdentityKey produces a deduplication key from layered identity fields.
-// Matching priority: iptc_guid > doi > content_hash > canonical_url
-func contentIdentityKey(id *forav1.ResourceIdentity) string {
- if id == nil {
- return uuid.NewString() // no identity = unique (no dedup)
- }
- if id.IptcGuid != nil && *id.IptcGuid != "" {
- return "iptc:" + *id.IptcGuid
- }
- if id.Doi != nil && *id.Doi != "" {
- return "doi:" + *id.Doi
- }
- if id.ContentHash != nil && *id.ContentHash != "" {
- return "hash:" + *id.ContentHash
- }
- if id.CanonicalUrl != nil && *id.CanonicalUrl != "" {
- return "url:" + *id.CanonicalUrl
- }
- return uuid.NewString()
-}
-```
-
-For the full deduplication logic, see the [Content Deduplication](/components/broker/content-dedup/) page.
-
-## Stage 4: Order by Relevance
-
-After grouping, the Broker puts the offers for each URI in its order of relevance to the agent's request. Relevance is the Broker's judgement of how well an offer answers the request, and the Broker's rules for it are public. The default engine draws on these signals:
-
-1. **Match to the request.** How well the resource answers the agent's `uris`, `query` or `search_filters`. For a request in words, this is the search backend's order.
-
-2. **The agent's preferred Exchanges.** The agent names the Exchanges it has relationships with, such as subscriptions or contracts, in `RequestConstraints.preferred_exchanges`. The Broker SHOULD put their offers first when they have the resource.
-
-3. **Content attestation level (v1.0).** Level 2 (third-party attested) > Level 1 (self-attested) > Level 0 (no attestation). Offers with `ResourceAttestation` entries from trusted verification vendors carry independently verifiable claims about the content.
-
-4. **Exchange track record.** Exchanges that consistently deliver accurate, well-structured content, and whose `estimated_quantity` values have proven accurate, rank higher.
-
-Price is not a signal. The agent compares prices itself: each offer carries its price, and `Pricing.unit_cost` normalizes it to a cost per unit, so an agent can compare offers across Exchanges and pricing models by its own policy.
-
-```go
-// rankOffers puts the offers for one URI in this Broker's order of relevance.
-// Price is not an input: the agent compares prices itself.
-func (e *defaultEngine) rankOffers(offers []rankedOffer, req *forav1.DiscoveryRequest) []rankedOffer {
- for i := range offers {
- score := 0.0
-
- // How well the resource answers the request: the search backend's
- // score for a request in words, equal for every offer on a named URI.
- score += e.matchScore(offers[i], req) * 1000.0
-
- // Exchanges the agent named, such as those it holds subscriptions with.
- if isPreferred(offers[i].Exchange.Domain, req.GetConstraints().GetPreferredExchanges()) {
- score += 500.0
- }
-
- // Content attestation level (v1.0)
- // Level 2 (third-party) > Level 1 (self-attested) > Level 0 (none)
- score += float64(attestationLevel(offers[i].Offer)) * 100.0
-
- // Exchange track record: accurate content and estimated_quantity (historical)
- score += e.exchangeRecord.Score(offers[i].Exchange.Domain) * 50.0
-
- offers[i].Score = score
- }
-
- // Stable sort: offers with equal scores keep the order the Exchanges returned.
- sort.SliceStable(offers, func(i, j int) bool {
- return offers[i].Score > offers[j].Score // descending: most relevant first
- })
- return offers
-}
-```
-
-## Stage 5: Verify exchange_signature
-
-The Broker SHOULD verify `exchange_signature` on every Offer before it returns it, and drops an offer whose signature fails. This prevents an Exchange from tampering with its own offer fields after signing.
-
-```go
-func verifyOfferSignature(offer *forav1.Offer, exchange string, pubKeys map[string]ed25519.PublicKey) error {
- if offer.Signature == "" {
- return fmt.Errorf("offer signature is required but empty")
- }
-
- key, ok := pubKeys[exchange]
- if !ok {
- return fmt.Errorf("no public key for exchange %q", exchange)
- }
-
- return helpers.VerifyOffer(offer, offer.Signature, key)
-}
-```
-
-## Pluggable Selection Policies
-
-The default policy orders offers by relevance, as described above. A Broker can plug in another policy for how it orders offers, and publishes its rules either way:
-
-```go
-type SelectionPolicy interface {
- // Rank puts offers in this Broker's order of relevance. Index 0 is the
- // offer it judges most relevant; the agent chooses among all of them.
- Rank(offers []rankedOffer, req *forav1.DiscoveryRequest) []rankedOffer
-}
-
-// Built-in policies
-type RelevancePolicy struct{} // Default: match, preferred Exchanges, attestation, track record
-type PreferredExchangePolicy struct{} // The agent's preferred Exchanges first, then relevance
-type FreshnessWeightedPolicy struct{} // Newer content first, weighted against relevance
-type QualityScorePolicy struct{} // Exchange reputation scores
-```
-
-No policy orders offers by price. The policy is set at Broker construction time, not per-request. Per-request behavior is controlled through `acceptable_restrictions` and `RequestConstraints`.
-
-## Exchange Authorization Verification
-
-Before it returns an offer, the Broker SHOULD verify that the Exchange is authorized by the provider whose content is being licensed. This is the FORA equivalent of ads.txt verification in programmatic advertising.
-
-```go
-func (o *Broker) verifyExchangeAuthorization(
- ctx context.Context,
- contentDomain string,
- exchangeDomain string,
-) (bool, error) {
- manifest, err := o.parseJSONCache.Get(ctx, contentDomain)
- if err != nil {
- return false, fmt.Errorf("fetching fora.json for %s: %w", contentDomain, err)
- }
- for _, authorized := range manifest.AuthorizedExchanges {
- if authorized.Domain == exchangeDomain {
- return true, nil
- }
- }
- return false, nil // Exchange not authorized by provider
-}
-```
-
-This check runs before the Broker returns the offers. The Broker drops an offer whose Exchange the provider has not authorized. It never puts another offer in place of one the agent chose, and can't: the agent's acceptance signs the offer it chose.
-
-## Selection Rationale Logging
-
-Every answer is logged with the order the Broker returned and the reasons for it, for audit:
-
-```go
-type SelectionLog struct {
- // Broker-internal audit key correlating this decision to the inbound request.
- // Request/response correlation rides the X-Request-ID HTTP header, not a message field.
- FORARequestID string `json:"fora_request_id"`
- Timestamp time.Time `json:"timestamp"`
- ExchangesQueried []string `json:"exchanges_queried"`
- ExchangesResponded []string `json:"exchanges_responded"`
- TotalOffers int `json:"total_offers"`
- FilteredOffers int `json:"filtered_offers"`
- SameContentGroups int `json:"same_content_groups"`
- Order []OrderEntry `json:"order"`
- RejectionReasons map[string]int `json:"rejection_reasons"`
- SelectionPolicy string `json:"selection_policy"`
- LatencyMs int64 `json:"latency_ms"`
-}
-
-// OrderEntry records one returned offer: where it stood and why.
-type OrderEntry struct {
- URI string `json:"uri"`
- OfferID string `json:"offer_id"`
- Exchange string `json:"exchange"`
- Position int `json:"position"`
- Score float64 `json:"score"`
- Signals map[string]float64 `json:"signals"` // each signal's share of the score
-}
-```
-
-## Transparency and Auditability
-
-The Broker is an intermediary. FORA addresses transparency through:
-
-### Signed Offer Pass-Through
-
-The Exchange signs the Offer using its private key. The Broker passes the signed offer through to the agent. **The Broker cannot inflate prices** because the Exchange's signature covers the pricing fields.
-
-```mermaid
-sequenceDiagram
- participant MP as Exchange
- participant Orch as Broker
- participant Agent as AI Agent
-
- MP->>Orch: ResourceResponse (Offer with exchange_signature)
- Note over Orch: Broker CANNOT modify offer fields without invalidating signature
- Orch->>Agent: DiscoveryResponse (includes original signed Offer)
- Note over Agent: Agent verifies exchange_signature against MP's public key. Price tampering detected.
-```
-
-### Fee Disclosure
-
-`DiscoveryResponse` carries the signed Offers unchanged (one `OfferGroup` per requested URI); it has no `broker_fee` field, so the Broker cannot fold a fee into the discovery result. Any Broker fee is additive and disclosed out of band, never hidden in the offer price — the Exchange's signature over the Offer's pricing fields makes silent inflation detectable. The agent sees: Exchange price + Broker fee = total cost.
-
-### Audit Trail
-
-For full auditability, the agent operator should:
-
-1. **Verify offer signatures** on every DiscoveryResponse
-2. **Retain selection logs**, which record the order the Broker returned and the signals behind it, and check them against the Broker's published rules
-3. **Spot-check by going direct** -- query Exchanges directly to verify the Broker isn't hiding offers
diff --git a/website/src/content/docs/components/content-ingestion/sources.mdx b/website/src/content/docs/components/content-ingestion/sources.mdx
index 637fbf4a..bd5d8aec 100644
--- a/website/src/content/docs/components/content-ingestion/sources.mdx
+++ b/website/src/content/docs/components/content-ingestion/sources.mdx
@@ -325,7 +325,7 @@ Companies like GumGum, Peer39, and DoubleVerify already index the web for contex
### Provenance Tracking
Every catalog entry records who provided it and when, via two fields on `ResourceEntry`:
-- `provenance_source` -- e.g., "gumgum.com", "ssp-alpha.com", "wordpress-plugin"
+- `provenance_source` -- e.g., "gumgum.com", "alpha.example", "wordpress-plugin"
- `provenance_timestamp` -- when the metadata was collected/generated
This creates an audit trail for "where did this catalog entry come from?" -- essential when multiple parties can push metadata for the same content.
diff --git a/website/src/content/docs/components/edge-function/bot-detection.mdx b/website/src/content/docs/components/edge-function/bot-detection.mdx
index b0096ccd..bd038b1a 100644
--- a/website/src/content/docs/components/edge-function/bot-detection.mdx
+++ b/website/src/content/docs/components/edge-function/bot-detection.mdx
@@ -278,7 +278,7 @@ When a bot is detected on a protected path without a signed URL:
HTTP/1.1 403 Forbidden
Content-Type: application/json
X-Content-Rules: https://techcrunch.com/.well-known/fora.json
-X-FORA-Exchange: exchange.ssp-example.com
+X-FORA-Exchange: exchange.example
Cache-Control: no-store
```
diff --git a/website/src/content/docs/components/edge-function/signed-url-verification.mdx b/website/src/content/docs/components/edge-function/signed-url-verification.mdx
index 211b4039..0c9465c1 100644
--- a/website/src/content/docs/components/edge-function/signed-url-verification.mdx
+++ b/website/src/content/docs/components/edge-function/signed-url-verification.mdx
@@ -318,4 +318,4 @@ sequenceDiagram
2. **Short TTL** — five minutes in the reference deployment, which narrows the window.
3. **Reconciliation** — the Exchange transaction log and the edge delivery log both record the signed-URL hash. Cross-referencing them detects replay after the fact.
-This matches ad-tech's approach to impression deduplication: real time is best-effort, reconciliation is authoritative.
+In real time the checks are best-effort; reconciliation is authoritative.
diff --git a/website/src/content/docs/components/exchange/billing-adapter.mdx b/website/src/content/docs/components/exchange/billing-adapter.mdx
index 5814ba76..f90177d1 100644
--- a/website/src/content/docs/components/exchange/billing-adapter.mdx
+++ b/website/src/content/docs/components/exchange/billing-adapter.mdx
@@ -171,35 +171,35 @@ type DynamoDBBillingAdapter struct {
## Real Integration Example
-A Exchange operator (e.g., an existing ad-tech SSP adding resource access) would implement the interface against their existing billing system:
+An Exchange operator that already runs a billing system implements the interface against it:
```go
-// ExampleSSPBillingAdapter connects to SSP Corp's internal billing API.
-type ExampleSSPBillingAdapter struct {
+// ExampleBillingAdapter connects to the operator's internal billing API.
+type ExampleBillingAdapter struct {
httpClient *http.Client
baseURL string
apiKey string
}
-func (a *ExampleSSPBillingAdapter) Authorize(
+func (a *ExampleBillingAdapter) Authorize(
ctx context.Context, req *BillingAuthorizeRequest,
) (*BillingAuthorizeResponse, error) {
- // Call SSP Corp's internal billing API
- sspReq := &ssp.AuthorizeRequest{
+ // Call the operator's internal billing API
+ billReq := &billing.AuthorizeRequest{
AccountID: mapBillingRefToAccount(req.BillingRef),
Amount: req.Amount,
Currency: req.Currency,
Product: "content-licensing",
Reference: req.OfferID,
}
- sspResp, err := a.ssp.Authorize(ctx, sspReq)
+ billResp, err := a.billing.Authorize(ctx, billReq)
if err != nil {
- return nil, fmt.Errorf("ssp billing: %w", err)
+ return nil, fmt.Errorf("billing: %w", err)
}
return &BillingAuthorizeResponse{
- Approved: sspResp.Status == "approved",
- BillingID: sspResp.HoldID,
- Reason: sspResp.DeclineReason,
+ Approved: billResp.Status == "approved",
+ BillingID: billResp.HoldID,
+ Reason: billResp.DeclineReason,
}, nil
}
```
diff --git a/website/src/content/docs/components/exchange/configuration.mdx b/website/src/content/docs/components/exchange/configuration.mdx
index 3722149d..0f95b0e0 100644
--- a/website/src/content/docs/components/exchange/configuration.mdx
+++ b/website/src/content/docs/components/exchange/configuration.mdx
@@ -10,7 +10,7 @@ Three-tier configuration with precedence: environment variables > config file >
| Setting | Source | Hot Reload? | Example |
|---|---|---|---|
| Listen address | Env var | No (restart) | `EXCHANGE_LISTEN_ADDR=:8080` |
-| Exchange domain | Env var | No | `EXCHANGE_DOMAIN=exchange.ssp.com` |
+| Exchange domain | Env var | No | `EXCHANGE_DOMAIN=exchange.example` |
| TLS cert/key | Env var / file | No | `EXCHANGE_TLS_CERT=/etc/tls/cert.pem` |
| Tenant configs | Config file (YAML/JSON) | Yes (SIGHUP) | `EXCHANGE_CONFIG=/etc/exchange/config.yaml` |
| Signing keys | Secrets manager | Yes (polled) | `EXCHANGE_SECRETS_PROVIDER=aws-sm` |
@@ -26,12 +26,12 @@ Three-tier configuration with precedence: environment variables > config file >
```yaml
# /etc/exchange/config.yaml
exchange:
- domain: "exchange.ssp-example.com"
+ domain: "exchange.example"
version: "1.0"
billing:
adapter: "dynamodb" # or "http", "in-memory"
- endpoint: "https://billing.internal.ssp.com/v1"
+ endpoint: "https://billing.internal.example/v1"
timeout: "30ms"
timeout_policy: "reject" # or "defer"
diff --git a/website/src/content/docs/components/transaction-log/storage-backends.mdx b/website/src/content/docs/components/transaction-log/storage-backends.mdx
index 70c21502..7aeb8795 100644
--- a/website/src/content/docs/components/transaction-log/storage-backends.mdx
+++ b/website/src/content/docs/components/transaction-log/storage-backends.mdx
@@ -214,7 +214,7 @@ type TransactionEvent struct {
### Retention Policy
-13-month minimum retention for financial data. Matches ad-tech invoice cycles.
+13-month minimum retention for financial data.
| Data Class | Hot (fast query) | Warm (queryable, slower) | Cold (archive) | Total Retention |
|---|---|---|---|---|
diff --git a/website/src/content/docs/getting-started/for-exchange-operators.mdx b/website/src/content/docs/getting-started/for-exchange-operators.mdx
index 536e564f..ef1f17b3 100644
--- a/website/src/content/docs/getting-started/for-exchange-operators.mdx
+++ b/website/src/content/docs/getting-started/for-exchange-operators.mdx
@@ -1,146 +1,87 @@
---
title: "FORA for Exchange Operators"
-description: "How to operate a FORA Exchange — aggregate resource catalogs, handle transactions, earn a margin"
+description: "How to run a FORA Exchange on FORA Server: what you deploy, how publishers and agents join, the rules and fee you set, and the checks every Exchange runs."
---
-## The Opportunity
+An Exchange holds publishers' catalogs and terms, signs their offers, records each sale and takes usage reports. Anyone can run one. FORA Server, which is open source, includes the Exchange, and every FORA agent can buy from any FORA Exchange, because every Exchange speaks the same protocol. You set your own rules and your own fee.
-Resource providers need a transaction layer but don't want to build one. Courts don't want to run billing APIs. Publishers don't want to negotiate with every AI company. Hospitals don't want to handle metered access to imaging data. Patent offices don't want to build per-query pricing.
+Settlement stays outside the protocol: you bill the agents' account holders and pay your publishers through your own billing. FORA defines no payment rail.
-You solve this by running an **Exchange**: aggregate their catalogs, handle discovery, pricing, and transactions, and earn a margin on every access. This is the aggregator pattern — the same model that drives SSPs in ad-tech, clearinghouses in finance, and distributors in publishing.
+## Who runs an Exchange
-FORA was validated across **18 real-world scenarios** spanning 10 industries. The same protocol works for all of them:
+The same messages carry any catalog. What changes is the unit an offer is metered in and the domain profile its metadata follows:
-| Exchange Type | What You Aggregate | Providers | Example Operators |
-|---|---|---|---|
-| Media exchange | News articles, podcasts, video | Publishers | SSPs, media companies |
-| Academic exchange | Journal articles, preprints | Publishers, repositories | Elsevier, OpenAlex |
-| Legal exchange | Court filings, legislation, patents | Courts, patent offices | PACER aggregator, EUR-Lex |
-| Credit/financial exchange | Credit reports, market data | Data providers | D&B resellers, MarketData |
-| Medical data exchange | Clinical data, imaging | Hospitals, research institutions | TCIA, imaging exchanges |
-| Government data exchange | Property records, business filings | County/state agencies | CoreLogic, ATTOM |
-
-The value proposition is the same regardless of domain: providers get revenue from AI agents without building anything, agents get standardized access without bespoke integrations, and you keep a margin on every transaction.
-
-## What You Deploy
-
-You deploy an **Exchange Node** -- a Go service that handles three API calls:
-
-1. **DiscoverResources** -- AI agent asks "what's available at this URL and how much?" Your Exchange looks up the provider's catalog and returns offers with pricing.
-2. **ExecuteTransaction** -- AI agent says "I'll take it." Your Exchange checks the requester's balance, logs the transaction, and returns a signed URL.
-3. **ReportUsage** -- AI agent reports what it did with the content. Mandatory. You track compliance.
-
-That's the whole protocol. Three RPCs. Your billing adapter plugs in where `Authorize(requester, amount)` and `Record(transaction)` are called.
-
-## Unit-Agnostic Metering
-
-A media exchange meters in tokens. A legal exchange meters in pages. A medical exchange meters in studies. A geospatial exchange meters in sq_km. Same protocol, different units.
-
-FORA pricing states what is metered and at what price, with no assumption about the unit:
-
-- `unit`: what is metered.
-- `rate`: the price of one `unit`.
-- `estimated_quantity`: optional, the publisher's own estimate, in `unit`. A metered purchase charges the estimate × `rate`, or one unit's `rate` when the offer states no estimate, and that charge is final (see [Charging a metered purchase](/protocol/transaction-flow/#charging-a-metered-purchase)).
-- `unit_cost`: the comparison metric, the price of one purchase divided by the resource's size in the comparison unit of its content type. It never enters the charge.
-
-```
-Exchange Type Metering Unit Example rate
-──────────────────────────────────────────────────────────────
-Media tokens $0.00003/token
-Legal pages $0.50/page
-Academic accesses $0.05/access
-Medical imaging studies $2.00/study
-Credit/financial records $5.00/record
-Geospatial sq_km $0.10/sq_km
-Streaming (audio) minutes $0.02/minute
-Pharma interaction_pairs $0.001/pair
-```
-
-Usage reporting follows the same pattern: `consumed_quantity` + `consumed_unit`, which matches the offer's `unit`. A report records the quantity consumed and is never refused for it. Your Exchange MUST support these fields on all offers and MUST NOT assume an offer is metered in tokens; only a usage report that omits `consumed_unit` is read as tokens.
-
-## Extension Profiles
-
-Your Exchange declares which domain profiles it supports in its manifest. This tells Brokers and agents what kind of resources you handle:
-
-```json
-// Media exchange
-{ "supported_profiles": ["fora-news-v1"] }
-
-// Academic exchange
-{ "supported_profiles": ["fora-academic-v1"] }
-
-// Legal exchange
-{ "supported_profiles": ["fora-legal-v1"] }
+| Exchange over | What it holds, and from whom | Who might run it |
+|---|---|---|
+| News | Articles, podcasts and video, from publishers | A news publisher group, a press agency |
+| Scholarly content | Journal articles and preprints, from publishers and repositories | A university press, a society publisher |
+| Legal records | Court filings, legislation and patents, from courts and patent offices | A legal-data company |
+| Financial data | Credit reports and market data, from data providers | A data vendor |
+| Medical data | Clinical data and imaging, from hospitals and research institutions | A research consortium |
+| Public records | Property records and business filings, from agencies | A public-records company |
+| Music | Recordings and the works they record, from labels, publishers and collectives | A licensing collective |
-// Multi-domain exchange
-{ "supported_profiles": ["fora-news-v1", "fora-academic-v1"] }
-```
+An existing marketplace can run a FORA Exchange over its own catalog, beside the channels it already has. See [For Content Marketplaces](/getting-started/existing-marketplace/).
-Agents declare which profiles they understand, and a Broker forwards that list to your Exchange unchanged; it does not route by profile. When an academic research agent declares `fora-academic-v1` and you declare that profile, your offers carry its fields.
+## What you deploy
-Profile conformance means your Exchange sets the required `ext` fields defined in the profile spec and validates them against the profile's JSON Schema:
+FORA Server's Exchange is one Go binary in a container, `ghcr.io/fora-protocol/exchange`. It listens on two ports: the public Exchange listener, `8081` by default, and an internal admin listener, `8082`. To run it you provide:
-| Profile | Scope | What It Means for Your Exchange |
-|---|---|---|
-| `fora-news-v1` | News, podcasts, broadcasting | Set IPTC subject codes, correction status, podcast metadata in offer ext fields |
-| `fora-academic-v1` | Scholarly articles, preprints | Set DOI, OA status, version lifecycle in offer ext fields |
-| `fora-legal-v1` | Legislation, case law, patents | Set jurisdiction, amendment chains, ELI/ECLI in offer ext fields |
+- **Two PostgreSQL databases**: one for the catalog, the transaction log and the audit log (`EXCHANGE_DSN`), and one for the account registry (`EXCHANGE_SOR_DSN`).
+- **Redis** (`REDIS_URL`), which stops a signed request from being replayed. Every instance of a scaled-out Exchange shares one.
+- **An Ed25519 private key**, which signs offers and delivery URLs. An RSA key is needed only for a publisher whose CDN is AWS CloudFront.
+- **A ledger.** `FORA_BILLING_ADAPTER` chooses it: `tigerbeetle` keeps a prepaid balance per agent account in TigerBeetle, in the currencies `EXCHANGE_BILLING_LEDGER` lists. The default, `free`, approves every charge and records none.
+- **The Broker's address** (`EXCHANGE_BROKER_WELLKNOWN_URL`). The Exchange reads the Broker's withdrawn-key list from there and refuses to start without the address. See [Broker](/components/broker/overview/#who-runs-a-broker).
+- **Your hostname** (`EXCHANGE_DOMAIN`), and one seat row for it, which holds your fee and your agent policy.
-A Exchange MAY implement zero, one, or multiple profiles. You can start with one domain and expand.
+The catalog importer, `fora-import`, ships in the same image and runs as a job. The publisher console is a separate, optional service. You can deploy each component by hand, or with the Terraform modules in the FORA Server repository, which render a Docker Compose stack. The [Exchange deployment guide](https://github.com/FORA-Protocol/reference-implementation/blob/main/src/exchange/DEPLOYMENT.md) and the [runbook](https://github.com/FORA-Protocol/reference-implementation/blob/main/src/exchange/RUNBOOK.md) are in the FORA Server repository.
-## If You're an SSP: How FORA Maps to Your Infrastructure
+The Exchange answers these calls:
-If you operate an SSP or ad exchange, FORA maps directly to your existing concepts:
+| Call | What it does |
+|---|---|
+| `ExchangeService.Register` | Opens an agent's account and returns its `billing_ref` |
+| `ExchangeService.GetAccountStatus` | Returns the state of the agent's account |
+| `ExchangeService.DiscoverResources` | Returns signed offers for the URLs in a `ResourceQuery` |
+| `ExchangeService.ExecuteTransaction` | Buys offers and returns a signed delivery URL for each paid item |
+| `ExchangeService.ReportUsage` | Takes the agent's usage report and returns its `report_id` |
+| `CatalogService.PushResources` | Takes catalog entries from a contributor the site's `fora.json` names |
+| `AdminService.SetTenantFeeRate` | Sets your fee, on the admin listener only |
+| `AdminService.SetReportingPolicy` | Sets your reporting policy, on the admin listener only |
-```
-Ad-Tech Concept → FORA Equivalent
-─────────────────────────────────────────────
-SSP / Exchange → Exchange Node
-Publisher → Resource Provider
-ads.txt → fora.json (authorized providers)
-Bid Request → ResourceQuery
-Win Notification → TransactionRequest
-eCPM → unit_cost (effective cost per unit)
-Impression → Content access (signed URL)
-Viewability Report → Usage Report
-```
+It also serves `/.well-known/fora.json`, your key directory at `/.well-known/http-message-signatures-directory`, `/healthz` and `/readyz`.
-**You already have:**
-- Provider relationships and contracts
-- Billing infrastructure (invoicing, prepaid, credit)
-- CDN access for provider domains
-- Revenue share agreements
+## Your rules and your fee
-**FORA adds:**
-- A Exchange service (Go binary, stateless, horizontally scalable)
-- An edge function deployed to provider CDNs (bot blocking + signed URL verification)
-- A resource catalog imported from provider sitemaps, with the terms each provider sets in the publisher console
+- **Your fee.** Your commission is `fee_rate_bps` on your seat, in basis points, set with `AdminService.SetTenantFeeRate` without a restart. 1500 is 15%. Each sale records the gross, your fee and the publisher's net.
+- **Which agents can buy.** `activate_new_agents_by_default` decides whether a newly registered agent can buy at once, or waits until you activate its account. A deactivated account is refused paid purchases with `DENIAL_REASON_ACCOUNT_INACTIVE`.
+- **A welcome credit.** `EXCHANGE_DEFAULT_AGENT_CREDIT` grants each new account a starting balance, for example `EUR=100`.
+- **Purchases through a Broker.** `allow_broker_relay` on your seat decides whether you accept purchases the Broker relays. A refused item is denied with `DENIAL_REASON_RELAY_NOT_ACCEPTED`, and the agent can buy that offer directly.
+- **How many signatures a request may carry.** `EXCHANGE_MAX_INTERMEDIARY_HOPS`, published as `max_intermediary_hops`, 4 by default.
+- **Reporting.** `AdminService.SetReportingPolicy` sets which fields a usage report must carry. A report is never refused for the quantity it states.
-## Provider Onboarding
+The publishers set the terms and prices of their own content. Your Exchange signs the offers it builds from them.
-For each provider, you:
+## Publishers
-1. Generate their `fora.json` and have them publish it on their origin: the file they serve proves they control the domain and names your Exchange
-2. Import their pages from their sitemap into the catalog, with the terms they set in the publisher console, which fills them in from their RSL license when they publish one
-3. Configure their pricing tier
-4. Authorize `catalog_contributors` -- third-party verification vendors the provider permits to push attestations for their content
-5. If applicable, deploy the FORA edge function to their delivery endpoint (CDN, API gateway, PACS server) for signed URL verification
-6. Done. Their content is now available to AI requesters through your Exchange
+A publisher joins your Exchange through a publisher console:
-Providers publish that one file and deploy nothing else in the managed model. You manage the rest. This is the [Exchange-Managed deployment model](/architecture/deployment-models/). Some providers (large publishers, data vendors) may prefer to manage their own delivery endpoint -- the protocol supports both.
+1. It signs in and registers its business and its site.
+2. It sets its terms. The console fills them in from the site's RSL license when the site publishes one, and the publisher sets the price.
+3. The console generates the site's `fora.json`, which names your Exchange and lists your catalog contributor (`EXCHANGE_CATALOG_CONTRIBUTOR_HOST`) in `catalog_contributors`, and the edge function package for the site's CDN. The publisher serves the file and installs the package, usually in its own CDN account.
+4. The console checks both, and the listing goes live once the site proves it authorized your Exchange. `fora-import` then imports the pages of the site's sitemap into your catalog, with the publisher's terms, through `CatalogService.PushResources`.
-## Requester Onboarding
+From then on, the publisher sees its sales in the console. See [Publisher Onboarding](/getting-started/publisher-onboarding/) for the publisher's side.
-AI companies register via your existing account management or a self-signup API:
+## Agents
-- **Enterprise**: Out-of-band key exchange during contract signing. You register their Ed25519 public key.
-- **Self-signup**: AI agent registers via API with their public key manifest. Per-request billing only (no subscription).
+An agent opens an account at your Exchange with `ExchangeService.Register`. The Exchange identifies the agent by the key that signed the request and returns a `billing_ref`, the opaque, long-lived handle of the agent's account at your Exchange. Registering again returns the same handle. A paid purchase without an account is denied with `DENIAL_REASON_ACCOUNT_NOT_REGISTERED`; free content needs none.
-You don't need bilateral deals with every AI company. Any agent that speaks the FORA protocol can buy from your Exchange.
+You don't need a separate deal with each AI company. Any agent that speaks FORA can open an account and buy, under your agent policy. An agent on MCP registers through the [Identity Service](/components/identity/overview/).
-## Requester Verification
+## Requester verification
-The `Requester` message carries no signature: it states who is asking, and the RFC 9421 HTTP Message Signature on the request proves who sent it. Your Exchange MUST verify every request before acting on it. The rules are on the [Authentication](/protocol/authentication/) page; apply them in this order, and reject a request that fails any of them, with no fallback and no degraded mode:
+The `Requester` message carries no signature: it states who is asking, and the RFC 9421 HTTP Message Signature on the request proves who sent it. An Exchange MUST verify every request before acting on it, and FORA Server's Exchange does. The rules are on the [Authentication](/protocol/authentication/) page. An Exchange applies them in this order, and rejects a request that fails any of them, with no fallback and no degraded mode:
1. **Count the signatures first.** Before you verify any, refuse a request carrying more signatures than your `WellKnownManifest.max_intermediary_hops` with `resource_exhausted` (HTTP 429) and no typed reason. Every signature counts, whether or not it covers another. See [Verification at the Exchange](/protocol/authentication/#verification-at-the-exchange).
2. **Verify each signature under the Web Bot Auth profile.** Resolve its `keyid`, the key's RFC 7638 thumbprint, in the key directory its own covered `Signature-Agent` member names (`{origin}/.well-known/http-message-signatures-directory`), never from `Requester.domain`. Check the profile parameters, the four components a FORA RPC covers (`@method`, `@target-uri`, `content-digest`, `authorization`) and the `Content-Digest` of the body. Refuse a failure as `unauthenticated` with `request_auth_failure`: `SIGNATURE_MISSING` when no signature parses, `SIGNATURE_INVALID` when one does not verify, `SIGNATURE_STALE` outside its `created`/`expires` window. When a required component is missing, also answer with an `Accept-Signature` field listing the components you require, so the client can fix its request. See [Signature Verification](/protocol/authentication/#signature-verification) and [The Web Bot Auth Profile](/protocol/authentication/#the-web-bot-auth-profile).
@@ -152,9 +93,9 @@ The `Requester` message carries no signature: it states who is asking, and the R
Cache directories and keys with a TTL and re-fetch them to pick up rotation, without a fetch per request (see [Caching Contract](/protocol/authentication/#caching-contract)).
-### Delegation Verification
+### Delegation verification
-When a request includes a `Delegation` message (nested inside `Requester`), run the chain through the profile's verifier (`helpers.VerifyDelegation` in the Go SDK). The procedure, the limits and the checks are stated once, in [Verification](/protocol/authentication/#verification). This page adds only what your Exchange supplies to the verifier and what it does with the result:
+When a request includes a `Delegation` message (nested inside `Requester`), the Exchange runs the chain through the profile's verifier (`helpers.VerifyDelegation` in the Go SDK). The procedure, the limits and the checks are stated once, in [Verification](/protocol/authentication/#verification). This page adds only what the Exchange supplies to the verifier and what it does with the result:
1. **Trust comes from the subscription record.** Give the verifier the trusted root keys of the subscription record that owns the gated term, each with the issuer identity it belongs to. Trust is configured on that record, never fetched: not from `principal_domain`, not from `issuer`, not from a WBA directory, OIDC or JWKS. A key trusted on one record grants nothing on another. Withdraw trust by removing a key from the record's list; `revocation_uri` is not part of the profile.
2. **The holder is the key the request proved.** Give the verifier the thumbprint of that key: on a direct request the key that signed it (RFC 9421), on a purchase a Broker relays the key that signed each item's `AgentAcceptance`. The verifier refuses a mismatch. This is mandatory: it is what makes a stolen token unusable, so a token possessed without its signing key grants nothing. On a query a Broker originated, which proves possession of no agent key, do not verify or honor the delegation: answer as if none were present.
@@ -163,7 +104,7 @@ When a request includes a `Delegation` message (nested inside `Requester`), run
This verification is entirely offline — no callback to the principal is required.
-### Scope-Based Catalog Filtering
+### Scope-based catalog filtering
After verifying identity (and any delegation, as above), present the non-gated terms the requester's stated scopes cover; only those reach the `DiscoverResources` response. The scopes are the requester's own statement and you do not verify them. A gated term, a subscription term in the usual case, is different: present it only when the verified delegation's effective scopes cover it, ignore `requester.scopes` for that term, and answer a requester without a verified delegation as if the term did not exist. The matching rule is stated once, in [Scope Matching](/protocol/authentication/#scope-matching).
@@ -171,13 +112,13 @@ For a resource that exists but falls outside the requester's scopes, answer exac
An offer you presented stays purchasable until it expires, so a purchase is never refused because the requester's scopes do not cover the resource.
-### Subscription Quota Signaling
+### Subscription quota signaling
-When the requester holds a subscription (identifiable via the requester's `delegation` and/or subscription scopes), populate `SubscriptionQuotaInfo` entries on offers and transaction responses. This proactive quota signaling lets agents track remaining allowance and avoid committing to transactions they cannot complete. Track `max_accesses` and `quota_period` from the `Delegation` message when present.
+When the requester holds a metered subscription, an Exchange can report the allowance left in `SubscriptionQuotaInfo` entries on offers and transaction responses, so the agent does not commit to a purchase it cannot complete. An Exchange meters a subscription on its subscription record, never per delegation token, and names the record in `SubscriptionQuotaInfo.subscription_id`.
-### New Denial Reasons to Implement
+### Denial reasons
-FORA defines identity- and entitlement-related denial reasons your Exchange MUST return when appropriate. The delegation reasons:
+FORA defines identity- and entitlement-related denial reasons an Exchange MUST return when they apply. The delegation reasons:
| Denial Reason | When to Return |
|---|---|
@@ -203,121 +144,53 @@ And the relay reason, for a provider that does not accept purchases a Broker rel
This is the identity/entitlement subset with operator guidance; the complete, authoritative `DenialReason` enum is rendered from the proto on the [proto reference](/reference/proto-fora/). For the full identity model specification — Requester fields, the JWT chain, scope format, and key management — see [Authentication](/protocol/authentication/).
-## Attestation Verification
-
-Your Exchange verifies `ResourceAttestation` signatures at catalog push time. When a provider or verification vendor pushes resource metadata via `CatalogService.PushResources`, your Exchange:
-
-1. Fetches the signer's public key from their WBA directory (the JWK Set at `https://{verifier}/.well-known/http-message-signatures-directory`), identified by its RFC 7638 thumbprint (the RFC 9421 `keyid`)
-2. Verifies the Ed25519 signature over JCS-canonicalized claims
-3. Checks that the `verifier` is either the provider domain (Level 1 self-attestation) or a vendor listed in the provider's `catalog_contributors` (Level 2 third-party attestation)
-4. Rejects attestations from unauthorized contributors
-
-This prevents unauthorized parties from injecting false claims into your resource catalog.
-
-## Dispute Resolution
-
-Your Exchange handles `DisputeTransaction` RPCs from agents. The dispute system operates in three tiers:
-
-| Tier | Scope | Volume | Response Time |
-|---|---|---|---|
-| **Tier 1 -- Automated** | Delivery failures, content hash mismatches, signed URL expiry | ~99% of disputes | < 1 second |
-| **Tier 2 -- Rule-Based** | Ambiguous evidence, delivery says 200 but content is suspect | ~0.9% of disputes | < 24 hours |
-| **Tier 3 -- Investigation** | Aggregate fraud patterns, systematic abuse | ~0.1% of disputes | Case-by-case |
-
-**`report_id` generation**: When an agent calls `ReportUsage`, your Exchange returns a `report_id` in the `UsageReportResponse`. This `report_id` is required on every `DisputeRequest` -- it proves the agent fulfilled its reporting obligation before disputing. Your Exchange rejects disputes without a valid `report_id`.
-
-Delivery logs are the authoritative evidence source. They cannot be fabricated by the agent and provide independent verification of delivery status, response size, and timing.
-
-## Exchange Manifest and Health Checks
-
-As an Exchange operator, you are responsible for two additional capabilities:
-
-**Exchange Manifest** -- Your Exchange serves a machine-readable self-description at `/.well-known/fora.json` (`role=ROLE_EXCHANGE`). This tells Brokers and agents what your Exchange supports (pricing models, delivery methods, accepted verifiers, endpoints) without trial-and-error. Your offer-signing keys are published separately in your WBA directory (the JWK Set at `/.well-known/http-message-signatures-directory`), not in `fora.json`. The manifest includes:
+## Units and profiles
-- **`base_currency`** (ISO 4217 code) -- the currency for all `unit_cost` values. Lets an agent compare offers across Exchanges. A legal exchange quoting in EUR and a media exchange quoting in USD can be compared when both declare their currency.
-- **`supported_profiles`** -- domain extension profiles your Exchange conforms to.
+An offer names what it is metered in, and a metered purchase charges the publisher's estimate times the rate:
-The manifest is generated from your configuration at startup and served as a static JSON document. See [Exchange Manifest](/protocol/exchange-manifest/).
-
-**Health Checks** -- Your Exchange exposes three health layers: gRPC health (`grpc.health.v1.Health/Check`), HTTP liveness (`/healthz`), and HTTP readiness (`/readyz`). Brokers use gRPC health probing to make structured routing decisions -- they can distinguish an Exchange with a stale catalog from one with billing down. Kubernetes uses the HTTP endpoints for pod lifecycle management. See [Health Checks](/components/exchange/health-checks/).
-
-## Revenue Model
-
-Revenue depends on your exchange domain and the value of the resources you aggregate:
+- `unit`: what is metered.
+- `rate`: the price of one `unit`.
+- `estimated_quantity`: optional, the publisher's own estimate, in `unit`. A metered purchase charges the estimate × `rate`, or one unit's `rate` when the offer states no estimate, and that charge is final (see [Charging a metered purchase](/protocol/transaction-flow/#charging-a-metered-purchase)).
+- `unit_cost`: the price of one purchase divided by the resource's size in the comparison unit of its content type. It never enters the charge.
```
-Media exchange:
- Provider sets price: $0.05/article (tokens)
- AI Agent pays: $0.05/article
- You keep: Your standard rev-share margin
-
-Legal exchange:
- Provider sets price: $0.50/page (court filing)
- AI Agent pays: $0.50/page
- You keep: Your standard rev-share margin
-
-Credit exchange:
- Provider sets price: $5.00/record (credit report)
- AI Agent pays: $5.00/record
- You keep: Your standard rev-share margin
-
-Medical imaging exchange:
- Provider sets price: $2.00/study (MRI scan)
- AI Agent pays: $2.00/study
- You keep: Your standard rev-share margin
+Exchange over Pricing.unit Example rate
+──────────────────────────────────────────────────────────────
+News tokens $0.00003/token
+Legal records pages $0.50/page
+Scholarly content accesses $0.05/access
+Medical imaging images $2.00/image
+Financial data records $5.00/record
+Geospatial sq-km $0.10/sq-km
+Audio streams minutes $0.02/minute
+Drug interactions pharma:interaction_pairs $0.001/pair
```
-Higher-value resources mean higher absolute margins per transaction. A credit exchange processing 2K reports/day at $5.00 average = $10K/day gross = **$3.6M/year**. A media exchange processing 10K articles/day at $0.05 average = $500/day gross = **$182K/year**. Infrastructure costs scale with RPS, not transaction value -- approximately **$40/day** at 10K RPS.
+A usage report states `consumed_quantity` and `consumed_unit`, in the offer's `unit`, and is never refused for the quantity it reports. An Exchange MUST NOT assume an offer is metered in tokens; only a usage report that omits `consumed_unit` is read as tokens.
-## Multi-Exchange Competition
+Your manifest's `supported_profiles` tells Brokers and agents which domain profiles your offers follow. FORA Server's Exchange declares `fora-news-v1`, `fora-comp-v1` and `fora-music-v1`. An agent declares the profiles it understands, and a Broker forwards that list to your Exchange unchanged. See [Extension Profiles](/protocol/extension-profiles/).
-AI agents can use a **Broker** to query multiple Exchanges at once. The Broker returns every Exchange's offers, each as a full package, in its order of relevance, and the agent compares them and decides. This means:
+## Exchange manifest and health
-- Competitive pressure keeps your margins honest
-- Premium content commands premium pricing (quality signals in offers)
-- Subscription deals give your providers an advantage (zero marginal cost for the requester)
-- `base_currency` in your manifest lets agents compare offers across Exchanges, even across currencies
+Your Exchange serves its manifest at `/.well-known/fora.json`, with `role` set to `ROLE_EXCHANGE`. It tells Brokers and agents what your Exchange offers: its endpoint, `base_currency`, `supported_profiles` and `max_intermediary_hops`. In FORA Server, `base_currency` is the first currency in `EXCHANGE_BILLING_LEDGER`, and the Exchange rebuilds the manifest from its configuration. Your offer-signing keys are in your key directory, not in `fora.json`. See [Exchange Manifest](/protocol/exchange-manifest/).
-## Technical Integration
+`/healthz` checks the catalog database, and `/readyz` also checks the ledger. FORA Server's Broker reads the health endpoint of each Exchange in its registry and routes only to an Exchange that answers `200`.
-**NFR targets**: 10K RPS, under 100ms p99 latency, under $0.00005/transaction infrastructure cost.
+## Attestations
-**Billing adapter interface** (your integration point):
-```go
-type BillingAdapter interface {
- Authorize(ctx, billingRef, amount) → (ok, error)
- Record(ctx, transaction) → error
- CheckSubscription(ctx, billingRef, providerGroup) → (sub, error)
-}
-// billingRef is the account handle the Exchange minted at Register and
-// resolves on every call from what authenticates the agent: the request
-// signature on a direct request, the agent's acceptances on a purchase a
-// Broker relays. The account is the agent's, never the Broker's.
-```
-
-Implement these three methods against your existing billing system. The reference implementation uses DynamoDB; production deployments wire it to their real ledger.
-
-## Unit-Agnostic Pricing for Non-Text Resources
-
-FORA uses a single unit-agnostic pricing model, `PRICING_MODEL_PER_UNIT`, for all metered resources. `Pricing.unit` names what is metered, so non-text resources are priced through the same model:
-
-| Model | Unit | Use Case |
-|---|---|---|
-| `PRICING_MODEL_PER_UNIT` | `pages` | Court filings, legal documents, PDFs |
-| `PRICING_MODEL_PER_UNIT` | `minutes` | Video, audio, streaming sessions |
-| `PRICING_MODEL_PER_UNIT` | `records` | Database records, credit reports, medical studies |
+An attestation is a signed claim about a resource, by its publisher or by a verification vendor. When attestations arrive with `CatalogService.PushResources`, the protocol has the Exchange check that the signer is the provider itself or a contributor the provider's `catalog_contributors` lists, and verify the attestation's Ed25519 signature against the key in the signer's key directory. See [Resource Attestation](/protocol/content-attestation/).
-Pricing is unit-agnostic: `unit_cost` replaces eCPT, `estimated_quantity` replaces `estimated_tokens`, and `Pricing.unit` specifies the metering unit. Your Exchange MUST support these fields on all offers.
+## Usage reports and disputes
-## Streaming Delivery
+`ExchangeService.ReportUsage` takes a report on a transaction your Exchange recorded and returns a `report_id`. An agent files a dispute with `ExchangeService.DisputeTransaction` at the Exchange that sold the item, and each `DisputeRequest` names the `report_id` of its usage report. The protocol standardizes the dispute's states and outcomes; how an Exchange decides a dispute is up to the Exchange. See [Dispute Resolution](/protocol/dispute-resolution/).
-FORA supports `DELIVERY_METHOD_STREAMING` for real-time connections (WebSocket, SSE, HLS, Icecast). Your Exchange generates a signed URL pointing to a streaming endpoint. The agent connects and receives continuous data. Stream mechanics (heartbeat, reconnection, concurrent connection limits) are managed by the provider, not the protocol.
+## Brokers
-Streaming transactions follow the same FORA flow, but the signed URL has a longer TTL (streaming sessions last minutes/hours) and usage is reported in time-based units (minutes, hours).
+An agent can buy from your Exchange directly or through a [Broker](/components/broker/overview/). A Broker sends your Exchange only the URLs it routes to you, never the agent's words, and returns your signed offers unchanged, each as a full package, in its own order of relevance. The agent decides which to buy. Your account holder is always the agent: a purchase through a Broker charges the agent's account at your Exchange, never the Broker's.
-## Next Steps
+## Next steps
-1. Review the [Exchange design](/components/exchange/overview/) for architecture details
-2. See the [Billing Adapter](/components/exchange/billing-adapter/) for the integration interface
-3. Walk through the [Scenario Walkthrough](/protocol/scenario-walkthrough/) for a complete transaction trace
-4. Review the [Threat Model](/security/threat-model/) -- it was built from 20 years of ad-tech fraud patterns
+1. Read the [Exchange deployment guide](https://github.com/FORA-Protocol/reference-implementation/blob/main/src/exchange/DEPLOYMENT.md) in the FORA Server repository.
+2. See [Publisher Onboarding](/getting-started/publisher-onboarding/) for what your publishers do.
+3. See [How Money Flows](/getting-started/how-money-flows/) for the billing chain and settlement.
+4. Review the [Threat Model](/security/threat-model/).
diff --git a/website/src/content/docs/getting-started/how-money-flows.mdx b/website/src/content/docs/getting-started/how-money-flows.mdx
index f9ef5dc6..cfe0b889 100644
--- a/website/src/content/docs/getting-started/how-money-flows.mdx
+++ b/website/src/content/docs/getting-started/how-money-flows.mdx
@@ -5,7 +5,7 @@ description: "The FORA billing chain, pricing models, unit_cost normalization, a
## The Billing Chain
-FORA never touches money. It follows the OpenRTB model: the protocol handles authorization and logging, while actual settlement happens outside the protocol through existing billing infrastructure.
+FORA never touches money. The protocol handles authorization and logging, while actual settlement happens outside the protocol through existing billing infrastructure.
The chain works like this:
@@ -124,7 +124,7 @@ The AI company pays for a subscription off-protocol. On-protocol, a subscription
## Overspend Prevention
-Two enforcement layers prevent overspend, mirroring how OpenRTB prevents advertiser overspend:
+Two enforcement layers prevent overspend:
- **Agent/Broker-side**: `RequestConstraints.max_unit_cost` -- the agent will not accept offers above this threshold. `BrokerService.Resolve` may filter out offers that would exceed the agent's budget (`max_price`, and `period_budget` for its `budget_scope`) and answers a URI left with none with `OFFER_ABSENCE_REASON_BUDGET_EXCEEDED`. How the budget is computed is the Broker's own behaviour, not part of the protocol. Resolve never charges.
- **Exchange-side**: The Exchange operator's Billing Adapter checks the requester's balance or credit before authorizing each item. An item the requester cannot afford is denied in the response body (`DENIAL_REASON_INSUFFICIENT_BALANCE`), also when it is the only item.
@@ -137,27 +137,27 @@ Here is a concrete transaction with dollar amounts.
**Setup:**
- Provider: *The Daily Meridian*, a mid-size tech publisher
-- Exchange: SSP-Alpha, which sells The Daily Meridian's catalog
+- Exchange: Exchange Alpha, which sells The Daily Meridian's catalog
- Article: "AI Regulation: What Providers Need to Know" (2,500 words, ~3,300 tokens)
- The Daily Meridian's RSL license: $0.08 per crawl
-- SSP-Alpha's price for the article: $0.05
-- Requester: Acme AI, whose agent has a registered account at SSP-Alpha (account handle `RegisterResponse.billing_ref`, here `acct_7f3e21c9` — an opaque value minted by the Exchange at registration, meaningless on its own)
-- Acme AI has an annual subscription to The Daily Meridian through SSP-Alpha
+- Exchange Alpha's price for the article: $0.05
+- Requester: Acme AI, whose agent has a registered account at Exchange Alpha (account handle `RegisterResponse.billing_ref`, here `acct_7f3e21c9` — an opaque value minted by the Exchange at registration, meaningless on its own)
+- Acme AI has an annual subscription to The Daily Meridian through Exchange Alpha
**What happens:**
| Step | Action | Cost |
|---|---|---|
-| 1 | Acme AI's agent queries SSP-Alpha via `DiscoverResources`, signed with its own key and carrying its delegation from Acme AI | $0 |
-| 2 | SSP-Alpha returns two offers: per-access ($0.05) and subscription ($0.00) | -- |
+| 1 | Acme AI's agent queries Exchange Alpha via `DiscoverResources`, signed with its own key and carrying its delegation from Acme AI | $0 |
+| 2 | Exchange Alpha returns two offers: per-access ($0.05) and subscription ($0.00) | -- |
| 3 | The agent selects the subscription offer (zero marginal cost) | $0.00 |
-| 4 | `ExecuteTransaction` -- SSP-Alpha verifies the delegation chain; the price is zero, so no Billing Adapter call and no `billing_id` | $0.00 |
+| 4 | `ExecuteTransaction` -- Exchange Alpha verifies the delegation chain; the price is zero, so no Billing Adapter call and no `billing_id` | $0.00 |
| 5 | Signed URL issued, the agent fetches the article from CDN | -- |
| 6 | Usage report filed: 3,150 actual tokens consumed | -- |
**Financial attribution:**
- `cost.amount`: $0.00 (subscription)
-- The annual subscription fee is settled off-protocol between Acme AI and SSP-Alpha
+- The annual subscription fee is settled off-protocol between Acme AI and Exchange Alpha
**Without the subscription**, the per-request path would have charged $0.05 for this article, with a `unit_cost` of $0.00001515 per token.
@@ -178,7 +178,7 @@ The protocol does not prescribe how credits are settled between Exchange operato
## Pricing Transparency
-A Broker's fee has no field. It is additive and disclosed out of band, never folded into the offer price the Exchange signed, so the agent sees what it pays for the resource and what it pays for brokerage (see [Selection Engine](/components/broker/selection-engine/)).
+A Broker's fee has no field. It is additive and disclosed out of band, never folded into the offer price the Exchange signed, so the agent sees what it pays for the resource and what it pays for brokerage (see [Broker: order, budget and fees](/components/broker/overview/#order-budget-and-fees)).
## Reconciliation
@@ -188,7 +188,7 @@ Three independent records ensure transaction integrity:
2. **Exchange transaction log** (Exchange operator controls): every transaction with its `billing_id` (none for a zero-price item), unit cost and currency, the requester, the signed offer and the agent's signed acceptance, with the public keys their Ed25519 signatures verify under
3. **Usage reports** (agent files): what the agent actually did with the resource (token count, function, citation)
-All three records must agree. Discrepancies are resolved offline, like ad-tech billing discrepancies.
+All three records must agree. Discrepancies are resolved offline, between the parties.
A provider registered on the operator's publisher console sees its sales there. "Overview" totals transactions, gross, the Exchange fee and net for a period. "Transactions" lists each sale, filterable by domain and by usage-report status, and "Verify" checks the sale's two Ed25519 signatures in the browser. "Income" shows daily totals, with "Download CSV". The console is the operator's tool, not part of the protocol. See [After setup](/getting-started/publisher-onboarding/#after-setup) in Publisher Onboarding.
diff --git a/website/src/content/docs/getting-started/industry-landscape.mdx b/website/src/content/docs/getting-started/industry-landscape.mdx
deleted file mode 100644
index 22021c25..00000000
--- a/website/src/content/docs/getting-started/industry-landscape.mdx
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: "Industry Landscape"
-description: "The current state of AI metered resource access: standards ecosystem, closed platforms, and where FORA fits in the timeline."
----
-
-## The robots.txt Era Is Ending
-
-For decades, `robots.txt` was the only interface between web crawlers and providers. It offered a binary choice: allow or block. For search engines, this was sufficient -- crawling led to indexing, which led to traffic back to the provider.
-
-AI changes this equation. When an LLM ingests content for RAG, grounding, or training, the provider gets no return traffic. The content's value is extracted without compensation. Providers are responding by blocking AI crawlers wholesale, but this sacrifices the discovery benefits that AI-powered search and assistants could provide.
-
-The industry needs transactional infrastructure -- a way to say "yes, you can use this content, for this price, under these terms."
-
-## The Standards Ecosystem
-
-Three complementary standards are emerging to fill this gap:
-
-### RSL 1.0 (Really Simple Licensing)
-
-Released December 2025. Like `robots.txt` but for licensing.
-
-- Provider links a license file at any URL, for example from a `License:` line in `robots.txt`, or embeds the license in a page, feed or media file
-- Machine-readable terms: attribution requirements, pay-per-crawl, pay-per-inference, training restrictions
-- 1,500+ media organizations endorsing
-- **Limitation**: Declares terms but provides no transaction infrastructure. An agent can read what content costs but has no way to pay for it through RSL alone.
-
-### IAB Tech Lab CoMP v1.0 (Content Monetization Protocol)
-
-Released March 2026, in public comment through April 2026.
-
-- Defines the **data model** for resource access: Package, AISystem, Retrieval, Scope objects
-- Provides a logging component for audit and invoicing
-- Backed by IAB Tech Lab (Prebid's parent organization) -- carries significant weight with SSPs and exchanges
-- **Limitation**: Deliberately leaves out billing, settlement, and transport. Defines what to describe but not how to transact.
-
-### FORA (Federated Open Resource Access)
-
-The open transaction protocol that completes the stack.
-
-- Adds discovery (`fora.json`), transaction execution, signed URL delivery, and usage reporting
-- Resource attestation (three verification levels) and automated dispute resolution
-- Provider onboarding where the `fora.json` a domain serves proves control of that domain
-- Layers on RSL (the publisher console reads a provider's RSL license to fill in its terms) and CoMP (wraps CoMP objects in transaction messages)
-- Multi-exchange architecture with an optional Broker for discovery across Exchanges
-
-## Closed Platforms
-
-Two proprietary approaches are operating today:
-
-### Microsoft Provider Content Exchange (PCM)
-
-Launched February 2026.
-
-- **Walled garden** -- Microsoft operates the exchange exclusively
-- Distinguishes **grounding** (per-request, real-time content for Copilot/Bing) from **training** (bulk licensing for model training)
-- "Pay per demonstrated value" -- providers receive compensation based on content performance metrics
-- Early partners: Associated Press, Vox Media, Conde Nast, Hearst, Business Insider
-- **Limitation**: Only works within Microsoft's ecosystem. A provider licensing through PCM cannot serve the same content to non-Microsoft AI systems through the same infrastructure.
-
-### TollBit
-
-Startup with $7M in funding, operational today.
-
-- Running per-request content licensing in production
-- Per-1000-pages pricing, providers set their own rates
-- Charges AI customers a transaction fee but does not take a provider revenue share
-- **Limitation**: Proprietary API. Providers and AI companies are locked into TollBit's infrastructure. No interoperability with other licensing systems.
-
-## Why Open Standards Matter
-
-The ad-tech industry learned this lesson two decades ago. Before OpenRTB, every ad exchange had its own proprietary protocol. Advertisers and providers had to build custom integrations for each exchange, creating lock-in and fragmentation.
-
-OpenRTB changed this by defining a common protocol that any exchange, DSP, or SSP could implement. The result: a liquid market where requesters and providers could transact across any compliant exchange.
-
-AI resource access is at the same inflection point. Microsoft PCM and TollBit are building walled gardens -- the equivalent of pre-OpenRTB proprietary exchanges. FORA aims to be the OpenRTB for resource access: an open protocol that any Exchange, AI company, or provider can implement.
-
-## Comparison
-
-| Layer | RSL | CoMP | Microsoft PCM | TollBit | FORA |
-|---|---|---|---|---|---|
-| Terms declaration | RSL license | Package object | Provider dashboard | Provider dashboard | Publisher console, filled in from the RSL license |
-| Discovery | `robots.txt`, `Link` header, HTML, RSS or file metadata | Not defined | Microsoft index | TollBit API | `fora.json` + edge function fallback |
-| Transaction protocol | None | Not defined | Proprietary | Proprietary | **Open protocol** |
-| Content verification | None | None | Not defined | Not defined | **Three-level attestation** |
-| Dispute resolution | None | None | Not defined | Not defined | **Automated (three-tier)** |
-| Billing/settlement | None | Out of scope | Microsoft handles | TollBit handles | Billing adapter (pluggable) |
-| Multi-exchange | No | Implied | No (Microsoft only) | No (TollBit only) | **Yes (Broker)** |
-| Domain extension profiles | None | None | None | None | **Three profiles (news, academic, legal)** |
-
-## Three-Layer Governance
-
-FORA v1.0 prevents protocol fragmentation through a three-layer governance model:
-
-| Layer | Scope | Governance | Example |
-|---|---|---|---|
-| **1. Core Proto** | Fields in `fora.proto` | Protocol version bump | `resource_mutability`, `data_as_of` |
-| **2. Standard Extensions** | `fora.*` namespace in ext | Defined in FORA spec | `fora.compliance.dua_required` |
-| **3. Domain Profiles** | Domain namespace in ext | Published by domain communities | `news.iptc_guid`, `academic.doi` |
-
-Three domain extension profiles ship with v1.0: `fora-news-v1` (news, podcasts, broadcasting), `fora-academic-v1` (scholarly articles, preprints, datasets), and `fora-legal-v1` (legislation, case law, patents). Each profile is grounded in existing industry standards (IPTC NewsML-G2, CrossRef/OpenAlex, ELI/ECLI/Akoma Ntoso).
-
-Exchanges declare conformance via `supported_profiles` in their manifest. Agents declare which profiles they understand in the request. A Broker forwards the agent's declaration to each Exchange it queries and does not route by it; an Exchange that supports `fora-legal-v1` answers a legal research agent with that profile's fields.
-
-## Scope Boundary
-
-FORA v1.0 draws a clear boundary: **resource access is in scope; job execution is not.**
-
-The test: "Does the resource exist before the transaction?" If yes, it is a FORA use case. If the transaction creates something new from agent input (translation, ML inference, document generation), it is not.
-
-**In scope:** static resources (articles, papers, patents), dynamic resources (credit reports, drug databases), streaming resources (quote feeds, live broadcasts), database lookups (drug interaction queries).
-
-**Out of scope:** translation, ML inference, document generation. A Exchange offering these should use a different protocol. However, a pre-computed translation database (translations as resources) is a valid FORA use case.
-
-## Timeline
-
-| Date | Event |
-|---|---|
-| December 2025 | RSL 1.0 released, 1,500+ providers endorsing |
-| February 2026 | Microsoft PCM launched with initial provider partners |
-| March 2026 | IAB CoMP v1.0 released for public comment |
-| March 2026 | FORA v1.0: metering generalization, streaming delivery, content mutability, extension profiles, CoMP alignment |
-| April 2026 | IAB CoMP public comment period closes |
-
-## The Window for Open Standards
-
-Three forces create urgency:
-
-1. **IAB CoMP is being defined now** -- the public comment period closes April 2026. The industry is actively shaping the data model. FORA builds on CoMP, so alignment matters.
-2. **Walled gardens are growing** -- Microsoft and TollBit are signing providers to exclusive or preferred deals. Each provider locked into a proprietary system is one fewer participant in an open market.
-3. **AI traffic doubles quarterly** -- every month without monetization infrastructure represents lost revenue for providers and growing legal risk for AI companies operating without clear licensing.
-
-## Next Steps
-
-- [What Is FORA?](/getting-started/what-is-fora/) -- protocol overview and how it works
-- [Standards Layering](/protocol/standards-layering/) -- technical detail on how RSL, CoMP, and FORA interoperate
-- [Discovery Paths](/protocol/discovery-paths/) -- how agents find and enter the FORA flow
diff --git a/website/src/content/docs/getting-started/what-is-fora.mdx b/website/src/content/docs/getting-started/what-is-fora.mdx
index c331173f..0706bf63 100644
--- a/website/src/content/docs/getting-started/what-is-fora.mdx
+++ b/website/src/content/docs/getting-started/what-is-fora.mdx
@@ -25,7 +25,7 @@ An agent buys access to a resource from an Exchange, directly or through an opti
**For resource providers:** Expose your catalog through an Exchange. Set your price. Get paid per access. No custom integrations per consumer.
-**For Exchange operators:** Aggregate provider catalogs. Handle transactions. Earn a margin. Compete on coverage, quality, and price.
+**For Exchange operators:** Run an Exchange on FORA Server, which is open source. Hold your providers' catalogs and terms, sign their offers and record each sale, under your own rules and fees. Every FORA agent can open an account and buy from it.
## How It Works
@@ -155,15 +155,16 @@ FORA covers **metered access to resources that exist**. The test: "Does the reso
| Streaming resources (quote feeds, live audio) | Compute services |
| Database lookups (drug interactions, property records) | |
-## What Exists Today
+## What FORA Is Made Of
- **The wire format**: the `fora.v1` and `fora.admin.v1` protobuf packages, with a [JSON Schema](/reference/json-schemas/) for each message. See [Proto: FORA v1](/reference/proto-fora/).
- **SDKs in three languages**: {PACKAGES.go.coordinate} for Go, {PACKAGES.ts.coordinate} on npm and {PACKAGES.python.coordinate} on PyPI.
- **Six extension profiles**: [news](/protocol/ext-news/), [academic](/protocol/ext-academic/), [legal](/protocol/ext-legal/), [CoMP](/protocol/ext-comp/), [C2PA](/protocol/ext-c2pa/) and [music](/protocol/ext-music/).
-- **Two live demos** on a demo Exchange. In [First License](/getting-started/poc-walkthrough/), an agent buys a license to an article whose site refuses its direct request. In [Music](/getting-started/live-demo-music/), an agent buys two different licenses to the same track.
-- **FORA Server**: an [open-source implementation](https://github.com/FORA-Protocol/reference-implementation) of the Exchange, the Broker, an identity service with an MCP adapter, and the edge function.
+- **FORA Server**: an [open-source implementation](https://github.com/FORA-Protocol/reference-implementation) of the Exchange, the Broker, the Identity Service with its MCP endpoint, and the edge function. Anyone can run it.
- **The standards it builds on**: IAB Tech Lab's CoMP V1 is mapped field for field and carried as the `fora-comp-v1` profile. The RSL 1.0 AI-use terms seed FORA's restriction vocabulary. See [Standards Layering](/protocol/standards-layering/).
+Two live demos run on a demo Exchange. In [First License](/getting-started/poc-walkthrough/), an agent buys a license to an article whose site refuses its direct request. In [Music](/getting-started/live-demo-music/), an agent buys two different licenses to the same track.
+
## Next Steps
- [For Resource Providers](/getting-started/for-providers/) — how to expose your resources through FORA
diff --git a/website/src/content/docs/index.mdx b/website/src/content/docs/index.mdx
index 90424e62..40d3da44 100644
--- a/website/src/content/docs/index.mdx
+++ b/website/src/content/docs/index.mdx
@@ -38,7 +38,7 @@ import { Card, CardGrid, LinkCard } from '@astrojs/starlight/components';
Where an operator runs a publisher console, name your business, add your domain and connect your site: one generated file on your site and one package on your CDN. No keys to generate, no catalog to push.
- No walled gardens. Exchange operators, providers, and third parties operate Exchanges. A Broker brings their offers to the agent in one answer.
+ Anyone can run an Exchange: an operator, a provider or a third party. A Broker brings their offers to the agent in one answer.
Zero-SDK resource access. Add the FORA MCP server to any MCP-capable agent and discover, transact, and dispute resources without custom integration.
@@ -49,7 +49,7 @@ import { Card, CardGrid, LinkCard } from '@astrojs/starlight/components';
- [What is FORA?](/getting-started/what-is-fora/) -- [How Money Flows](/getting-started/how-money-flows/) -- [Industry Landscape](/getting-started/industry-landscape/)
+ [What is FORA?](/getting-started/what-is-fora/) -- [How Money Flows](/getting-started/how-money-flows/) -- [Content marketplaces](/resources/content-marketplaces/) -- [The standards map](/resources/standards-map/)
[Transaction Flow](/protocol/transaction-flow/) -- [Discovery Paths](/protocol/discovery-paths/) -- [Authentication](/protocol/authentication/)
diff --git a/website/src/content/docs/protocol/discovery-paths.mdx b/website/src/content/docs/protocol/discovery-paths.mdx
index 12abd94f..aa390275 100644
--- a/website/src/content/docs/protocol/discovery-paths.mdx
+++ b/website/src/content/docs/protocol/discovery-paths.mdx
@@ -29,7 +29,7 @@ sequenceDiagram
Agent->>PUB: GET /.well-known/fora.json
PUB-->>Agent: WellKnownManifest (role=ROLE_PUBLISHER, exchange endpoints)
- Note over Agent: Content at /premium/* requires licensed access via exchange.ssp.com
+ Note over Agent: Content at /premium/* requires licensed access via exchange.example
Agent->>MP: DiscoverResources (ResourceQuery)
MP-->>Agent: ResourceResponse (Offer[] with pricing)
diff --git a/website/src/content/docs/protocol/scenario-walkthrough.mdx b/website/src/content/docs/protocol/scenario-walkthrough.mdx
index 3ba71aad..bc3bd454 100644
--- a/website/src/content/docs/protocol/scenario-walkthrough.mdx
+++ b/website/src/content/docs/protocol/scenario-walkthrough.mdx
@@ -9,8 +9,8 @@ description: "End-to-end FORA v1.0 walkthrough: provider setup, agent request, s
**Agent**: Anthropic's Claude (`claude.ai`), running the FORA Agent SDK
**Broker**: Anthropic's hosted Broker (`broker.anthropic.com`)
-**Subscription**: Anthropic has an annual deal with Hearst Media via SSP-Alpha exchange
-**Request**: Claude needs an article about AI regulation originally published by Hearst's TechCrunch (`techcrunch.com`), syndicated to The Verge (`theverge.com`) via SSP-Beta exchange
+**Subscription**: Anthropic has an annual deal with Hearst Media via Exchange Alpha
+**Request**: Claude needs an article about AI regulation originally published by Hearst's TechCrunch (`techcrunch.com`), syndicated to The Verge (`theverge.com`) via Exchange Beta
**Extension Profiles**: Both Exchanges declare `supported_profiles: ["fora-news-v1"]` in their manifests. The Broker forwards `supported_profiles` from the agent to enable profile-aware metadata in offers (e.g., `news.iptc_guid`, `news.correction_status`).
---
@@ -48,8 +48,8 @@ Before any agent request, providers configure their domains and Exchanges ingest
"contact": "licensing@hearst.com",
"exchanges": [
{
- "domain": "exchange.ssp-alpha.com",
- "endpoint": "https://exchange.ssp-alpha.com/fora/v1",
+ "domain": "exchange.alpha.example",
+ "endpoint": "https://exchange.alpha.example/fora/v1",
"relationship": "PROVIDER_RELATIONSHIP_DIRECT"
}
]
@@ -114,15 +114,15 @@ The Broker announces its key in its own WBA directory the same way:
}
```
-### 0c. SSP-Alpha Resource Ingestion
+### 0c. Exchange Alpha Resource Ingestion
-SSP-Alpha's Resource Ingestion Pipeline runs in the background:
+Exchange Alpha's Resource Ingestion Pipeline runs in the background:
```
1. Crawl techcrunch.com/sitemap.xml -> discover all /premium/* URLs
2. Fetch the RSL license robots.txt names -> extract permits/prohibits and its rate ($0.08/crawl), Hearst's cap
3. HTML crawl via readability -> extract text -> word count -> estimate tokens
-4. Apply Hearst's private pricing (from SSP-Alpha config DB): $0.05/article
+4. Apply Hearst's private pricing (from Exchange Alpha config DB): $0.05/article
(Below the RSL ceiling of $0.08 — compliant)
5. Third-party attestation (GumGum via CatalogService.PushResources):
GumGum crawls the article, signs attestation claims with Ed25519:
@@ -168,31 +168,31 @@ SSP-Alpha's Resource Ingestion Pipeline runs in the background:
7. Compile into radix trie -> serialize to catalog.bin -> Exchange loads via atomic pointer swap
```
-SSP-Alpha also knows about Anthropic's subscription, looked up by Anthropic's account handle (minted at registration):
+Exchange Alpha also knows about Anthropic's subscription, looked up by Anthropic's account handle (minted at registration):
```
BillingAdapter.CheckSubscription("acct_7f3e21c9", "hearst-media")
-> { subscription_id: "SUB-ANTHROPIC-HEARST-2026", active: true, quota_remaining: 850000 }
```
-### 0d. The Verge Syndication via SSP-Beta
+### 0d. The Verge Syndication via Exchange Beta
```
1. The Verge reprinted the TechCrunch article (syndication deal):
theverge.com/premium/ai-regulation-republish.html
-2. The Verge has fora.json pointing to SSP-Beta:
+2. The Verge has fora.json pointing to Exchange Beta:
{
"ver": "1.0",
"provider": "theverge.com",
"exchanges": [{
- "domain": "exchange.ssp-beta.com",
- "endpoint": "https://exchange.ssp-beta.com/fora/v1",
+ "domain": "exchange.beta.example",
+ "endpoint": "https://exchange.beta.example/fora/v1",
"relationship": "PROVIDER_RELATIONSHIP_DIRECT"
}]
}
-3. SSP-Beta's ingestion pipeline:
+3. Exchange Beta's ingestion pipeline:
- Discovers the article, estimates 3100 tokens
- The Verge's pricing: $0.07/article (higher than TechCrunch, below RSL ceiling)
- Identity: same iptc_guid (syndicated from same TechCrunch wire)
@@ -204,7 +204,7 @@ BillingAdapter.CheckSubscription("acct_7f3e21c9", "hearst-media")
resource_mutability: RESOURCE_MUTABILITY_STATIC
}
- Attestations: [{ verifier: "gumgum.com", claims: { estimated_quantity: 3100, word_count: 2350 } }]
- - Anthropic has NO subscription with SSP-Beta
+ - Anthropic has NO subscription with Exchange Beta
```
---
@@ -227,8 +227,8 @@ Step 1: Parse domain -> "techcrunch.com"
Step 2: ExchangeRegistry lookup
- Cache miss for techcrunch.com
- Background: fetch https://techcrunch.com/.well-known/fora.json
- - Discovers: exchange.ssp-alpha.com is authorized (PROVIDER_RELATIONSHIP_DIRECT)
- - Caches: techcrunch.com -> [ssp-alpha]
+ - Discovers: exchange.alpha.example is authorized (PROVIDER_RELATIONSHIP_DIRECT)
+ - Caches: techcrunch.com -> [exchange.alpha.example]
Step 3: Prepare RFC 9421 HTTP Message Signature (alg=ed25519)
- requester.id = "claude-agent-001"
@@ -251,13 +251,13 @@ Step 3: Prepare RFC 9421 HTTP Message Signature (alg=ed25519)
## Phase 2: Supply Discovery (Requester Identity, Subscription Detection, Content Attestations, Ed25519 Verification)
-The SDK sends `DiscoverResources` to SSP-Alpha — `POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/DiscoverResources`:
+The SDK sends `DiscoverResources` to Exchange Alpha — `POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/DiscoverResources`:
{/* fora-validate: ResourceQuery */}
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"requester": {
"id": "claude-agent-001",
"domain": "claude.ai",
@@ -270,7 +270,7 @@ The SDK sends `DiscoverResources` to SSP-Alpha — `POST https://exchange.ssp-al
}
```
-### Inside SSP-Alpha's Exchange
+### Inside Exchange Alpha
```
1. Validate request (proto validation) -> pass
@@ -341,11 +341,11 @@ The SDK sends `DiscoverResources` to SSP-Alpha — `POST https://exchange.ssp-al
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"offers": [
{
"offer_id": "2325749d-50d3-431a-ac34-900d443ee88e",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"title": "AI Regulation: What Providers Need to Know",
"pricing": {
"model": "PRICING_MODEL_PER_UNIT",
@@ -389,7 +389,7 @@ The SDK sends `DiscoverResources` to SSP-Alpha — `POST https://exchange.ssp-al
},
{
"offer_id": "4f155204-a53e-42aa-8471-154f87d7d3d5",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"title": "AI Regulation: What Providers Need to Know",
"pricing": {
"model": "PRICING_MODEL_FREE",
@@ -463,7 +463,7 @@ If Anthropic uses its hosted Broker instead of the SDK directly, the Broker prov
],
"acceptable_restrictions": [{ "axis": "RESTRICTION_KIND_FUNCTION", "values": ["ai-input"] }],
"constraints": {
- "preferred_exchanges": ["exchange.ssp-alpha.com"],
+ "preferred_exchanges": ["exchange.alpha.example"],
"max_unit_cost": "0.00005",
"reporting_capable": true,
"budget_scope": "team:claude-rag",
@@ -479,13 +479,13 @@ Discovery through the Broker is Broker-led: the agent asked the Broker, and the
1. Carries the agent's `requester` message, naming as `requester.domain` the host of the directory the agent's signature verified against (`claude.ai`, as the agent sent it)
2. Signs the query alone, with its own labeled RFC 9421 HTTP Message Signature covering its own request components and only its own `Signature-Agent` member. The query carries no agent signature headers
-Broker → SSP-Alpha (multi-URI batch query) — `POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/DiscoverResources`:
+Broker → Exchange Alpha (multi-URI batch query) — `POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/DiscoverResources`:
{/* fora-validate: ResourceQuery */}
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"requester": {
"id": "claude-agent-001",
"domain": "claude.ai",
@@ -501,21 +501,21 @@ Broker → SSP-Alpha (multi-URI batch query) — `POST https://exchange.ssp-alph
}
```
-SSP-Alpha's Exchange verifies the Broker's signature -- it looks up the public key by its `keyid` thumbprint in the key directory named by the Broker's `Signature-Agent` member, Ed25519 verifies, and authenticates the caller as the Broker. The query carries no delegation, and the Exchange would not honour one: nothing on a query the Broker signs alone can pass its holder binding. How an agent proves a holder-of-key entitlement at discovery time through a Broker is an open protocol question. A discovery query moves no money, so it carries no agent consent; see [Multi-hop forwarding](/protocol/authentication/#multi-hop-forwarding).
+Exchange Alpha verifies the Broker's signature -- it looks up the public key by its `keyid` thumbprint in the key directory named by the Broker's `Signature-Agent` member, Ed25519 verifies, and authenticates the caller as the Broker. The query carries no delegation, and the Exchange would not honour one: nothing on a query the Broker signs alone can pass its holder binding. How an agent proves a holder-of-key entitlement at discovery time through a Broker is an open protocol question. A discovery query moves no money, so it carries no agent consent; see [Multi-hop forwarding](/protocol/authentication/#multi-hop-forwarding).
-SSP-Alpha returns `offer_groups` (batch mode -- multiple URIs in query):
+Exchange Alpha returns `offer_groups` (batch mode -- multiple URIs in query):
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"offer_groups": [
{
"uri": "https://techcrunch.com/premium/ai-regulation-2026.html",
"offers": [
{
"offer_id": "2325749d-50d3-431a-ac34-900d443ee88e",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.05", "currency": "USD", "unit": "accesses", "unit_cost": "0.00001515", "estimated_quantity": 1 },
"identity": { "canonical_url": "https://techcrunch.com/premium/ai-regulation-2026.html", "iptc_guid": "urn:newsml:techcrunch:20260315:ai-reg-001", "content_hash": "a1b2c3d4e5f6...", "hash_method": "simhash-v1" },
"attestations": [{ "verifier": "gumgum.com", "claims": { "estimated_quantity": 3300, "word_count": 2500 }, "signature": "..." }],
@@ -529,7 +529,7 @@ SSP-Alpha returns `offer_groups` (batch mode -- multiple URIs in query):
},
{
"offer_id": "4f155204-a53e-42aa-8471-154f87d7d3d5",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"pricing": { "model": "PRICING_MODEL_FREE", "rate": "0", "currency": "USD", "unit_cost": "0", "estimated_quantity": 3300 },
"subscription_id": "SUB-ANTHROPIC-HEARST-2026",
"identity": { "canonical_url": "https://techcrunch.com/premium/ai-regulation-2026.html", "iptc_guid": "urn:newsml:techcrunch:20260315:ai-reg-001", "content_hash": "a1b2c3d4e5f6...", "hash_method": "simhash-v1" },
@@ -554,17 +554,17 @@ SSP-Alpha returns `offer_groups` (batch mode -- multiple URIs in query):
}
```
-Note: SSP-Alpha returns an empty `offers` array for the `theverge.com` URI with `absence_reason: NOT_IN_CATALOG` because The Verge is not an SSP-Alpha tenant. This v1.0 diagnostic lets the Broker distinguish "not in catalog" from "resource blocked for your use case." The Broker also queries SSP-Beta:
+Note: Exchange Alpha returns an empty `offers` array for the `theverge.com` URI with `absence_reason: NOT_IN_CATALOG` because The Verge is not an Exchange Alpha tenant. This v1.0 diagnostic lets the Broker distinguish "not in catalog" from "resource blocked for your use case." The Broker also queries Exchange Beta:
```json
-// SSP-Beta returns (single-URI, flat offers):
+// Exchange Beta returns (single-URI, flat offers):
{
"ver": "1.0",
- "exchange": "exchange.ssp-beta.com",
+ "exchange": "exchange.beta.example",
"offers": [
{
"offer_id": "ecb6fef4-1d83-4751-ab92-b3bc7c2fee39",
- "exchange": "exchange.ssp-beta.com",
+ "exchange": "exchange.beta.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.07", "currency": "USD", "unit": "accesses", "unit_cost": "0.00002258", "estimated_quantity": 1 },
"identity": {
"canonical_url": "https://theverge.com/premium/ai-regulation-republish.html",
@@ -595,8 +595,8 @@ Step 1: Group by iptc_guid
- These are ALL the same underlying article (TechCrunch original, syndicated to The Verge)
Step 2: SimHash cross-check (for non-news content without IPTC guids)
- - SSP-Alpha hash: "a1b2c3d4e5f6..." (simhash-v1)
- - SSP-Beta hash: "a1b2c3d4e5f7..." (simhash-v1)
+ - Exchange Alpha hash: "a1b2c3d4e5f6..." (simhash-v1)
+ - Exchange Beta hash: "a1b2c3d4e5f7..." (simhash-v1)
- Hamming distance = 1 bit -> substantially similar (threshold < 3 bits)
- For 99% of web content that lacks IPTC guids, SimHash is the primary dedup signal.
The Exchange computes SimHash during ingestion from extracted article text.
@@ -609,11 +609,11 @@ Step 2: SimHash cross-check (for non-news content without IPTC guids)
```
Step 3: Order within the content group
The Broker keeps all three offers, each as the full package its Exchange
- signed, and puts them in its order of relevance. The agent named SSP-Alpha
- in preferred_exchanges, so SSP-Alpha's offers come first:
- 1. 4f155204-a53e-42aa-8471-154f87d7d3d5 ($0, subscription, SSP-Alpha, attested by gumgum.com)
- 2. 2325749d-50d3-431a-ac34-900d443ee88e ($0.05, per-request, SSP-Alpha, attested by gumgum.com)
- 3. ecb6fef4-1d83-4751-ab92-b3bc7c2fee39 ($0.07, per-request, SSP-Beta, attested by gumgum.com)
+ signed, and puts them in its order of relevance. The agent named Exchange Alpha
+ in preferred_exchanges, so Exchange Alpha's offers come first:
+ 1. 4f155204-a53e-42aa-8471-154f87d7d3d5 ($0, subscription, Exchange Alpha, attested by gumgum.com)
+ 2. 2325749d-50d3-431a-ac34-900d443ee88e ($0.05, per-request, Exchange Alpha, attested by gumgum.com)
+ 3. ecb6fef4-1d83-4751-ab92-b3bc7c2fee39 ($0.07, per-request, Exchange Beta, attested by gumgum.com)
Price is not part of the order. The agent compares the packages itself.
@@ -628,7 +628,7 @@ Step 4: Budget filter (applied before the offers are returned)
### The Agent Chooses
-The agent gets all three offers and decides by its own policy: use its subscription where it covers the content, and prefer third-party attested content. It chooses `4f155204-a53e-42aa-8471-154f87d7d3d5`, the subscription offer from SSP-Alpha, at zero marginal cost and attested by gumgum.com.
+The agent gets all three offers and decides by its own policy: use its subscription where it covers the content, and prefer third-party attested content. It chooses `4f155204-a53e-42aa-8471-154f87d7d3d5`, the subscription offer from Exchange Alpha, at zero marginal cost and attested by gumgum.com.
---
@@ -638,7 +638,7 @@ The agent commits to the subscription offer, directly with the SDK or through th
### Direct (SDK) request -- single signature in the headers:
-`POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/ExecuteTransaction`
+`POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/ExecuteTransaction`
{/* fora-validate: TransactionRequest */}
```json
@@ -655,7 +655,7 @@ The agent commits to the subscription offer, directly with the SDK or through th
{
"offer": {
"offer_id": "4f155204-a53e-42aa-8471-154f87d7d3d5",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"title": "AI Regulation: What Providers Need to Know",
"pricing": {
"model": "PRICING_MODEL_FREE",
@@ -693,9 +693,9 @@ The agent commits to the subscription offer, directly with the SDK or through th
### Orchestrated request -- bought through the Broker:
-The agent sends the purchase to the Broker, `POST https://broker.example/fora.v1.BrokerService/ExecuteTransaction`, signed for the Broker's URL. The Broker re-packages it and sends SSP-Alpha's Exchange its own sub-request:
+The agent sends the purchase to the Broker, `POST https://broker.example/fora.v1.BrokerService/ExecuteTransaction`, signed for the Broker's URL. The Broker re-packages it and sends Exchange Alpha its own sub-request:
-`POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/ExecuteTransaction`
+`POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/ExecuteTransaction`
{/* fora-validate: TransactionRequest */}
```json
@@ -712,7 +712,7 @@ The agent sends the purchase to the Broker, `POST https://broker.example/fora.v1
{
"offer": {
"offer_id": "4f155204-a53e-42aa-8471-154f87d7d3d5",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"title": "AI Regulation: What Providers Need to Know",
"pricing": {
"model": "PRICING_MODEL_FREE",
@@ -748,9 +748,9 @@ The agent sends the purchase to the Broker, `POST https://broker.example/fora.v1
}
```
-The sub-request body carries SSP-Alpha's items exactly as the agent signed them, with the agent's `agent_acceptance` on each item, its `agent_request_acceptance`, its `requester` and its `idempotency_key` unchanged. The Broker re-packaged this request for SSP-Alpha and signs it alone, with its own labeled RFC 9421 signature covering its own request components and only its own `Signature-Agent` member. The Exchange authenticates the caller as the Broker (its public key selected by `keyid` thumbprint in the directory the Broker's `Signature-Agent` member names). The agent's identity and consent are verified from the body: each `agent_acceptance` is a detached Ed25519 signature over `{offer_sig, requester_id, requester_domain, idempotency_key}`, which the Exchange verifies against the agent's registered key, resolved from `requester.domain` (`claude.ai/.well-known/http-message-signatures-directory`), and the request acceptance proves these items are the complete in-order set addressed to SSP-Alpha. That key also gives the delivery-URL binding, and a delegation's `cnf.jkt` would be checked against it. The Broker returns SSP-Alpha's answer to the agent inside a `BrokerTransactionResponse`, alongside the results of any other Exchange in the same purchase.
+The sub-request body carries Exchange Alpha's items exactly as the agent signed them, with the agent's `agent_acceptance` on each item, its `agent_request_acceptance`, its `requester` and its `idempotency_key` unchanged. The Broker re-packaged this request for Exchange Alpha and signs it alone, with its own labeled RFC 9421 signature covering its own request components and only its own `Signature-Agent` member. The Exchange authenticates the caller as the Broker (its public key selected by `keyid` thumbprint in the directory the Broker's `Signature-Agent` member names). The agent's identity and consent are verified from the body: each `agent_acceptance` is a detached Ed25519 signature over `{offer_sig, requester_id, requester_domain, idempotency_key}`, which the Exchange verifies against the agent's registered key, resolved from `requester.domain` (`claude.ai/.well-known/http-message-signatures-directory`), and the request acceptance proves these items are the complete in-order set addressed to Exchange Alpha. That key also gives the delivery-URL binding, and a delegation's `cnf.jkt` would be checked against it. The Broker returns Exchange Alpha's answer to the agent inside a `BrokerTransactionResponse`, alongside the results of any other Exchange in the same purchase.
-### Inside SSP-Alpha's Exchange
+### Inside Exchange Alpha
```
1. Validate request (proto validation) -> pass
@@ -885,13 +885,13 @@ CDN access log records:
The SDK auto-submits a usage report (background, non-blocking). Usage reporting is mandatory for subscription transactions -- failure to report within the window triggers `DENIAL_REASON_REPORTING_OVERDUE` on subsequent transactions.
-`POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/ReportUsage`
+`POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/ReportUsage`
{/* fora-validate: UsageReport */}
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"idempotency_key": "ur-claude-001",
"transaction_id": "txn-alpha-001",
"billing_id": "bill-sub-alpha-001",
@@ -949,7 +949,7 @@ Three independent records that must agree:
- url_hash=9f2c7a4e... fetched at 15:25:00, 200 OK, 45KB
- agent_id=NzbLsXh8..., signature and agent binding verified by the edge
-2. Exchange transaction log (SSP-Alpha controls):
+2. Exchange transaction log (Exchange Alpha controls):
- txn-alpha-001: signed_url_hash=9f2c7a4e... (the join key to the log above)
- subscription SUB-ANTHROPIC-HEARST-2026, amount=$0
- subscription_unit_value: $0.05 (value of the access for accounting)
@@ -978,7 +978,7 @@ PASS: Citation included as required by the Offer's attribution terms
Hearst queries the Exchange's provider audit API to independently verify all transactions for their content:
```
-GET https://exchange.ssp-alpha.com/provider/techcrunch.com/transactions
+GET https://exchange.alpha.example/provider/techcrunch.com/transactions
?from=2026-03-15T00:00:00Z
&to=2026-03-16T00:00:00Z
```
@@ -993,7 +993,7 @@ Response includes signed Offer snapshots for every transaction:
"billing_id": "bill-sub-alpha-001",
"offer_snapshot": {
"offer_id": "4f155204-a53e-42aa-8471-154f87d7d3d5",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"pricing": { "model": "PRICING_MODEL_FREE", "rate": "0", "currency": "USD" },
"subscription_id": "SUB-ANTHROPIC-HEARST-2026",
"terms": [
@@ -1015,11 +1015,11 @@ Response includes signed Offer snapshots for every transaction:
**What Hearst can verify**:
-1. **Offer authenticity**: Hearst verifies the `exchange_signature` on each `offer_snapshot` using SSP-Alpha's published Ed25519 public key (fetch SSP-Alpha's WBA directory at `exchange.ssp-alpha.com/.well-known/http-message-signatures-directory` and read its `keys`). This proves the Exchange actually issued this Offer -- it cannot deny having offered these terms.
+1. **Offer authenticity**: Hearst verifies the `exchange_signature` on each `offer_snapshot` using Exchange Alpha's published Ed25519 public key (fetch Exchange Alpha's WBA directory at `exchange.alpha.example/.well-known/http-message-signatures-directory` and read its `keys`). This proves the Exchange actually issued this Offer -- it cannot deny having offered these terms.
2. **RSL price ceiling compliance**: Hearst's RSL declares a maximum rate of $0.08/crawl. The subscription's `subscription_unit_value` of $0.05 is below this ceiling. If any per-request Offer exceeded $0.08, Hearst would detect it by comparing `offer_snapshot.pricing.rate` against their RSL terms.
-3. **Private floor compliance**: Hearst's contract with SSP-Alpha specifies a private minimum rate of $0.04/article. The `subscription_unit_value` of $0.05 is above this floor. Private floor pricing is contractual (not protocol-enforced), but the audit data makes violations detectable.
+3. **Private floor compliance**: Hearst's contract with Exchange Alpha specifies a private minimum rate of $0.04/article. The `subscription_unit_value` of $0.05 is above this floor. Private floor pricing is contractual (not protocol-enforced), but the audit data makes violations detectable.
### What Hearst Sees (Subscription Summary)
@@ -1059,7 +1059,7 @@ But if Hamming distance > threshold, or content is entirely different:
### Dispute Request
```json
-POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/DisputeTransaction
+POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/DisputeTransaction
{
"ver": "1.0",
@@ -1090,14 +1090,14 @@ Three-tier resolution: Tier 1 automated (<1s, auto-disputable claims like CDN
## What the Broker Adds (Cross-Provider Intelligence)
-**Without Broker (SDK only)**: the agent found the article via SSP-Alpha (from `fora.json`) and got the subscription deal. It never knew The Verge also had the article at $0.07 via SSP-Beta.
+**Without Broker (SDK only)**: the agent found the article via Exchange Alpha (from `fora.json`) and got the subscription deal. It never knew The Verge also had the article at $0.07 via Exchange Beta.
**With Broker**: the Broker queried both Exchanges, matched the same article via iptc_guid (confirmed by SimHash similarity) and returned every offer with its attestation data. The agent still chose the subscription offer -- but now Anthropic has intelligence:
```
"This article is available from two sources:
- - SSP-Alpha (TechCrunch, subscription, $0/request, third-party attested by gumgum.com)
- - SSP-Beta (The Verge, per-request, $0.07/request, third-party attested by gumgum.com)
+ - Exchange Alpha (TechCrunch, subscription, $0/request, third-party attested by gumgum.com)
+ - Exchange Beta (The Verge, per-request, $0.07/request, third-party attested by gumgum.com)
Our subscription saves us $0.07 per request from the alternative source.
At 10K requests/month for this provider's content, that's $700/month
diff --git a/website/src/content/docs/protocol/standards-layering.mdx b/website/src/content/docs/protocol/standards-layering.mdx
index 66ef79e9..58acbfc4 100644
--- a/website/src/content/docs/protocol/standards-layering.mdx
+++ b/website/src/content/docs/protocol/standards-layering.mdx
@@ -300,8 +300,8 @@ An Exchange serves its `fora.json` (`role=ROLE_EXCHANGE`) declaring:
],
"exchanges": [
{
- "domain": "exchange.ssp-example.com",
- "endpoint": "https://exchange.ssp-example.com/fora/v1",
+ "domain": "exchange.example",
+ "endpoint": "https://exchange.example/fora/v1",
"relationship": "DIRECT"
}
]
diff --git a/website/src/content/docs/protocol/transaction-flow.mdx b/website/src/content/docs/protocol/transaction-flow.mdx
index 426bed73..ddfb93fc 100644
--- a/website/src/content/docs/protocol/transaction-flow.mdx
+++ b/website/src/content/docs/protocol/transaction-flow.mdx
@@ -44,7 +44,7 @@ Content-Type: application/json
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"requester": {
"id": "research-bot",
"domain": "buyer.example.com",
@@ -70,11 +70,11 @@ Key fields:
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"offers": [
{
"offer_id": "9d5735d7-1f17-4801-8dcf-7cac0b7b32b0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"title": "The Future of AI Infrastructure",
"ext": {
"comp.package_id": "PKG-TC-AI-INFRA",
@@ -147,14 +147,14 @@ When requesting multiple URIs, the response uses `offer_groups` instead of `offe
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"offer_groups": [
{
"uri": "https://cdn.fora-protocol.org/premium/ai-infrastructure.html",
"offers": [
{
"offer_id": "9d5735d7-1f17-4801-8dcf-7cac0b7b32b0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.00002", "currency": "USD", "unit_cost": "0.00002", "estimated_quantity": 2500, "unit": "tokens" },
"terms": [
{
@@ -171,7 +171,7 @@ When requesting multiple URIs, the response uses `offer_groups` instead of `offe
"offers": [
{
"offer_id": "89636cda-93f6-460e-af7f-2b6aef0f491b",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.00002", "currency": "USD", "unit_cost": "0.00002", "estimated_quantity": 2500, "unit": "tokens" },
"terms": [
{
@@ -202,7 +202,7 @@ When the requester has a subscription, the Exchange includes both per-request an
"offers": [
{
"offer_id": "9d5735d7-1f17-4801-8dcf-7cac0b7b32b0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.00002", "currency": "USD", "unit_cost": "0.00002", "estimated_quantity": 2500, "unit": "tokens" },
"terms": [
{
@@ -214,7 +214,7 @@ When the requester has a subscription, the Exchange includes both per-request an
},
{
"offer_id": "c5b01a4e-6536-4a42-a4fc-e41a1df1913d",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_FREE", "rate": "0", "currency": "USD", "unit_cost": "0" },
"subscription_id": "SUB-12345",
"terms": [ { "semantics": "TERM_SEMANTICS_ENUMERATED", "scopes": ["subscription:SUB-12345"] } ],
@@ -253,7 +253,7 @@ When the requester holds a subscription, the Exchange attaches `SubscriptionQuot
"offers": [
{
"offer_id": "c5b01a4e-6536-4a42-a4fc-e41a1df1913d",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_FREE", "rate": "0", "currency": "USD" },
"subscription_id": "SUB-12345",
"terms": [ { "semantics": "TERM_SEMANTICS_ENUMERATED", "scopes": ["subscription:SUB-12345"] } ],
@@ -310,7 +310,7 @@ Content-Type: application/json
{
"offer": {
"offer_id": "9d5735d7-1f17-4801-8dcf-7cac0b7b32b0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"title": "The Future of AI Infrastructure",
"pricing": {
"model": "PRICING_MODEL_PER_UNIT",
@@ -436,7 +436,7 @@ For batch transactions, use the `items` array:
{
"offer": {
"offer_id": "9d5735d7-1f17-4801-8dcf-7cac0b7b32b0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.00002", "currency": "USD", "unit_cost": "0.00002", "estimated_quantity": 2500, "unit": "tokens" },
"expires_at": "2026-03-14T02:30:00Z",
"terms": [
@@ -451,7 +451,7 @@ For batch transactions, use the `items` array:
{
"offer": {
"offer_id": "89636cda-93f6-460e-af7f-2b6aef0f491b",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.00002", "currency": "USD", "unit_cost": "0.00002", "estimated_quantity": 2500, "unit": "tokens" },
"expires_at": "2026-03-14T02:30:00Z",
"terms": [
@@ -607,7 +607,7 @@ Content-Type: application/json
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"idempotency_key": "ur-e4f2a1",
"transaction_id": "txn-mp-93a7f2",
"billing_id": "bill-93a7f2-001",
@@ -717,11 +717,11 @@ sequenceDiagram
PUB->>MP: Compare: signed URL accesses vs transactions
```
-Three independent records -- CDN logs, Exchange transactions, usage reports -- that must agree. This provides stronger reconciliation than ad-tech's two-sided model.
+Three independent records -- CDN logs, Exchange transactions, usage reports -- that must agree.
## Consistency Model
-FORA uses **at-most-once with reconciliation**, same as OpenRTB:
+FORA uses **at-most-once with reconciliation**:
- Idempotency keys on every `TransactionRequest`, scoped to the agent whatever the route (prevent double-charge on retry, through a Broker or directly; a key reused with different items is refused with `already_exists`)
- "Authorize first, deliver second" ordering (do not issue signed URL until billing succeeds)
@@ -743,7 +743,7 @@ Content-Type: application/json
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"idempotency_key": "dsp-20260318-abc123",
"transaction_id": "txn-mp-93a7f2",
"billing_id": "bill-93a7f2-001",
@@ -811,7 +811,7 @@ message Preview {
```json
{
"offer_id": "9bb01145-326e-42a9-b2ac-058e3114bdfc",
- "exchange": "exchange.ssp-example.com",
+ "exchange": "exchange.example",
"title": "Climate Summit Photo - Reuters",
"pricing": { "model": "PRICING_MODEL_PER_UNIT", "rate": "0.50", "currency": "USD", "estimated_quantity": 1, "unit": "accesses" },
"previews": [
@@ -838,7 +838,6 @@ This follows the universal content exchange pattern:
- **Shutterstock**: `small_thumb.url` (100px, unwatermarked), `preview.url` (450px, watermarked), `preview_1500.url` (1500px, watermarked)
- **Spotify**: `preview_url` -- URL to a 30-second MP3 clip
- **IIIF**: Parameterized URL template -- client requests any size
-- **OpenRTB**: `img.url` + `img.w` + `img.h` per asset
Nobody puts image bytes in offer metadata. The Exchange holds a URL string; the CDN holds the pixels.
diff --git a/website/src/content/docs/protocol/walkthrough-v1.mdx b/website/src/content/docs/protocol/walkthrough-v1.mdx
index cacd049a..96c23ed8 100644
--- a/website/src/content/docs/protocol/walkthrough-v1.mdx
+++ b/website/src/content/docs/protocol/walkthrough-v1.mdx
@@ -44,8 +44,8 @@ curl -s https://techcrunch.com/.well-known/fora.json | jq
"contact": "licensing@techcrunch.com",
"exchanges": [
{
- "domain": "exchange.ssp-alpha.com",
- "endpoint": "https://exchange.ssp-alpha.com/fora/v1",
+ "domain": "exchange.alpha.example",
+ "endpoint": "https://exchange.alpha.example/fora/v1",
"relationship": "PROVIDER_RELATIONSHIP_DIRECT"
}
],
@@ -59,13 +59,13 @@ The agent now knows which Exchange to query for TechCrunch content. The `support
The agent sends a `ResourceQuery` to the Exchange with its identity in the `Requester` message. This is the v1.0 replacement for CoMP's `AISystem` — it carries identity, scopes, and optional delegation in a single envelope. The request is authenticated separately by an RFC 9421 HTTP Message Signature in the HTTP headers, not by a field in the message body.
-`POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/DiscoverResources`
+`POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/DiscoverResources`
{/* fora-validate: ResourceQuery */}
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"uris": [
"https://techcrunch.com/2026/03/19/ai-agents-commerce.html"
],
@@ -97,14 +97,14 @@ The Exchange looks up the article in its catalog and returns one offer for each
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"offer_groups": [
{
"uri": "https://techcrunch.com/2026/03/19/ai-agents-commerce.html",
"offers": [
{
"offer_id": "3a1cf96e-74b7-4c5d-abb0-925c3f83dfe3",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"title": "AI Agents Are Rewriting Commerce",
"ext": {
"comp.package_id": "PKG-TC-AGENTS-COMMERCE",
@@ -179,7 +179,7 @@ The Exchange looks up the article in its catalog and returns one offer for each
The agent commits to the offer by sending the full signed `offer` back, reflected exactly as received at discovery:
-`POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/ExecuteTransaction`
+`POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/ExecuteTransaction`
{/* fora-validate: TransactionRequest */}
```json
@@ -190,7 +190,7 @@ The agent commits to the offer by sending the full signed `offer` back, reflecte
{
"offer": {
"offer_id": "3a1cf96e-74b7-4c5d-abb0-925c3f83dfe3",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"title": "AI Agents Are Rewriting Commerce",
"pricing": {
"model": "PRICING_MODEL_PER_UNIT",
@@ -288,13 +288,13 @@ The CDN edge function verifies:
Usage reporting is mandatory. The agent reports actual consumption, in the unit of the offer's price (`accesses`):
-`POST https://exchange.ssp-alpha.com/fora/v1/fora.v1.ExchangeService/ReportUsage`
+`POST https://exchange.alpha.example/fora/v1/fora.v1.ExchangeService/ReportUsage`
{/* fora-validate: UsageReport */}
```json
{
"ver": "1.0",
- "exchange": "exchange.ssp-alpha.com",
+ "exchange": "exchange.alpha.example",
"idempotency_key": "ur-001",
"transaction_id": "txn-tc-001",
"billing_id": "bill-tc-001",
diff --git a/website/src/content/docs/reference/fora-json-example.mdx b/website/src/content/docs/reference/fora-json-example.mdx
index d691dbc5..44343a81 100644
--- a/website/src/content/docs/reference/fora-json-example.mdx
+++ b/website/src/content/docs/reference/fora-json-example.mdx
@@ -25,13 +25,13 @@ The `fora.json` file is served at `/.well-known/fora.json` and carries a `WellKn
],
"exchanges": [
{
- "domain": "exchange.ssp-alpha.com",
- "endpoint": "https://exchange.ssp-alpha.com/v1",
+ "domain": "exchange.alpha.example",
+ "endpoint": "https://exchange.alpha.example/v1",
"relationship": "DIRECT"
},
{
- "domain": "exchange.ssp-beta.com",
- "endpoint": "https://exchange.ssp-beta.com/v1",
+ "domain": "exchange.beta.example",
+ "endpoint": "https://exchange.beta.example/v1",
"relationship": "RESELLER"
}
]
@@ -99,7 +99,7 @@ The agent checks `/.well-known/fora.json` before attempting to access content:
```
1. Agent wants content from techprovider.com
2. GET https://techprovider.com/.well-known/fora.json
-3. Finds Exchange endpoint: exchange.ssp-alpha.com/v1
+3. Finds Exchange endpoint: exchange.alpha.example/v1
4. Calls DiscoverResources → gets Offers with pricing
5. Calls ExecuteTransaction → gets signed URL
6. Fetches content from CDN
@@ -113,7 +113,7 @@ If the agent doesn't know about FORA and tries to crawl directly:
1. Agent hits techprovider.com/premium/article
2. Edge function returns 403 with two headers:
X-Content-Rules: https://techprovider.com/.well-known/fora.json
- X-FORA-Exchange: exchange.ssp-alpha.com
+ X-FORA-Exchange: exchange.alpha.example
3. Agent discovers fora.json from X-Content-Rules (and, optionally, starts
discovery at the X-FORA-Exchange domain, resolving its endpoint from
that Exchange's own fora.json)
@@ -123,10 +123,10 @@ If the agent doesn't know about FORA and tries to crawl directly:
## Relationship Types
-| Relationship | Description | Ad-Tech Equivalent |
-|---|---|---|
-| `DIRECT` | Provider has a direct contract with this Exchange | ads.txt DIRECT |
-| `RESELLER` | Exchange resells content via another authorized party | ads.txt RESELLER |
+| Relationship | Description |
+|---|---|
+| `DIRECT` | Provider has a direct contract with this Exchange |
+| `RESELLER` | Exchange resells content via another authorized party |
## Provider Trust Model
diff --git a/website/src/content/docs/security/threat-model.mdx b/website/src/content/docs/security/threat-model.mdx
index f772ec31..8a91cf3a 100644
--- a/website/src/content/docs/security/threat-model.mdx
+++ b/website/src/content/docs/security/threat-model.mdx
@@ -1,66 +1,60 @@
---
title: "Threat Model"
-description: "FORA threat model with 41 attack vectors and countermeasures, informed by 20 years of ad-tech fraud history"
+description: "How each party in FORA could cheat, and how a third party could attack it: the attack, and the countermeasure the protocol and FORA Server provide."
---
-## Methodology
+## How This Page Is Organized
-Three independent adversarial analyses were conducted:
-1. **Ad-tech fraud history**: Every major fraud category from 20+ years of programmatic advertising, mapped to FORA equivalents
-2. **Content licensing abuse brainstorm**: 56 attack vectors from each party's perspective (dishonest exchange, agent, provider, broker, attacker)
-3. **STRIDE security threat model**: Formal threat modeling of the protocol's technical surface
+The threats are grouped by who attacks: a dishonest Exchange operator, agent, provider or Broker, a third party, and abuse of the system as a whole. Three sections cover attestations, delegation and the licensing layer. Each threat states the attack and its countermeasure, and says whether the protocol prevents it, reconciliation detects it, or only a contract can settle it.
-## Key Lesson from Ad-Tech History
+## The Rule Behind the Design
-> **Every self-reported field gets gamed.** Any claim that is not cryptographically attested by a trusted party will be falsified if there's economic incentive.
+> **A self-reported field gets falsified when falsifying it pays.** A claim that no party signs and answers for cannot be trusted.
-This single pattern accounts for most ad-tech fraud: domain spoofing (self-reported domain), geo spoofing (self-reported location), viewability fraud (self-reported measurement), and attribution fraud (self-reported conversion). FORA must learn from this.
+So FORA signs what it can. The Exchange signs each offer, the agent signs its acceptance of each offer it buys, and every sender signs its own request. What no signature can cover, such as what an agent does with content after it fetches it, is left to reconciliation and to contracts.
## 1. Supply-Side Threats (Dishonest Exchange Operator)
### T1: Hidden fee inflation
**Attack**: Exchange charges agent $0.75 but tells provider the rate was $0.50, pocketing the spread.
-**Ad-tech parallel**: The "unknown delta" from ISBA study -- 15% of spend unaccounted for.
-**Countermeasure (protocol)**: Offers are cryptographically signed by the Exchange (Ed25519). Provider can verify prices weren't inflated beyond RSL terms.
+**Countermeasure (protocol)**: The price of an offer derives from exactly one catalog term, as the publisher declared it, and the Exchange signs the offer (Ed25519, `Offer.signature`). The transaction record holds the signed offer and the agent's signed acceptance of it, so the price the agent agreed to is on record under two signatures. In FORA Server's publisher console, the provider sees each sale with its gross, the Exchange fee and its net, and can check both signatures in the browser.
**Countermeasure (reconciliation)**: Provider compares CDN access logs against Exchange-reported transaction volumes and revenue.
### T2: Dynamic price discrimination
**Attack**: Exchange serves different prices to different requesters for identical content.
-**Countermeasure (protocol)**: Not directly preventable -- price discrimination is a business decision. If prices are derived from RSL (provider-set), the Exchange can't inflate beyond RSL terms without detection.
-**Countermeasure (reconciliation)**: Brokers querying from different identities can detect discrepancies.
+**Countermeasure (protocol)**: Not directly preventable -- price discrimination is a business decision. The offer's price derives from the publisher's own term, so an offer priced otherwise is signed evidence against the Exchange that issued it.
+**Countermeasure (reconciliation)**: An agent or a Broker that queries under different identities can compare the offers it gets.
### T3: Bait-and-switch content
**Attack**: Offer describes "2026 Q4 Financial Report, 15,000 words" but signed URL delivers different content.
-**Ad-tech parallel**: Inventory misrepresentation (declaring premium placement, serving remnant).
-**Countermeasure (protocol)**: **Content hash in the Offer.** ResourceIdentity.content_hash commits to content at offer time. Agent verifies after fetch. Mismatch = dispute.
+**Countermeasure (protocol)**: **Content hash in the Offer.** `ResourceIdentity.content_hash` commits to the content at offer time. The agent verifies it after the fetch, and a mismatch on a static resource is grounds for a dispute.
### T4: Phantom transactions / ghost billing
**Attack**: Exchange fabricates billing_ids that never corresponded to real agent requests.
-**Ad-tech parallel**: Impression inflation by exchanges.
-**Countermeasure (protocol)**: **Mutual transaction receipts.** Agent's idempotency key in TransactionRequest is agent's proof; Exchange's billing_id is Exchange's proof. Neither can forge the other's Ed25519 signature.
+**Countermeasure (protocol)**: **The agent signs each purchase.** Each item carries the agent's `AgentAcceptance`, an Ed25519 signature over the offer's signature, the requester and the idempotency key. FORA Server's Exchange verifies it against the agent's registered key and stores the signed offer with both signatures for every item it executes. An Exchange cannot produce an acceptance for a purchase the agent never made.
### T5: Provider revenue skimming
**Attack**: Exchange tells provider 1,000 transactions occurred; actually processed 1,500.
**Countermeasure (reconciliation)**: **Three-sided reconciliation.** Provider's CDN logs, Exchange's transaction log, and usage reports must all agree.
-**Countermeasure (protocol)**: Both sides record `signed_url_hash` — SHA-256 of the delivery URL verbatim. The Exchange stores it on the transaction and the delivery endpoint stores it on its delivery event, so the two logs join on a value neither side chooses.
+**Countermeasure (protocol)**: Both sides record the SHA-256 of the delivery URL verbatim. The Exchange stores it on the transaction as `signed_url_hash`, and FORA Server's edge function writes it into each delivery log record, so the two logs join on a value neither side chooses.
### T6: Overly long signed URL expiry
**Attack**: Exchange issues 24-hour URLs instead of 5-minute, enabling reuse.
-**Countermeasure (protocol)**: The delivery endpoint refuses any URL whose `exp` has passed, and the Exchange issues short expiries -- five minutes in the reference flows. No verifier enforces a second, independent upper bound on the TTL: the only bound is the `exp` the Exchange signed, so a 24-hour URL is detected by reconciliation (T5), not refused at the edge. A provider who wants a hard ceiling has to add that check to its own edge function.
+**Countermeasure (protocol)**: The delivery endpoint refuses any URL whose `exp` has passed, and the Exchange issues short expiries: five minutes in FORA Server, and a seat can set a shorter one. No verifier enforces a second, independent upper bound on the TTL: the only bound is the `exp` the Exchange signed, so a 24-hour URL is detected by reconciliation (T5), not refused at the edge. A provider who wants a hard ceiling has to add that check to its own edge function.
### T7: Signing key leakage
**Attack**: Exchange shares signing keys with a preferred requester, enabling URL forgery.
-**Countermeasure (protocol)**: **Asymmetric signing, with per-tenant key isolation.** The Exchange holds a separate private key per tenant, loaded from a key store at startup; the delivery endpoint verifies with the matching public key, published in the Exchange's key directory. This bounds the damage rather than preventing the act -- the attacker here is the Exchange, so no control the Exchange operates can stop it from exporting its own key. What the design gives you is that a leaked verification key forges nothing, a compromised edge cannot mint URLs, and a leaked tenant key forges URLs for that one tenant and no other. Detection is T5's job: forged fetches appear in the provider's delivery log and not in the Exchange's transaction log, and the two join on `signed_url_hash`.
+**Countermeasure (protocol)**: **Asymmetric signing.** The Exchange signs delivery URLs with its Ed25519 private key, and the delivery endpoint verifies them with the public key the Exchange publishes in its key directory. This bounds the damage rather than preventing the act -- the attacker here is the Exchange, so no control the Exchange operates can stop it from exporting its own key. What the design gives you is that a leaked verification key forges nothing and a compromised edge cannot mint URLs. Detection is T5's job: forged fetches appear in the provider's delivery log and not in the Exchange's transaction log, and the two join on `signed_url_hash`.
## 2. Demand-Side Threats (Dishonest Agent / Requester)
### T8: Signed URL sharing
**Attack**: Agent A pays, shares signed URL with Agents B, C, D before expiry.
-**Countermeasure (protocol)**: **Agent-bound signed URLs.** Embed the agent's RFC 7638 JWK Thumbprint (`agent_identity_hash`) as the URL's `agent_id` parameter, covered by the URL's Ed25519 signature; a capable edge function requires the fetcher to present its public key + an RFC 9421 signature (proof-of-possession) and checks `thumbprint(presented key) == agent_identity_hash`. Implemented via `agent_identity_hash` on `TransactionResponse`.
+**Countermeasure (protocol)**: **Agent-bound signed URLs.** Embed the agent's RFC 7638 JWK Thumbprint (`agent_identity_hash`) as the URL's `agent_id` parameter, covered by the URL's Ed25519 signature; a capable edge function requires the fetcher to present its public key + an RFC 9421 signature (proof-of-possession) and checks `thumbprint(presented key) == agent_identity_hash`. The Exchange returns the value as `agent_identity_hash` on `TransactionResponse`. FORA Server's edge function enforces the binding by default. Behind CloudFront's own signed-URL check, which cannot run it, the URL works for whoever holds it until it expires, and T5's reconciliation applies.
### T9: Systematic caching / content mirroring
**Attack**: Agent fetches every article once, caches locally forever, never pays again.
-**Countermeasure (protocol)**: **Single-use signed URLs.** Edge function marks URL as consumed after first fetch.
+**Countermeasure (protocol)**: **Short, bound URLs.** A signed URL works only until it expires and, when bound, only for the agent whose key it names (T8). It does not stop an agent from keeping what it fetched.
**Countermeasure (legal)**: License terms prohibiting caching beyond session scope.
### T10: Usage underreporting (token count)
@@ -73,44 +67,43 @@ This single pattern accounts for most ad-tech fraud: domain spoofing (self-repor
### T12: Offer metadata harvesting
**Attack**: Agent calls DiscoverResources repeatedly, extracting metadata -- never transacting.
-**Ad-tech parallel**: Bid stream data harvesting.
-**Countermeasure (protocol)**: Rate limiting on DiscoverResources. Exchange tracks query-to-transaction ratio per agent.
+**Countermeasure (protocol + operational)**: Every query is signed, so the Exchange knows who asks, and it can limit each caller and report the limit in `ResourceResponse.rate_limit`. The operator can watch each caller's ratio of queries to purchases. FORA Server's Exchange leaves request rate limits to a proxy in front of it.
### T13: Credential sharing / proxy laundering
**Attack**: One agent identity (signing key) shared across organizations.
-**Countermeasure (protocol + operational)**: Sharing a key cannot redirect costs: the request carries no self-supplied billing field, so every request signed with the shared key bills the one account of the key directory that publishes that key — the abuse lands on the sharer's own bill. Detection is behavioral, not cryptographic: the Exchange monitors usage patterns per verified identity (IP diversity, volume spikes, impossible concurrency) and can deactivate the account. The signature binding does not prevent sharing. It concentrates all shared usage under one identity so it can be seen and priced.
+**Countermeasure (protocol + operational)**: Sharing a key cannot redirect costs: the request carries no self-supplied billing field, so every request signed with the shared key bills the one account of the key directory that publishes that key — the abuse lands on the sharer's own bill. Detection is behavioral, not cryptographic: the operator watches usage per verified identity (IP diversity, volume spikes, impossible concurrency) and can deactivate the account, which is then refused paid purchases with `DENIAL_REASON_ACCOUNT_INACTIVE`. The signature binding does not prevent sharing. It concentrates all shared usage under one identity so it can be seen and priced.
## 3. Provider-Side Threats (Dishonest Provider)
### T14: Paywall-gated garbage
**Attack**: Compelling headline, but behind the paywall: padding, filler, or unrelated content.
-**Countermeasure (protocol)**: Content integrity hash catches *changed* content. Exchange curation/reputation systems address quality.
+**Countermeasure (protocol)**: The content hash catches *changed* content. Quality is left to the Exchange's curation of its publishers and to the agent's choice of what to buy.
-### T15: Word count / token count inflation
-**Attack**: Provider pads content to inflate word count, affecting unit_cost calculations.
-**Countermeasure (protocol)**: Exchange independently verifies content length during RSL ingestion. Agent independently tokenizes after fetch.
+### T15: Quantity inflation
+**Attack**: Provider overstates `estimated_quantity`, or pads the content to justify it, so a metered purchase charges more.
+**Countermeasure (protocol)**: The estimate is the publisher's own statement, in the signed offer, and the charge (estimate × rate) is fixed before the agent buys. The agent counts what it fetched and disputes a resource that falls short (`DISPUTE_REASON_INCOMPLETE_CONTENT`), with the CDN's delivery log as corroboration.
### T16: Content versioning fraud
**Attack**: Provider changes content at URL after Exchange has priced it.
-**Countermeasure (protocol)**: **Content integrity hash in the Offer.** SHA-256 of content at offer creation time. Agent verifies after fetch.
+**Countermeasure (protocol)**: **Content hash in the Offer.** `content_hash` records the content at offer time, as a SimHash (`simhash-v1`, Level 1) or a SHA-256 (`sha256`, Level 2). The agent verifies it after the fetch.
### T17: Double-selling with exclusivity claims
**Attack**: Provider grants "exclusive" licensing to multiple Exchanges.
-**Countermeasure**: ResourceIdentity enables detection (same content_hash from different exchanges). Prevention requires legal contracts.
+**Countermeasure**: `ResourceIdentity` enables detection: the same content hash, DOI or IPTC GUID offered by different Exchanges. Prevention requires legal contracts.
### T18: Selective enforcement / preferential access
**Attack**: Edge function blocks some agents but quietly allows others to scrape freely.
-**Countermeasure**: Not solvable at protocol level. Market dynamics address it.
+**Countermeasure**: Not solvable at protocol level. It is a contract matter between the provider and its Exchange.
## 4. Broker Threats
### T19: Hidden orchestration fee
**Attack**: Broker adds markup to every offer relayed to the agent.
-**Countermeasure (protocol)**: **Exchange signs offers (Ed25519).** Broker passes through signed offers. Agent verifies the price was not tampered with.
+**Countermeasure (protocol)**: **Exchange signs offers (Ed25519).** The Broker passes the signed offers through unchanged, and the agent verifies that the price was not tampered with. A Broker's fee has no field: it is disclosed out of band and added to the offer price, never folded into it.
### T20: Kickback-driven offer selection
-**Attack**: Broker always routes to a specific Exchange regardless of pricing.
-**Countermeasure (protocol)**: Agent can bypass Broker and query and buy at Exchanges directly. A Broker signs every request it sends alone, with its own RFC 9421 HTTP Message Signature, so the Exchange knows which Broker sent it and the Broker cannot deny it. The agent's consent to a transaction is the `AgentAcceptance` it signed into the body, which a Broker cannot alter or forge, and `agent_request_acceptance` binds the full ordered set of offers the agent chose.
+**Attack**: Broker orders or leaves out offers to favor an Exchange that pays it, whatever their relevance to the request.
+**Countermeasure (protocol)**: A Broker's order is its own judgement, which is why an agent works with a Broker it trusts. The agent can bypass the Broker and query and buy at Exchanges directly. A Broker signs every request it sends alone, with its own RFC 9421 HTTP Message Signature, so the Exchange knows which Broker sent it and the Broker cannot deny it. The agent's consent to a transaction is the `AgentAcceptance` it signed into the body, which a Broker cannot alter or forge, and `agent_request_acceptance` binds the full ordered set of offers the agent chose.
### T21: Query intelligence harvesting
**Attack**: Broker logs every DiscoverResources query, sells the data.
@@ -133,7 +126,7 @@ This single pattern accounts for most ad-tech fraud: domain spoofing (self-repor
### T22: Exchange impersonation
**Attack**: Attacker sets up fake Exchange, poisons fora.json via DNS hijack.
-**Countermeasure (protocol)**: fora.json served over HTTPS from provider's domain (TLS proves endorsement). Every Offer carries `exchange_signature` (Ed25519). Agent verifies against Exchange's public key.
+**Countermeasure (protocol)**: fora.json served over HTTPS from provider's domain (TLS proves endorsement). Every Offer carries the Exchange's Ed25519 signature (`Offer.signature`). The agent verifies it against the key in the Exchange's key directory.
### T23: Signed URL interception (MITM)
**Attack**: Attacker intercepts TransactionResponse, steals signed URL.
@@ -141,15 +134,15 @@ This single pattern accounts for most ad-tech fraud: domain spoofing (self-repor
### T24: Transaction replay
**Attack**: Attacker captures valid TransactionRequest and replays it.
-**Countermeasure (protocol)**: **Idempotency keys.** Every state-mutating call carries a required `idempotency_key` — `TransactionRequest`, `UsageReport`, and `DisputeRequest`. Servers dedupe per agent and key, whatever the route — the agent the RFC 9421 signature authenticates on a direct request, the agent its acceptances authenticate on a relayed purchase — so a replay returns the original result instead of re-charging or re-filing, and a captured purchase replayed through another Broker is a replay too. The agent's authorization is verified before any stored result is created or returned. A key reused by the same agent with a different request (different items, or another order) is refused with `already_exists` and changes nothing; a key another agent used is never a collision. Broker `Resolve` (`DiscoveryRequest`) is pure discovery — it executes no transaction, has no replay exposure, and carries no key.
+**Countermeasure (protocol)**: **Idempotency keys.** Every state-mutating call carries a required `idempotency_key` — `TransactionRequest`, `UsageReport`, and `DisputeRequest`. Servers dedupe per agent and key, whatever the route — the agent the RFC 9421 signature authenticates on a direct request, the agent its acceptances authenticate on a relayed purchase — so a replay returns the original result instead of re-charging or re-filing, and a captured purchase replayed through another Broker is a replay too. The agent's authorization is verified before any stored result is created or returned. A key reused by the same agent with a different request (different items, or another order) is refused with `already_exists` and changes nothing, as FORA Server's Exchange does on `ExecuteTransaction`; a key another agent used is never a collision. Broker `Resolve` (`DiscoveryRequest`) is pure discovery — it executes no transaction, has no replay exposure, and carries no key.
### T25: Billing_id forgery in usage reports
**Attack**: Attacker fabricates billing_ids in usage reports.
-**Countermeasure (protocol)**: Exchange validates billing_id exists in transaction log before accepting usage reports.
+**Countermeasure (protocol)**: The Exchange accepts a usage report only for a transaction it recorded, and checks the report's `billing_id` against that transaction.
### T26: DiscoverResources flooding (DoS)
**Attack**: Flood DiscoverResources to exhaust Exchange resources.
-**Countermeasure (protocol)**: Per-partner rate limiting keyed on the **verified requester identity** (RFC 9421 request signature — domain/key). Anonymous queries rejected.
+**Countermeasure (protocol + operational)**: Anonymous queries are refused: every `ExchangeService` call must carry a valid RFC 9421 request signature, so a rate limit can key on the **verified requester identity**. FORA Server's Exchange limits agent registrations per IP address and leaves other request rate limits to a proxy in front of it.
### T-EP-1: Manifest-advertised endpoint redirection
**Attack**: A party that answers for `{domain}/.well-known/fora.json` — the domain's operator, or anyone who can influence what a consumer reads there — advertises an `endpoint` on a host it controls, or on another port of the named host, or one carrying `user:password@` credentials. Every consumer that resolves that domain then sends signed calls (usage reports, disputes, execute) to the attacker's address, or stamps an `Authorization` header the SDK never chose. A dial-time SSRF guard raises no objection: the destination is an ordinary public host.
@@ -159,35 +152,35 @@ This single pattern accounts for most ad-tech fraud: domain spoofing (self-repor
**Bounded, not eliminated.** The manifest fetch follows redirects, so the party that answers *for the document* may be one a redirect chose. What that party cannot do is change where the signed call lands: whatever the manifest says, the endpoint it advertises must still anchor to the domain the offer named.
-## 6. Systemic / Arbitrage Threats
+## 6. Systemic Threats
### T27: Content arbitrage (buy low, resell high)
**Attack**: Entity buys from Exchange A at $0.04, resells via own Exchange at $0.05.
-**Countermeasure (protocol)**: ResourceIdentity enables detection. fora.json declares authorized providers.
+**Countermeasure (protocol)**: The provider's `fora.json` names the Exchanges that may sell its content, so an agent can check that the Exchange selling it is one of them. `ResourceIdentity` shows the same content offered elsewhere.
### T28: Free content laundering
**Attack**: Scrape freely available content, package behind paywall as "premium."
-**Countermeasure**: Content fingerprinting against known free content databases.
+**Countermeasure**: Outside the protocol: the Exchange's review of its publishers. A listing goes live only when the site's own `fora.json` names the Exchange, and fingerprinting against known free content can flag the rest.
### T29: Synthetic content farming
**Attack**: Generate AI content at near-zero cost, sell as human-authored.
-**Countermeasure**: CoMP's `Text.sourcetype` field. Future: C2PA content credentials.
+**Countermeasure**: Signed origin claims. CoMP V1 marks AI-generated text in `Text.sourcetype`, and the [fora-c2pa-v1](/protocol/ext-c2pa/) profile carries C2PA validation results, including who signed the content credentials and the declared source type, as attestation claims. A false claim with no credentials behind it is a contract matter.
### T30: License tier arbitrage
**Attack**: Buy at grounding rate, use for training. Collapses pricing model at scale.
**Countermeasure**: Black box problem. Legal/contractual enforcement only.
### T31: Absence-reason existence oracle
-**Attack**: An unauthorized caller probes for a resource and reads the `absence_reason`. Authorization-flavored values (`NOT_AUTHORIZED`, `NOT_IN_CATALOG`, `CONTENT_BLOCKED`) distinguish "no such resource" from "it exists but you may not have it" — confirming existence and the reason for refusal. Broker `Resolve` (`DiscoveryResponse.absence_reason`) exposes the same oracle at the broker that `DiscoverResources` (`OfferGroup.absence_reason`) does at the Exchange, so hiding it on one surface but not the other still leaks.
+**Attack**: An unauthorized caller probes for a resource and reads the `absence_reason`. Authorization-flavored values (`OFFER_ABSENCE_REASON_NOT_AUTHORIZED`, `OFFER_ABSENCE_REASON_NOT_IN_CATALOG`, `OFFER_ABSENCE_REASON_CONTENT_BLOCKED`) distinguish "no such resource" from "it exists but you may not have it" — confirming existence and the reason for refusal. Broker `Resolve` (`DiscoveryResponse.absence_reason`) exposes the same oracle at the broker that `DiscoverResources` (`OfferGroup.absence_reason`) does at the Exchange, so hiding it on one surface but not the other still leaks.
**Countermeasure (protocol)**: A scope shortfall is never disclosed. When the requester's scopes leave no presentable offer for a resource, the Exchange answers with no offers and no absence reason, exactly as for any resource with nothing to offer, and a Broker adds no reason of its own (the existence-hiding rule on `Requester.scopes`). No absence or denial reason reports a scope shortfall. For the other reasons, the reason is a hint, not a guarantee: where existence itself must stay hidden, the Exchange/Broker **MAY omit** `absence_reason` (leave it unset) rather than reveal an authorization-flavored value, and this applies equally to `OfferGroup.absence_reason` and `DiscoveryResponse.absence_reason`. `ErrorDetail.message`/`metadata` are held to the same rule (T-LIC-adjacent leakage): servers SHOULD NOT restore the withheld detail there as free text.
## Prevention Taxonomy
| Level | Threat IDs | What It Means |
|---|---|---|
-| **Preventable at protocol level** | T3, T4, T5, T6, T7, T8, T9, T12, T16, T19, T22, T23, T24, T25, T26, T-BRK-1, T-ATT-1, T-ATT-2, T-ATT-3, T-ATT-5, T-DEL-1, T-DEL-2, T-DEL-3, T-DEL-4, T-DEL-6 | Protocol changes make the attack structurally impossible |
-| **Detectable via reconciliation** | T1, T2, T4, T5, T13, T14, T15, T17, T27, T-ATT-4, T-DEL-5 | Three-sided reconciliation catches it |
-| **Legal/contractual only** | T10, T11, T13, T17, T18, T20, T21, T28, T29, T30, T-DEL-5 | Can't enforce technically |
+| **Prevented by the protocol** | T3, T4, T8, T16, T19, T22, T23, T24, T25, T‑BRK‑1, T‑BRK‑2, T‑EP‑1, T‑ATT‑1, T‑ATT‑5, T‑DEL‑1, T‑DEL‑2, T‑DEL‑3, T‑DEL‑4, T‑DEL‑6, T31, T‑LIC‑1, T‑LIC‑2, T‑LIC‑3, T‑LIC‑4 | Signatures and checks make the attack fail |
+| **Detected by reconciliation or monitoring** | T1, T2, T5, T6, T7, T12, T13, T14, T15, T17, T26, T27, T‑BRK‑3, T‑ATT‑2, T‑ATT‑3, T‑ATT‑4, T‑DEL‑5 | The records disagree, or the operator sees the pattern |
+| **Left to contracts** | T9, T10, T11, T18, T20, T21, T28, T29, T30 | No technical control reaches it |
### The Three Lines of Defense
@@ -197,7 +190,7 @@ Line 1: Protocol-level prevention
agent-signed request-set proof (request acceptance, verified before
idempotency state), holder-bound JWT delegation chain (cnf),
RFC 9421 request signatures from every sender (with chain verification
- on unchanged forwarding), subscription-level quota tracking
+ on unchanged forwarding)
Makes attacks structurally impossible
Line 2: Three-sided reconciliation
@@ -214,29 +207,29 @@ Line 3: Legal/contractual enforcement
### T-ATT-1: Forged attestation injection
**Attack**: Attacker crafts a fake `ResourceAttestation` with a fabricated `verifier` domain and pushes it via `CatalogService.PushResources`.
-**Countermeasure (protocol)**: Exchange verifies that the request's signer is the provider itself or listed in the provider's `catalog_contributors` (from `fora.json`). Exchange verifies the attestation `signature` against the verifier's public key in its WBA directory (the JWK Set at `/.well-known/http-message-signatures-directory`). FORA has no dedicated verifier role; a verifier publishes under its operator's role (`ROLE_PUBLISHER` for a self-attesting publisher, `ROLE_EXCHANGE` for a standalone vendor). Both checks must pass.
+**Countermeasure (protocol)**: The Exchange checks that the request's signer is the provider itself or listed in the provider's `catalog_contributors` (from `fora.json`), and the protocol has it verify the attestation `signature` against the verifier's public key in its WBA directory (the JWK Set at `/.well-known/http-message-signatures-directory`). An agent can verify the same signature itself, because every verifier publishes its attestation-signing keys there. FORA has no dedicated verifier role; a verifier publishes under its operator's role (`ROLE_PUBLISHER` for a self-attesting publisher, `ROLE_EXCHANGE` for a standalone vendor). Both checks must pass.
### T-ATT-2: Stale attestation exploitation
**Attack**: Provider updates content (e.g., replaces article with filler) but the catalog retains the old attestation claiming 5000 tokens. Agent pays based on stale claims.
-**Countermeasure (protocol)**: `attested_at` timestamp enables agent freshness checks. Agents reject attestations older than their threshold for the content type (e.g., 4 hours for breaking news). Content hash mismatch (Level 1) triggers auto-credit via the dispute system.
-**Countermeasure (reconciliation)**: CDN response size corroborates discrepancies. 800 bytes for a 5000-token claim is auto-creditable regardless of hash match.
+**Countermeasure (protocol)**: `attested_at` timestamp enables agent freshness checks. An agent rejects attestations older than its own threshold for the content type (for example, 4 hours for breaking news). A content hash mismatch is grounds for a dispute (`DISPUTE_REASON_CONTENT_MISMATCH`).
+**Countermeasure (reconciliation)**: The CDN's response size corroborates the discrepancy: 800 bytes delivered for a 5,000-token claim is evidence whether or not the hash matches.
### T-ATT-3: Verification vendor compromise
**Attack**: Attacker compromises a third-party verifier's Ed25519 private key and signs fraudulent attestations for arbitrary content.
-**Countermeasure (protocol)**: Key rotation via JWKS pattern -- keys have `not_before` / `not_after` windows. Exchange caches the verifier's WBA directory with TTL-based refresh (1 hour default). Compromised key can be revoked by removing it from the verifier's WBA directory (the JWK Set at `/.well-known/http-message-signatures-directory`).
-**Countermeasure (operational)**: Exchange monitors attestation patterns per verifier. Sudden changes in claim distributions trigger investigation.
+**Countermeasure (protocol)**: Key rotation via JWKS pattern -- keys have `not_before` / `not_after` windows. Directories are cached with a TTL and refreshed; FORA Server and the Go SDK default to one hour. Compromised key can be revoked by removing it from the verifier's WBA directory (the JWK Set at `/.well-known/http-message-signatures-directory`).
+**Countermeasure (operational)**: The operator watches attestation patterns per verifier and investigates a sudden change in what a verifier claims.
### T-ATT-4: Claims inflation attack
**Attack**: Provider self-attests inflated `estimated_quantity: 10000` for a 500-word article, computes a valid content hash for the actual (short) content, and prices based on the inflated count.
-**Countermeasure (protocol)**: CDN response size is the corroboration signal. CDN log showing a 2KB response for a 10000-token claim is auto-creditable. Agent files dispute with `INCOMPLETE_CONTENT` reason; Tier 1 auto-resolution via CDN corroboration.
-**Countermeasure (pattern)**: Provider flagged for investigation when token discrepancy rate exceeds 2%. Graduated consequences apply.
+**Countermeasure (protocol)**: The agent files a dispute with `DISPUTE_REASON_INCOMPLETE_CONTENT`, and the CDN's response size corroborates it: a 2 KB response for a 10,000-token claim.
+**Countermeasure (operational)**: The operator watches each provider's disputes and the gap between its estimates and what agents report.
### T-ATT-5: Catalog contributor spoofing
-**Attack**: Unauthorized party registers a domain similar to a legitimate verifier (e.g., `doub1everify.com`) and pushes attestations claiming to be a trusted vendor.
+**Attack**: Unauthorized party registers a domain similar to a legitimate verifier (for example, `verif1er.example` for `verifier.example`) and pushes attestations claiming to be a trusted vendor.
**Countermeasure (protocol)**: `catalog_contributors` in `fora.json` uses exact domain matching. The provider must explicitly list the contributor's domain. The Exchange fetches the WBA directory from the exact `verifier` domain in the attestation and verifies the signature against that domain's `keys` (the JWK Set at `/.well-known/http-message-signatures-directory`).
## 8. Delegation and Authorization Threats
@@ -254,7 +247,7 @@ Line 3: Legal/contractual enforcement
### T-DEL-3: Revocation bypass
**Attack**: Principal revokes a delegation but cached or stored tokens continue to work until their `expires_at` timestamp.
-**Countermeasure (protocol)**: Short `exp` (2-4 hours for standard access) limits the window of continued access; the verifier allows 60 seconds of clock skew and no more. Trust is configured per subscription record, so removing the issuer's key from that record refuses every chain it signed at the next request. Per-token revocation through `revocation_uri` is not part of this profile.
+**Countermeasure (protocol)**: A short `exp` limits the window of continued access; the verifier allows 60 seconds of clock skew and no more. Trust is configured per subscription record, so removing the issuer's key from that record refuses every chain it signed at the next request. Per-token revocation through `revocation_uri` is not part of this profile.
### T-DEL-4: Signer impersonation and forged forwarding
@@ -266,25 +259,25 @@ FORA's Broker never forwards an agent's request unchanged: it originates discove
### T-DEL-5: Scope pollution
**Attack**: Agent declares scopes it doesn't actually have, hoping the Exchange returns premium content.
-**Countermeasure (reconciliation + contractual)**: `Requester.scopes` is the requester's own statement, signed and attributable, and the Exchange does not verify it. The Exchange presents an offer for a term only when the stated scopes cover the term's `LicenseTerm.scopes`, which hides the term from a requester that does not state the scope but does not stop one that states it falsely, so a false statement is detected and settled rather than prevented. For every scoped term an account bought, the transaction record holds the Exchange-signed offer and the agent's acceptance of it, attributed to the signing key, its directory and its [account](/protocol/authentication/#accounts). Reconciling those purchases against what the term's issuer actually granted that account, such as a subscription roster, a revenue-share agreement or an enterprise grant, exposes a scope the agent never held, and the account relationship and the term's contract settle it. An Exchange that needs prevention MAY require a verified delegation that grants a term's scopes before it presents the term ([Delegation](/protocol/authentication/#delegation)), and answers a requester without one as if the term did not exist. Verifying stated scopes is deferred, not designed out.
+**Countermeasure (reconciliation + contractual)**: `Requester.scopes` is the requester's own statement, signed and attributable, and the Exchange does not verify it. The Exchange presents an offer for a term only when the stated scopes cover the term's `LicenseTerm.scopes`, which hides the term from a requester that does not state the scope but does not stop one that states it falsely, so a false statement is detected and settled rather than prevented. For every scoped term an account bought, the transaction record holds the Exchange-signed offer and the agent's acceptance of it, attributed to the signing key, its directory and its [account](/protocol/authentication/#accounts). Reconciling those purchases against what the term's issuer actually granted that account, such as a subscription roster, a revenue-share agreement or an enterprise grant, exposes a scope the agent never held, and the account relationship and the term's contract settle it. An Exchange that needs prevention MAY require a verified delegation that grants a term's scopes before it presents the term ([Delegation](/protocol/authentication/#delegation)), and answers a requester without one as if the term did not exist.
### T-DEL-6: Quota gaming via multiple tokens
**Attack**: Agent obtains multiple delegation tokens for the same subscription (e.g., by requesting new delegations from different intermediaries) to exceed per-subscription quotas.
-**Countermeasure (protocol)**: **Exchange tracks quotas by `subscription_id`, not by delegation token.** All tokens referencing the same subscription share one counter. Multiple tokens for the same subscription do not multiply the quota. Rate limiting is applied at the subscription level regardless of how many delegation tokens reference it.
+**Countermeasure (protocol)**: **A quota belongs to the subscription, not to a token.** An Exchange meters a subscription on its subscription record and names it in `SubscriptionQuotaInfo.subscription_id`, so every token for one subscription draws on one count. A delegation chain cannot carry a cap of its own: the verifier refuses a chain with a cap claim.
## 9. Licensing-Layer Threats
### T-LIC-1: SSRF / phishing via `License.uri`
**Attack**: A malicious publisher pushes a term whose `License.uri` points at an internal address — `http://169.254.169.254/latest/meta-data/…` (cloud metadata), `http://localhost:6379/`, or `file:///etc/passwd`. An agent platform that auto-fetches the document to "read the license before use" (REFERENCE_ONLY requires this) issues a server-side request into its own infrastructure — leaking cloud credentials, reaching internal services, or reading local files. A variant points `uri` at attacker-controlled HTTPS to harvest the fetcher's identity/IP or serve misleading terms.
-**Countermeasure (protocol)**: `License.uri` is deliberately never *rejected* at ingest (data-labels TDL identifiers use non-URL schemes) — but "do not reject" is not "blindly fetch." A consumer that resolves `uri` MUST: (a) allowlist schemes (`https` + known TDL schemes); (b) block loopback, link-local, private, and cloud-metadata IP ranges, resolving-then-checking to defeat DNS rebinding; (c) fetch client-side through an egress proxy, never from the Exchange's privileged network; (d) treat the fetched bytes as untrusted content. The Exchange applies the same rules when it fetches to pin `uri_digest` (T-LIC-4).
+**Countermeasure (protocol)**: `License.uri` is deliberately never *rejected* at ingest (data-labels TDL identifiers use non-URL schemes) — but "do not reject" is not "blindly fetch." A consumer that resolves `uri` MUST: (a) allowlist schemes (`https` + known TDL schemes); (b) block loopback, link-local, private, and cloud-metadata IP ranges, resolving-then-checking to defeat DNS rebinding; (c) fetch client-side through an egress proxy, never from the Exchange's privileged network; (d) treat the fetched bytes as untrusted content. The publisher supplies `uri_digest` with the `uri` (T-LIC-4), so the Exchange never fetches the document.
**Same class — the SDK's directory fetch.** The same SSRF discipline applies to the WBA / well-known **directory fetches** the SDKs perform to resolve a signer's keys: the directory host is derived from a caller-supplied `Signature-Agent` and fetched **before** the ed25519 signature check, so an unauthenticated caller controls the fetch target (pre-auth SSRF). Defense is layered, and the layers have distinct owners:
- **In-code (SDK, primary).** The SDKs ship a **safe-by-default** SSRF-guarded transport, and it is **two checks, not one**. The *address pin* is connection-level: it resolves-then-checks every candidate address against a shared reserved-range corpus and pins the checked IP to defeat rebinding, on a maintained HTTP client (`net/http` / `httpx` / `undici`). The *scheme allowlist* is http(s)-only on the initial URL and every redirect hop, and it is deliberately **not** part of the connector — by the time a connection-level hook runs, the URL has been reduced to a host and a port and the scheme is no longer visible. Go and Python wrap the transport, so one object carries both (`SSRFGuard` inside `NewGuardedTransport`, `ssrf_guard()` inside `guarded_client`). TypeScript composes `ssrfGuard()` as the undici connector and states the scheme rule beside it, in `requireScheme()`. Because both ship in the artifact, their correctness cannot depend on deployment — and a caller who replaces the dial replaces the address pin with it, so the scheme check sits **above** the dial in the client tier, where no injected transport can remove it.
-- **Egress boundary (operator, recommended defense-in-depth).** Operators SHOULD additionally run any role that resolves directories from request-supplied hosts behind **restricted egress** (an egress proxy or network policy that cannot route to RFC1918 / link-local / metadata) and **IMDSv2 with hop-limit 1**. This neutralizes the entire class regardless of any in-code gap — but it is *defense-in-depth, not a substitute* for the SDK guard, which remains the primary control for an OSS artifact that runs in deployments the maintainers do not control.
+- **Egress boundary (operator, recommended defense-in-depth).** Operators SHOULD additionally run any role that resolves directories from request-supplied hosts behind **restricted egress** (an egress proxy or network policy that cannot route to RFC1918 / link-local / metadata) and **IMDSv2 with hop-limit 1**. This neutralizes the entire class regardless of any in-code flaw — but it is *defense-in-depth, not a substitute* for the SDK guard, which remains the primary control for an OSS artifact that runs in deployments the maintainers do not control.
-**Which fetches this covers, and where it does not reach yet.** The rule is the URL's **provenance**, not what is being fetched. A **request-derived** host is one another party chose — it arrives in a header, or on a signed message — so it takes the guarded transport; with one exception, named below, that is a gap rather than a choice. A **fixed, operator-chosen** address takes the plain transport deliberately: the operator rather than an attacker picked it, and an on-prem directory may legitimately sit on a private address a guard would refuse. Where each fetch stands today:
+**Which fetches take the guarded transport.** The rule is the URL's **provenance**, not what is being fetched. A **request-derived** host is one another party chose — it arrives in a header, or on a signed message — so it belongs on the guarded transport. A **fixed, operator-chosen** address takes the plain transport deliberately: the operator rather than an attacker picked it, and an on-prem directory may legitimately sit on a private address a guard would refuse. Each SDK's default:
| Fetch | URL comes from | Go | TypeScript | Python |
|---|---|---|---|---|
@@ -293,9 +286,7 @@ FORA's Broker never forwards an agent's request unchanged: it originates discove
| Exchange endpoint (`Offer.exchange`) | the request | guarded | **plain** | **plain** |
| Well-known JWKS | operator configuration | plain | plain | plain |
-The last row is the deliberate one — nobody but the operator can point that URL. The **third row is a known gap, not a decision**: that host comes off a signed offer, so by the rule above it belongs on the guarded transport in every language, and the two ports have not caught up. It is tracked separately.
-
-**What to do about it today.** TypeScript and Python require the application to supply the endpoint resolver — neither client builds one for you — so the remedy sits at a construction site you already own: pass the guarded transport explicitly, `guardedFetchFromEnv()` in TypeScript or `guarded_client()` in Python, rather than letting that resolver take its default. Conversely, a deployment that needs the guarded posture on a configured URL, or the plain one on a request-derived host, injects its own transport or sets `SKIP_SSRF` / `ALLOW_INSECURE`.
+Nobody but the operator can point the well-known JWKS URL, so it takes the plain transport. The Exchange endpoint comes off a signed offer, so it belongs on the guarded transport in every language. TypeScript and Python require the application to supply the endpoint resolver — neither client builds one for you — so pass the guarded transport to it explicitly, `guardedFetchFromEnv()` in TypeScript or `guarded_client()` in Python, rather than letting it take its plain default. Conversely, a deployment that needs the guarded posture on a configured URL, or the plain one on a request-derived host, injects its own transport or sets `SKIP_SSRF` / `ALLOW_INSECURE`.
### T-LIC-2: Silent restriction downgrade
@@ -311,14 +302,3 @@ The last row is the deliberate one — nobody but the operator can point that UR
**Attack**: A term carries a `License.uri`; the agent fetches and trusts the document. The publisher (or a MitM on the fetch) later changes the bytes at `uri` — which is just a URL — so the agent's understanding of the terms silently diverges from what was offered. `immutable: true` makes this worse (the agent caches and stops re-checking), but a mutable `uri` is swappable too.
**Countermeasure (protocol)**: `License.uri_digest` pins the document as `method:hexdigest` and is **required whenever `uri` is present** — any semantics, mutable or not. The party that sets `uri` supplies the digest with it: the publisher, on a term it pushes. Because the entire Offer is signed, the digest is tamper-evident; the agent verifies the bytes it fetches against it and refuses on mismatch.
-
-## Comparison to Ad-Tech Fixes
-
-| Ad-Tech Fix | Year | FORA Equivalent | Status |
-|---|---|---|---|
-| ads.txt | 2017 | fora.json (authorized providers) | In proto |
-| sellers.json | 2019 | Exchange identity in ResourceResponse | In proto |
-| SupplyChain Object | 2019 | exchange_signature on Offer | In proto |
-| ads.cert | 2020 | exchange_signature + content_integrity_hash | In proto |
-| MRC Viewability Standard | 2014 | A metered charge fixed at purchase (estimate × rate), never re-measured | Design principle |
-| Open Measurement SDK | 2018 | Three-sided reconciliation | In protocol flow |
diff --git a/website/src/data/collective-evidence.ts b/website/src/data/collective-evidence.ts
index e1b336df..78b7bf55 100644
--- a/website/src/data/collective-evidence.ts
+++ b/website/src/data/collective-evidence.ts
@@ -188,7 +188,7 @@ const Q = {
koPretraining: `This agreement is limited to regulating the National Library’s training of language models on the data governed by this agreement. It does not affect any pre-training that the base models used by the National Library may have undergone.`,
offerSig: `REQUIRED. Hex-encoded detached Ed25519 signature over the canonical serialization of the ENTIRE Offer — every field, including \`pricing\`, \`terms\` (the full licensing payload), \`expires_at\`, and \`exchange\`.`,
acceptance: `The agent's detached acceptance signature over this item's \`offer\`.`,
- money: `FORA never touches money. It follows the OpenRTB model: the protocol handles authorization and logging, while actual settlement happens outside the protocol through existing billing infrastructure.`,
+ money: `FORA never touches money. The protocol handles authorization and logging, while actual settlement happens outside the protocol through existing billing infrastructure.`,
manyTerms: `A resource carries zero or more \`LicenseTerm\` entries, at most 32. Each term is a complete, self-contained access arrangement, and a resource with several terms is the normal case.`,
brokerSearch: `A Broker runs one catalog search, which its operator chooses per deployment. The search only proposes URIs: prices, license terms and signatures always come from the Exchange, so a search result cannot produce an offer the Exchange does not stand behind.`,
ndpLicensed: `Members of NDP Nieuwsmedia are providing access to their archives, which include articles from over 30 national and regional news titles.`,
diff --git a/website/src/data/content-marketplaces.ts b/website/src/data/content-marketplaces.ts
new file mode 100644
index 00000000..6086b032
--- /dev/null
+++ b/website/src/data/content-marketplaces.ts
@@ -0,0 +1,260 @@
+// The content-marketplaces series (/resources/content-marketplaces/ and the
+// pages under it, plus /resources/standards-map/): the texts every page uses
+// word for word, so the seven pages say the same thing the same way. A page
+// imports a text from here and never types it again. Change a text here and
+// every page changes with it.
+//
+// Texts that hold links are HTML strings; the components render them with
+// set:html. "See About FORA." links to the About FORA card, which every page
+// carries with id="about".
+
+/** How real a thing is. StatusTag (src/lib/resource-markup.ts) renders these. */
+export const STATUS = {
+ live: { label: 'Live', means: 'Released and in use.' },
+ beta: { label: 'Beta', means: 'Open to sign up, labelled beta by the vendor.' },
+ 'closed-beta': { label: 'Closed beta', means: 'By admission only.' },
+ pilot: { label: 'Pilot', means: 'The vendor\'s own word for a limited program, such as Microsoft\'s PCM.' },
+ design: { label: 'Design', means: 'Designed, not in released software. Every FORA design item carries it.' },
+ roadmap: { label: 'Roadmap', means: 'Planned, not designed in public.' },
+ 'not-public': { label: 'Not public', means: 'The vendor doesn\'t say.' },
+} as const;
+export type StatusKey = keyof typeof STATUS;
+
+/**
+ * The positioning statement and the tagline the owner approved on 2026-11-15
+ * (messaging review, option A), word for word. The About page and the
+ * content-marketplaces page both use them.
+ */
+export const POSITIONING = 'FORA lets any AI agent find your content, read your license, pay and get a signed receipt, on the terms you set. It is an open protocol and free, open-source software, so any company can also run its own FORA marketplace.';
+/** The tagline; the phrase is shown in blue. */
+export const TAGLINE = 'Every AI agent is a customer. FORA is your storefront.';
+
+/** "See About FORA.", linked to the page's About FORA card. */
+export const SEE_ABOUT = 'See About FORA.';
+
+/**
+ * The About FORA card (Callout kind="about"): once per page, near the end.
+ * The owner's text of the fifth round (2026-11-15), word for word.
+ */
+export const ABOUT_FORA: { title: string; text: string }[] = [
+ {
+ title: 'Federated Open Resource Access.',
+ text: 'FORA is an open protocol and free, open-source software. Any company can run its own content marketplace on it, and every FORA marketplace works with every other.',
+ },
+ {
+ title: 'Where it runs.',
+ text: 'Gutefrage runs the whole FORA stack itself on helpster.de: its own Exchange, on its own terms.',
+ },
+ {
+ title: 'Ready to try.',
+ text: 'Anyone can run FORA\'s Exchange and publisher console: Gutefrage runs its own, and the code is open to clone. Postindustria offers a ready-made deployment with a publisher console, so a publisher can try it and start selling. It charges publishers no fee beyond the payment system\'s transaction fees.',
+ },
+ {
+ title: 'Money and disputes.',
+ text: 'Money moves outside the protocol: your operator bills the buyer and pays you under its own rules. The protocol defines a dispute call, filed against a usage report, and each operator handles disputes under its own rules.',
+ },
+];
+
+/**
+ * FORA's terms, each explained once (Callout kind="define"), where the term
+ * first matters on a page. Spread one into a Callout:
+ * ``.
+ */
+export const DEFINITIONS = {
+ exchange: {
+ tag: 'What is an Exchange?',
+ text: 'An Exchange represents publishers\' catalogs. One Exchange can serve as many publishers as needed with no loss for any of them, because every URL is a separate listing with its own terms. Publishers share an Exchange when they\'re happy with how its operator settles.',
+ },
+ broker: {
+ tag: 'What is a Broker?',
+ text: 'A search service for AI agents. It asks Exchanges for their signed offers and returns them in order of relevance, optionally narrowed to the kinds of license the agent asks for. The agent decides what it buys, where and why. A Broker never buys, sells or charges, and it can\'t change an offer.',
+ },
+ operator: {
+ tag: 'What is an operator?',
+ text: 'The company that runs an Exchange, and often the publisher console that comes with it. It bills buyers and pays publishers under its own rules.',
+ },
+ edgeFunction: {
+ tag: 'What is the edge function?',
+ text: 'FORA\'s small program on your CDN, on Cloudflare, Fastly or Amazon CloudFront. On the paths you license, it refuses AI bots that come without a signed link, and serves the agents that bring one. Readers and search crawlers pass as before.',
+ },
+ signedLink: {
+ tag: 'What is a signed link?',
+ text: 'A short-lived link to one page, bound to the agent that bought it. Your CDN checks it before your site serves the page.',
+ },
+ dealTerm: {
+ tag: 'What is a deal term?',
+ text: 'For a buyer that already pays you under a contract, your Exchange can show a term priced at zero that only agents naming that deal see. The buyer still owes a usage report. The Exchange doesn\'t verify the name. A false claim is signed, so it can be traced to the key that signed it.',
+ },
+} as const;
+
+/**
+ * The search callout's FORA half. A vendor page writes one or two sentences
+ * on what the vendor does to search crawlers, then this text and these links:
+ * `…`.
+ */
+export const SEARCH_FORA = {
+ text: 'FORA\'s edge never refuses Googlebot, Bingbot or Applebot. On the paths you license it refuses AI bots that come without a signed link, AI search crawlers such as PerplexityBot included, by default. The lists are yours to change.',
+ links: [
+ { href: '/resources/ai-crawlers/', text: 'How to control which bots get in →' },
+ { href: '/components/edge-function/bot-detection/', text: 'Bot detection' },
+ ],
+};
+
+/** The comparison table's eight questions, in this order, on every vendor page. */
+export const COMPARE_QUESTIONS = [
+ 'How do you say what\'s for sale?',
+ 'How does a buyer find your content?',
+ 'Who is the buyer, provably?',
+ 'What lets a given use happen?',
+ 'Who sets the price, in what unit?',
+ 'How does money move?',
+ 'What do you see?',
+ 'What if the numbers are wrong?',
+] as const;
+
+type Eight = [T, T, T, T, T, T, T, T];
+
+/** One [vendor, FORA] pair per question, in the order of COMPARE_QUESTIONS. */
+export function compareRows(cells: Eight<[string, string]>) {
+ return COMPARE_QUESTIONS.map((q, i) => ({ q, cells: cells[i] }));
+}
+
+/** At a glance (GlanceCard): two groups, the same rows in the same order on every vendor page. */
+export const GLANCE_GROUPS = [
+ {
+ name: 'Money',
+ rows: [
+ { key: 'payer', label: 'Who pays you, and when' },
+ { key: 'fees', label: 'Fees' },
+ { key: 'reporting', label: 'What you see' },
+ { key: 'contract', label: 'Contract' },
+ { key: 'status', label: 'Status' },
+ ],
+ },
+ {
+ name: 'Your stack',
+ rows: [
+ { key: 'dns', label: 'DNS' },
+ { key: 'cdn', label: 'CDN' },
+ { key: 'firewall', label: 'Firewall and bot shield' },
+ { key: 'site', label: 'Your site and CMS' },
+ { key: 'search', label: 'Search traffic' },
+ { key: 'upkeep', label: 'Upkeep' },
+ { key: 'leaving', label: 'Leaving' },
+ ],
+ },
+] as const;
+export type GlanceKey = (typeof GLANCE_GROUPS)[number]['rows'][number]['key'];
+
+/** The GlanceCard's groups, from one [vendor, FORA] pair per row key. */
+export function glanceGroups(cells: Record) {
+ return GLANCE_GROUPS.map((g) => ({
+ name: g.name,
+ rows: g.rows.map((r) => ({ label: r.label, cells: cells[r.key] })),
+ }));
+}
+
+/** FORA's cells that read the same on every page (settled 2026-11-15; CDN, fifth round). */
+export const FORA_CELLS = {
+ /** GlanceCard, "Who pays you, and when". */
+ payer: `Your Exchange operator, under its own terms. ${SEE_ABOUT}`,
+ /** GlanceCard, "Fees". */
+ fees: `No Exchange fee at FORA's publisher console, beyond the payment system's. ${SEE_ABOUT}`,
+ /** GlanceCard, "CDN" (fifth round: a drop-in, no minutes). */
+ cdn: 'A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.',
+ /** GlanceCard, "Leaving". */
+ leaving: 'Delete the edge function from your CDN.',
+ /** Comparison table, "How does money move?". */
+ money: `Outside the protocol. ${SEE_ABOUT}`,
+ /** Comparison table, "What if the numbers are wrong?". */
+ disputes: `Defined in the protocol, handled under your operator's rules. ${SEE_ABOUT}`,
+};
+
+/** The series' section on the Resources index. */
+export const SERIES_SECTION = {
+ name: 'Content marketplaces and standards',
+ intro: 'Who pays publishers for AI use today, how each channel works on your site, and which standards declare what. Start with the map.',
+};
+
+export interface SeriesPage {
+ href: string;
+ title: string;
+ /** The Resources index card. */
+ summary: string;
+ audience: string;
+ formats: string[];
+ updated: string;
+ /**
+ * False until the page exists. The Resources index lists only built pages,
+ * so it never links a route the site doesn't serve; "More in this series"
+ * lists all seven, as the copy has it.
+ */
+ built: boolean;
+}
+
+/** The seven pages, in the order the index and "More in this series" list them. */
+export const SERIES: SeriesPage[] = [
+ {
+ href: '/resources/content-marketplaces/',
+ title: 'Content marketplaces and FORA',
+ summary: 'Who pays publishers for AI use of their content today, how each channel works, what your engineers change for it, and how FORA, the open protocol any company can run a marketplace on, works beside all of them.',
+ audience: 'Publishers',
+ formats: ['Guide', 'Map'],
+ updated: '2026-11-15',
+ built: true,
+ },
+ {
+ href: '/resources/content-marketplaces/tollbit/',
+ title: 'TollBit and FORA',
+ summary: 'How TollBit charges AI bots for your pages, what your engineers set up for it, and how to run both on one site.',
+ audience: 'Publishers and engineers',
+ formats: ['Guide'],
+ updated: '2026-11-15',
+ built: true,
+ },
+ {
+ href: '/resources/content-marketplaces/cloudflare/',
+ title: 'Cloudflare and FORA',
+ summary: 'How Cloudflare charges AI crawlers at its edge, what that takes on your site, and how a publisher on Cloudflare can run both.',
+ audience: 'Publishers and engineers',
+ formats: ['Guide'],
+ updated: '2026-11-15',
+ built: true,
+ },
+ {
+ href: '/resources/content-marketplaces/microsoft-pcm/',
+ title: 'Microsoft Publisher Content Marketplace and FORA',
+ summary: 'How Microsoft\'s pilot marketplace licenses content to Copilot, what it asks of your site, and how to use both.',
+ audience: 'Publishers',
+ formats: ['Guide'],
+ updated: '2026-11-15',
+ built: true,
+ },
+ {
+ href: '/resources/content-marketplaces/prorata-gist/',
+ title: 'ProRata.ai and Gist, and FORA',
+ summary: 'How ProRata pays a share of each Gist answer, what Gist Answers needs from your site, and how to run both.',
+ audience: 'Publishers',
+ formats: ['Guide'],
+ updated: '2026-11-15',
+ built: true,
+ },
+ {
+ href: '/resources/content-marketplaces/perplexity/',
+ title: "Perplexity's Publishers' Program and Comet Plus, and FORA",
+ summary: 'How Comet Plus is built to pay publishers from subscription revenue, what it asks of your site, and how to run both.',
+ audience: 'Publishers',
+ formats: ['Guide'],
+ updated: '2026-11-15',
+ built: true,
+ },
+ {
+ href: '/resources/standards-map/',
+ title: 'The standards map',
+ summary: 'Thirteen open standards tell a machine something about your content: what each answers, who uses it, how they stack, and where FORA sits.',
+ audience: 'Publishers and engineers',
+ formats: ['Guide', 'Table'],
+ updated: '2026-11-15',
+ built: true,
+ },
+];
diff --git a/website/src/data/resources.ts b/website/src/data/resources.ts
index bc679fc7..ed581d1a 100644
--- a/website/src/data/resources.ts
+++ b/website/src/data/resources.ts
@@ -1,7 +1,11 @@
// The Resources section (/resources/): one entry per topic, in the order the
// index lists them. A topic has one page that holds its article and its
// formats (slides, a generator, a video); `formats` names what that page has.
-// Topics that live elsewhere on the site link there.
+// Topics that live elsewhere on the site link there. A topic with a `section`
+// is listed under that section's heading (SECTIONS), after the topics
+// without one; a series of pages, such as the content marketplaces, is one
+// section.
+import { SERIES, SERIES_SECTION } from './content-marketplaces';
export interface Resource {
href: string;
@@ -11,8 +15,13 @@ export interface Resource {
formats: string[];
/** ISO date of the last substantive update. */
updated: string;
+ /** The name of the section the index lists it under; one of SECTIONS. */
+ section?: string;
}
+/** The index's sections, in order, each with a heading and an intro. */
+export const SECTIONS: { name: string; intro: string }[] = [SERIES_SECTION];
+
export const RESOURCES: Resource[] = [
{
href: '/resources/ai-crawlers/',
@@ -70,6 +79,10 @@ export const RESOURCES: Resource[] = [
formats: ['Walkthrough'],
updated: '2026-11-10',
},
+ // The content-marketplaces series, in its own order; a page is listed once it is built.
+ ...SERIES.filter((p) => p.built).map(({ href, title, summary, audience, formats, updated }) => ({
+ href, title, summary, audience, formats, updated, section: SERIES_SECTION.name,
+ })),
];
/** The date a resource page shows in its hero: its entry's `updated`. */
diff --git a/website/src/lib/resource-markup.ts b/website/src/lib/resource-markup.ts
new file mode 100644
index 00000000..25a9fb25
--- /dev/null
+++ b/website/src/lib/resource-markup.ts
@@ -0,0 +1,19 @@
+// Inline markup for resource pages that also appears inside HTML strings (a
+// GlanceCard cell, a table cell, a step): a status tag and a citation marker.
+// Their styles are global, in styles/landing.css ("Resource-page atoms"), so
+// they look the same wherever a string lands. StatusTag.astro renders the same
+// markup as statusTag(), so a tag in a component and a tag in a string match.
+import { STATUS, type StatusKey } from '../data/content-marketplaces';
+
+/** A status pill: Live, Beta, Closed beta, Pilot, Design, Roadmap, Not public. */
+export function statusTag(status: StatusKey): string {
+ return `${STATUS[status].label}`;
+}
+
+/**
+ * Citation markers: cite(1, 2) gives "[1, 2]", each number linked to its
+ * entry in the page's numbered SourceList (id="src-N").
+ */
+export function cite(...n: number[]): string {
+ return `[${n.map((i) => `${i}`).join(', ')}]`;
+}
diff --git a/website/src/pages/about.astro b/website/src/pages/about.astro
new file mode 100644
index 00000000..53f5a525
--- /dev/null
+++ b/website/src/pages/about.astro
@@ -0,0 +1,250 @@
+---
+// About FORA: why FORA exists, what it is, the company and the people who
+// build it, and how the protocol is developed. Built from the landing
+// components (src/components/landing/), like /publishers/. The positioning
+// statement and the tagline are shared with the content-marketplaces page
+// through src/data/content-marketplaces.ts. remark-standards runs on .mdx
+// only, so the standards in "How FORA is developed" are linked here by hand:
+// from src/data/standards.mjs where it lists them, and otherwise to the pages
+// the standards map links (/resources/standards-map/).
+import LandingLayout from '../layouts/LandingLayout.astro';
+import AudienceHero from '../components/landing/AudienceHero.astro';
+import Band from '../components/landing/Band.astro';
+import CardGrid from '../components/landing/CardGrid.astro';
+import PointList from '../components/landing/PointList.astro';
+import PullQuote from '../components/landing/PullQuote.astro';
+import LinkRow from '../components/landing/LinkRow.astro';
+import ClosingCta from '../components/landing/ClosingCta.astro';
+import { FORA_PUBLISHER_CONSOLE_URL } from 'astro:env/client';
+import { POSITIONING, TAGLINE } from '../data/content-marketplaces';
+import { STANDARDS } from '../data/standards.mjs';
+import { REPO_URL, BUILD_LINKS } from '../consts';
+
+const SERVER_URL = BUILD_LINKS.find((l) => l.label === 'FORA Server')!.url;
+const ISSUES_URL = `${REPO_URL}/issues`;
+const a = (href: string, text: string) => `${text}`;
+const std = (id: string, text: string) => a(STANDARDS.find((s) => s.id === id)!.url, text);
+
+// The v1 announcement on LinkedIn, 10 September 2026.
+const V1_POST = 'https://lnkd.in/p/dxJURtKj';
+
+const WHAT = [
+ {
+ title: 'An open protocol',
+ text: 'A public specification anyone can implement. Six steps take an agent from finding a resource to proving what it got: Discover, Query, Transact, Deliver, Report and Dispute.',
+ },
+ {
+ title: 'Free, open-source software',
+ text: 'FORA Server runs the whole stack: Exchange, Broker and search, identity and registration, content ingestion, an MCP endpoint and edge protection. Run all of it or one piece. SDKs for Go, TypeScript and Python.',
+ },
+ {
+ title: 'Federated, with no central registry',
+ text: 'Each marketplace, called an Exchange, runs on its own and sets its own terms. An agent registers at each Exchange it buys from, and uses the same SDK for all of them.',
+ },
+];
+
+const PEOPLE = [
+ { title: 'Constantine Mirin', text: 'CEO of Postindustria and co-author of the FORA protocol.' },
+ { title: 'Eugene Dymo', text: 'Technical Partner at Postindustria. He works on the FORA protocol and its documentation.' },
+ { title: 'Yaroslav Krasilchuk', text: 'Senior Agentic Engineer at Postindustria. He works on the FORA protocol and FORA Server.' },
+ { title: 'Serge Shtyk', text: 'Engineer. He works on FORA Server.' },
+];
+
+const OPEN = [
+ {
+ title: 'A public specification.',
+ text: `The protocol, its schemas and these docs live in one public repository, ${a(REPO_URL, 'FORA-Protocol/protocol')}. Changes land as pull requests anyone can read, and the ${a('/reference/changelog/', 'changelog')} lists every release.`,
+ },
+ {
+ title: 'A stable v1.',
+ text: 'FORA v1 was released on 10 September 2026. Within v1, fields and values can be added, and nothing already shipped is renamed, renumbered, retyped or removed. Every build checks this.',
+ },
+ {
+ title: 'Open licenses.',
+ text: `The protocol specification and FORA Server are open source under Apache 2.0, and the documentation is CC BY-ND 4.0. Deploy it without asking anyone. The ${a('/brand/', 'brand guidelines')} cover the FORA name and logo.`,
+ },
+ {
+ title: 'Built on open work.',
+ text: `FORA reads ${std('rsl', 'RSL')}, IAB Tech Lab's ${a('https://github.com/IABTechLab/CoMP', 'CoMP')}, ${a('https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/', 'TDMRep')} and ${std('c2pa', 'C2PA')}, and identifies agents with ${std('webbotauth-httpsig-protocol-00', 'Web Bot Auth')}. It is the transaction layer between them.`,
+ },
+];
+---
+
+
+ Read the protocol
+ Code on GitHub
+
+
+
+
Gutefrage runs the whole FORA stack itself, on its own servers, and has launched it on helpster.de. Its Broker searches the index Gutefrage already runs, and Gutefrage decides which fields are searched and how results rank.
+
+
+
+
+
+
The goal is for FORA to be used as widely as possible: by publishers, AI companies, marketplaces and anyone else who works with content. We help everyone who tries it, and we want everyone who builds on it to win.
+
Postindustria develops FORA, the protocol and FORA Server, and hosts a ready-made deployment with a publisher console, so a publisher can try it and start selling. It charges publishers no fee beyond the payment system's transaction fees. Anyone else can run the same: Gutefrage runs its own, and the code is open to clone.
FORA needs more than code. We want people who will use it, test it, argue with it and run it: publishers and the platforms that monetize them, AI companies building agents, content libraries and music distributors, legal and product teams, and researchers.
+
If you see a gap, a better way, or a use we haven't thought of, tell us.
Nobody browses a cable shop's website. People go where one search covers every store. That is how marketplaces won.
Now agents do the searching, and the buying, for articles, music, data and files. Selling to them will soon be as obvious as selling online.
-
Marketplaces put a middleman between you and the buyer. FORA doesn't. It is an open protocol: no one owns the customer, and your terms travel with your content.
+
No one owns your customer. FORA is an open protocol: any agent can buy from any FORA marketplace, including your own, and your terms travel with your content.
diff --git a/website/src/pages/resources/ai-crawlers.astro b/website/src/pages/resources/ai-crawlers.astro
index 913b2f5b..f77cf92f 100644
--- a/website/src/pages/resources/ai-crawlers.astro
+++ b/website/src/pages/resources/ai-crawlers.astro
@@ -99,7 +99,7 @@ const FAQ = [
title="Each AI company reads its own refusal"
lead="The AI companies treat their uses as allowed unless a site refuses them, and there is no single signal they all honor. So a refusal has to be said in each vendor's own form, in up to four places."
>
-
+
-
+ `${text}`;
+
+const GLANCE = glanceGroups({
+ payer: [`Cloudflare, as merchant of record, monthly, to a new Stripe Connect account, after settlement periods and payout thresholds ${cite(1, 2)}.`, FORA_CELLS.payer],
+ fees: ['Not public. Cloudflare\'s docs, posts and terms state no fee.', FORA_CELLS.fees],
+ reporting: [
+ `Which crawlers visit and how often they're charged. Your earnings balance isn't in the dashboard ${cite(3)}.`,
+ `Each sale with its usage-report status, and daily income with a CSV download, in your operator's publisher console ${cite(33)}.`,
+ ],
+ contract: [
+ `Pay Per Crawl's program terms: not public. Pay Per Use: each program's terms say what the buyer may do ${cite(4)}. No dispute process documented.`,
+ `Your agreement with your Exchange operator. Your terms go into each offer the Exchange signs ${cite(34)}. Disputes: see About FORA.`,
+ ],
+ status: [
+ `Pay Per Crawl ${statusTag('closed-beta')}, charging listed under Enterprise plans with Bot Management ${cite(1, 5)}. Pay Per Use ${statusTag('beta')} ${cite(4)}. No AI company named as paying through Pay Per Crawl.`,
+ `${statusTag('live')} ${SEE_ABOUT}`,
+ ],
+ dns: [
+ `Cloudflare's nameservers, with DNSSEC off first, or your own DNS provider on Business or Enterprise ${cite(6, 7, 8)}. Every web hostname routed through Cloudflare ${cite(9)}.`,
+ `No record to add ${cite(33)}.`,
+ ],
+ cdn: [
+ `Cloudflare only ${cite(6)}.`,
+ 'A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.',
+ ],
+ firewall: [
+ `Your rules run first, so a crawler they block is never offered a price ${cite(10)}. Turn off Block AI Bots to join ${cite(11)}.`,
+ `Your WAF and bot product run first. Let signed requests and your two files through them; FORA's guide gives two setups ${cite(35)}.`,
+ ],
+ site: [
+ `No change for one price. A price per page needs a response header from your origin or a Worker ${cite(12)}.`,
+ `One file, fora.json, naming your Exchanges, and a sitemap the operator imports your pages from ${cite(33)}.`,
+ ],
+ search: [
+ `Only crawlers you set to Charge pay. Cloudflare warns that charging a search crawler may hurt your SEO ${cite(13)}.`,
+ `Googlebot, Bingbot and Applebot always pass ${cite(35)}. See Search traffic, below.`,
+ ],
+ upkeep: [
+ `Cloudflare keeps the list of crawlers you can charge ${cite(14)}. Logpush can't fill in the past, and logs are lost while a job fails ${cite(15)}.`,
+ `Change your Exchanges by editing your discovery file, with nothing to redeploy ${cite(33)}.`,
+ ],
+ leaving: ['The docs describe no step to turn Pay Per Crawl off, close its Stripe account or take a final payout.', FORA_CELLS.leaving],
+});
+
+const SHORT_ANSWER = [
+ { title: 'Cloudflare charges at the door.', text: 'Pay Per Crawl charges a crawler one price per page, and Cloudflare collects and pays out. In Pay Per Use, an AI company proposes a price for a use, and you accept or decline. Both are in beta. Pay Per Crawl needs your site\'s traffic to run through Cloudflare.' },
+ { title: 'FORA sells the license.', text: 'You set the uses, buyers, caps and price for each resource, and can offer one article on several terms. An AI agent (software that acts for a user, one task at a time) buys under an offer your Exchange signs. Pay Per Crawl needs no Exchange of yours, because Cloudflare is one.' },
+ { status: 'closed-beta' as const, title: 'Pay Per Crawl is by admission only.', text: 'Cloudflare\'s plan table lists charging under Enterprise plans with Bot Management. You need a new Stripe account, and your balance isn\'t in the dashboard. Cloudflare names no AI company paying through it.' },
+];
+
+const PPC_STEPS = [
+ { title: 'Your site runs through Cloudflare, and is admitted.', text: `"Your domain must be using Cloudflare's nameservers, or have DNS records managed by Cloudflare" (${a(C.enable, 'Enable in account settings')}). The program is a closed beta (${a(C.whatIs, 'What is Pay Per Crawl')}). The plan table lists charging under Enterprise plans with Bot Management (${a(C.getStarted, 'Get started')}).` },
+ { title: 'You set one price and pick who pays it.', text: `Cloudflare lists the AI crawlers it knows, and you set each one to Charge, Allow or Block. Cloudflare says "you can only set a single price" for every crawler set to Charge (${a(C.faq, 'FAQ')}), and "The minimum price is $0.001 USD per crawl" (${a(C.setPrice, 'Set a price')}).` },
+ { title: 'The crawler registers.', text: `It signs its requests with Web Bot Auth, an IETF draft for signing bot requests. It passes Cloudflare's review and connects Stripe (${a(C.crawlPages, 'Crawl pages')}).` },
+ { title: 'Cloudflare quotes.', text: 'An unpaid request gets HTTP 402, Payment Required, with the price. The crawler retries with a signed agreement to it, or states a maximum up front.' },
+ { title: 'Cloudflare charges each successful fetch.', text: `"Error responses are not billed", and a crawler "will incur the cost set by the site owner" on every visit (${a(C.faq, 'FAQ')}).` },
+ { title: 'Cloudflare pays you.', text: `"Cloudflare acts as the Merchant of Record for pay per crawl" (${a(C.whatIs, 'What is Pay Per Crawl')}): it is the party that takes the crawler's payment. It pays monthly to a dedicated Stripe Connect account, "subject to settlement periods and minimum payout thresholds" (${a(C.payouts, 'Manage payouts')}).` },
+];
+
+const KEY_FACTS = [
+ { value: '$0.001', text: `The lowest price you can set per crawl ${cite(17)}` },
+ { value: '1', text: `Price for every crawler you set to Charge, unless your origin or a Worker prices each page ${cite(12, 16)}` },
+ { value: '20%+', text: `Of the web behind Cloudflare's network, the vendor's own figure ${cite(19)}` },
+];
+
+const SETUP = [
+ { title: 'Your DNS and proxy.', text: `Your domain moves to Cloudflare's nameservers, and "If your domain uses DNSSEC, you must turn it off at your registrar before changing nameservers" (${a(C.onboard, 'Onboard a domain')}). Keeping your DNS provider is "only available to customers on a Business or Enterprise plan" (${a(C.cname, 'CNAME setup')}). A hostname not routed through Cloudflare (left unproxied) never meets Pay Per Crawl (${a(C.proxy, 'Proxy status')}).` },
+ { title: 'Your content stays on your servers.', text: `Cloudflare keeps no copy or catalog of your pages. A crawler gets the list of domains that charge it and finds the pages itself (${a(C.discover, 'Discover payable content')}). "The Cloudflare CDN does not cache HTML or JSON by default", so each crawl normally reaches your origin (${a(C.cache, 'Default cache behavior')}).` },
+ { title: 'Cloudflare decides which bots you can charge.', text: `You choose Charge, Allow or Block only for crawlers on Cloudflare's list. Bot operators apply to join it, and "Cloudflare reserves the right to re-assign Verified bot categories" (${a(C.verifiedBots, 'Verified bots')}). On the free plan, AI Crawl Control "identifies AI crawlers based on their user agent strings" (${a(C.manage, 'Manage AI crawlers')}).` },
+ { title: 'Your other rules run first.', text: `Firewall rules and bot tools act before Pay Per Crawl, so a crawler they block is never offered a price (${a(C.waf, 'AI Crawl Control with WAF')}).` },
+ { title: 'Per-page prices need a header.', text: `Since June 2026, your origin or a Worker can price each page in a response header (${a(C.advanced, 'Advanced configuration')}).` },
+ { title: 'Refusals and redirects.', text: `A blocked crawler gets a 403 (refused), or on paid plans a 402 (pay first) with a message of your own (${a(C.manage, 'Manage AI crawlers')}). The one redirect shipped sends a verified AI crawler to the page's canonical URL (${a(C.redirects, 'Redirects for AI Training')}), not to a license or a marketplace.` },
+ { title: 'Logs.', text: `Cloudflare's log export, Logpush, streams each request with a Pay Per Crawl outcome, whose values aren't listed (${a(C.logpush, 'Logpush')}).` },
+ { title: 'FORA agents and Cloudflare\'s signature check.', text: `Cloudflare's verifier reads an older form of Web Bot Auth than the one FORA's software sends, and "will fail to verify a message if" it uses the later form (${a(C.webBotAuth, 'Web Bot Auth')}). So Cloudflare can't verify a FORA agent by its signature, and the agent can't pay Pay Per Crawl with it. FORA sales don't depend on it: the agent brings a signed link, which FORA's Worker checks. Let signed requests through your rules, as under Running both. The working group's -01, of 2026-10-29, lets a verifier accept Cloudflare's older form and tells signers to send the form FORA's software sends (${a(C.draft01, 'draft-ietf-webbotauth-httpsig-protocol-01')}).` },
+];
+
+const CAUTIONS = [
+ { title: 'Your balance comes on request.', text: `"You can request balance updates from your Cloudflare team" (${a(C.monitor, 'Monitor activity')}).` },
+ { title: 'You need a new Stripe account.', text: `"Pre-existing Stripe accounts are not compatible with this feature" (${a(C.payouts, 'Manage payouts')}).` },
+ { title: 'Logs can be lost.', text: `"If your job is disabled or fails, logs generated during that period are permanently lost" (${a(C.logpush, 'Logpush')}). Logpush is billed per gigabyte above 25 GB a month on the Free to Business plans (${a(C.logpushPricing, 'Logpush pricing')}).` },
+ { title: 'Country blocks win.', text: `Crawlers from countries you block "will continue to be blocked, even if they provide the required headers" (${a(C.waf, 'AI Crawl Control with WAF')}).` },
+ { title: 'A bad price is your error.', text: `An invalid per-page price reaches the crawler as an error: "This is a site owner configuration issue" (${a(C.errors, 'Error codes')}).` },
+];
+
+const AHEAD_FIRST = [
+ { title: 'It enforces where FORA can\'t.', text: `"More than 20% of the web sits behind Cloudflare's network" (${a(C.smarter, 'Making AI search smarter')}, published 2026-07-01; vendor's own figure). A crawler you set to Charge with no billing relationship gets "the functional equivalent of a network level block" (${a(C.launch, 'launch post')}, published 2025-07-01). In July 2026, Cloudflare announced that on 2026-09-15 it would change the settings of every free customer that hadn't changed them (${a(C.press, 'press release')}). FORA's edge function refuses unlicensed AI bots only on the sites that install it.` },
+];
+const AHEAD_REST = [
+ { title: 'It detects bots, and FORA uses that.', text: `Cloudflare verifies a bot by its signature, a published IP list or reverse DNS (${a(C.verifiedBots, 'Verified bots')}).` },
+ { title: 'It moves the money.', text: `Cloudflare is the merchant of record ${cite(1)}. In 2025 it said beta crawlers are "charged a single fee via a connected credit card or bank account at the end of each day" (${a(C.x402, 'x402 post')}, published 2025-09-23). FORA never moves money, by design. ${SEE_ABOUT}` },
+ { title: 'The price travels in HTTP.', text: `A registered crawler reads the price from a 402 response and agrees to it with one signed header (${a(C.crawlPages, 'Crawl pages')}). A FORA purchase takes protocol calls, in practice through an SDK or FORA Server's Identity Service.` },
+ { title: 'No code, on a site already on Cloudflare.', text: `There, one price for your site takes dashboard settings, admission to the beta, a review of your security rules and a new Stripe account. Pay Per Use needs "no origin change" ${cite(4)}. FORA needs a fora.json file, the edge function and an Exchange.` },
+];
+
+const COMPARE = compareRows([
+ [
+ `Dashboard settings: allow, charge or block per listed crawler, one price, free paths ${cite(12, 13, 16)}. Preferences go in robots.txt as Content Signals, a line that states a preference with no price ${cite(30)}. Cloudflare's docs describe no license in the 402.`,
+ `A file on your site names your Exchanges ${cite(34)}. Each resource can carry several terms, up to 32: uses, buyers, places, caps, duties and a price ${cite(36)}.`,
+ ],
+ [
+ `A registered crawler asks Cloudflare for the domains that charge it, finds pages itself, and gets each page's price from a 402 ${cite(18, 20)}. Pay Per Use: the domains that accepted its offer ${cite(4)}.`,
+ `An agent asks your Exchange, or a Broker, which returns the signed offers whole (${a('/resources/content-marketplaces/#broker-order', 'how a Broker orders offers')}) ${cite(37)}.`,
+ ],
+ [
+ `A Web Bot Auth signature in an older draft's form, which deployed crawlers still send, plus a reviewed registration ${cite(18, 24, 40)}. On the free plan, the user agent ${cite(22)}.`,
+ `A Web Bot Auth signature in the form of the working group's first draft (-00), checked against a key on the buyer's domain ${cite(38)}.`,
+ ],
+ [
+ `Cloudflare's edge, per request: a verified crawler set to Charge, with a signed price ${cite(18)}. Use limits sit in robots.txt, or in each Pay Per Use program's terms ${cite(3, 4)}.`,
+ `An offer the Exchange signs and the agent accepts and signs, then a signed link that expires, checked at your CDN ${cite(34)}.`,
+ ],
+ [
+ `You: one price per fetch for every charged crawler, or a price per page ${cite(12, 16)}. Pay Per Use: the buyer sets a price per use; you accept or decline ${cite(4)}.`,
+ `You, per term: free, per unit (a fetch, an access, a token) or flat. One article can be free for research and paid for commercial use. No revenue-share price ${cite(36)}.`,
+ ],
+ [`Cloudflare charges the buyer through Stripe and pays you monthly ${cite(2)}. Its fee isn't published.`, FORA_CELLS.money],
+ [
+ `Which crawlers visit, how often they're charged, robots.txt violations. "Your accrued earnings balance is not currently visible in the dashboard." (${a(C.monitor, 'Monitor activity')})`,
+ `A signed record of each sale, with its usage-report status, in the publisher console your Exchange operator runs ${cite(34)}. No protocol call returns your sales.`,
+ ],
+ [`No dispute process is documented. Pay Per Use reports are the buyer's own; Cloudflare checks each names an enrolled site ${cite(4)}.`, FORA_CELLS.disputes],
+]);
+
+const WORKS = [
+ { title: 'FORA\'s edge runs on Cloudflare.', text: `On Cloudflare, FORA's edge function is a Worker on a route that covers your hostname. It gets both Cloudflare's detection, through its verified-bot signal, and FORA's own lists, and the deployment is yours. Cloudflare's protections, AI Crawl Control included, run first, so let signed requests, your FORA and RSL files, and the Exchange's reads of your sitemap through them.FORA's guide gives two setups: the edge function decides for every client on the paths you license, or your bot product stays in front and signed requests skip it (${a('/components/edge-function/bot-detection/#cloudflare', 'Bot detection')}). The edge function also runs on CloudFront, so FORA doesn't need Cloudflare's DNS.` },
+ { title: 'Point every crawler at your license.', text: `Cloudflare documents a rule that adds a link to your terms or RSL license to its responses, "even when those crawlers are blocked" (${a(C.transform, 'Transform Rules')}).` },
+ { title: 'Keep your signals and terms in step.', text: `Cloudflare's Markdown for Agents adds a signal allowing training when your origin sends none (${a(C.markdown, 'Markdown for Agents')}). If a FORA term forbids training, send a signal that says so.` },
+];
+
+const TODO = [
+ { title: 'Decide per crawler first.', text: `AI Crawl Control allows or blocks each crawler on every plan, with no beta to wait for (${a(C.getStarted, 'Get started')}).` },
+ { title: 'Check your Cloudflare setup before you join.', text: `Every web hostname must run through Cloudflare's proxy. List the firewall and bot rules that would block a crawler you want to charge. Pay Per Crawl runs after Cloudflare's bot tools, so "you need to first turn off Block AI Bots" (${a(C.bots, 'AI Crawl Control with bots')}).` },
+ { title: 'Ask before you join Pay Per Crawl.', text: 'Ask for the fee, the payout threshold and which crawlers pay; none is published. FORA itself is free, open-source software. Agree how often you\'ll get balance updates, and plan for a new Stripe account. For the terms and the exit, see For legal.' },
+ { title: 'Start your logs on day one.', text: 'Logpush can\'t fill in the past, so set it up before the first charge.' },
+ { title: 'Sell to agents as well.', text: 'Name your FORA Exchanges in fora.json, set terms per resource, and run FORA\'s edge on the paths you license.' },
+];
+
+const LEGAL = [
+ { title: 'Pay Per Crawl\'s terms aren\'t published.', text: 'Ask for the program terms before you join. Cloudflare is the merchant of record.' },
+ { title: 'Pay Per Use sets use limits per program.', text: `Each program's terms define "what the AI company may do with the content, including any restrictions on training" (${a(C.payPerUse, 'Pay Per Use')}). The buyer reports its own uses.` },
+ { title: 'Leaving.', text: 'The docs describe no step to turn Pay Per Crawl off, close its Stripe account or take a final payout.' },
+ { title: 'Disputes.', text: 'Neither program documents a dispute process.' },
+];
+
+// The SourceList, numbered as the copy numbers it: an entry's position,
+// counted across the groups, is the N in cite(N).
+const cf = (title: string, href: string, checked = '2026-11-15') => ({ title, publisher: 'Cloudflare', href, checked });
+const fora = (title: string, href: string) => ({ title, publisher: 'FORA documentation', href, checked: '2026-11-15' });
+const SOURCES = [
+ {
+ name: 'Cloudflare',
+ items: [
+ cf('What is Pay Per Crawl?', C.whatIs),
+ cf('Manage payouts', C.payouts),
+ cf('Monitor activity', C.monitor),
+ cf('Pay Per Use', C.payPerUse, '2026-11-14'),
+ cf('Get started with AI Crawl Control', C.getStarted),
+ cf('Enable in account settings', C.enable),
+ cf('Onboard a domain', C.onboard),
+ cf('CNAME setup', C.cname),
+ cf('Proxy status', C.proxy),
+ cf('AI Crawl Control with WAF', C.waf),
+ cf('AI Crawl Control with Bots', C.bots),
+ cf('Advanced configuration', C.advanced),
+ cf('Select crawlers to charge', C.selectCrawlers),
+ cf('Verified bots', C.verifiedBots),
+ cf('Logpush', C.logpush),
+ cf('Pay Per Crawl FAQ', C.faq),
+ cf('Set a pay per crawl price', C.setPrice),
+ cf('Crawl pages', C.crawlPages),
+ cf('Making AI search smarter', C.smarter, '2026-11-14'),
+ cf('Discover payable content', C.discover),
+ cf('Default cache behavior', C.cache),
+ cf('Manage AI crawlers', C.manage),
+ cf('Redirects for AI Training', C.redirects),
+ cf('Web Bot Auth', C.webBotAuth),
+ cf('Logpush pricing', C.logpushPricing),
+ cf('Error codes', C.errors),
+ cf('Introducing pay per crawl', C.launch, '2026-11-14'),
+ cf('Cloudflare allows the agentic internet to flourish with a simple philosophy: your content, your rules', C.press, '2026-11-14'),
+ cf('x402', C.x402, '2026-11-14'),
+ cf('Managed robots.txt', C.robots),
+ cf('AI Crawl Control with Transform Rules', C.transform),
+ cf('Markdown for Agents', C.markdown),
+ ],
+ },
+ {
+ name: 'FORA',
+ items: [
+ fora('Publisher onboarding', '/getting-started/publisher-onboarding/'),
+ fora('What is FORA?', '/getting-started/what-is-fora/'),
+ fora('Bot detection', '/components/edge-function/bot-detection/'),
+ fora('Licensing terms', '/protocol/licensing-terms/'),
+ fora('The Broker', '/components/broker/overview/'),
+ fora('Authentication', '/protocol/authentication/'),
+ ],
+ },
+ {
+ name: 'Press, filings and others',
+ items: [
+ { title: 'Cloudflare says bot blocking is fueling publisher AI deals', publisher: 'Press Gazette', href: C.pressGazette, checked: '2026-11-14' },
+ { title: 'HTTP Message Signatures for automated traffic (draft-ietf-webbotauth-httpsig-protocol-01)', publisher: 'IETF', href: C.draft01, checked: '2026-11-14' },
+ ],
+ },
+];
+---
+
+
+ Where Cloudflare is ahead
+ Run both
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Pay Per Crawl, in six steps:
+
+
Pay Per Use reverses who sets the price (${a(C.payPerUse, 'Pay Per Use')}, published 2026-09-30). An AI company "defines the use it will pay for and sets a price", such as returning an excerpt of your page to a customer. You accept offers in the dashboard, with "no origin change". "Usage is self-reported": the buyer reports its own uses, and Cloudflare charges the buyer and pays you monthly. Its reason for the program: "AI products fetch far more than they use".`} />
+
Settling a FORA sale through Pay Per Crawl. Pay Per Crawl charges when a crawler fetches a page. Its docs describe no way to bill an amount for a sale made elsewhere.
+
A Cloudflare price a FORA agent can verify. Cloudflare's docs describe no signed price or receipt. The crawler gets a header that states the amount charged.
+
+
+
+
+
+
+
+
+
+
+
Sources
+
Sources are checked on the date of publication.
+
+
+
+
+
+
+ What is FORA?
+ Run your own marketplace
+ Licensing terms
+ All content marketplaces
+
+
+
+
diff --git a/website/src/pages/resources/content-marketplaces/index.astro b/website/src/pages/resources/content-marketplaces/index.astro
new file mode 100644
index 00000000..1c8f707a
--- /dev/null
+++ b/website/src/pages/resources/content-marketplaces/index.astro
@@ -0,0 +1,988 @@
+---
+// Resource: Content marketplaces and FORA, the hub of the content-marketplaces
+// series. The five deep pages sit under it at
+// /resources/content-marketplaces//. In the hub's own order: hero, the
+// short answer, what FORA takes (FORA's half of the GlanceCard, as a pair),
+// who has shown money moving (KeyFacts), the map (MarketMap), how each kind
+// works, where they are ahead, the eight questions, what changes on your CDN
+// (id="together"), when an AI company buys (with id="broker-order", which the
+// deep pages link), what to do, the deep pages, and About FORA with the
+// sources and the series navigation.
+//
+// Shared texts (About FORA, the definitions, the search callout, the glance
+// row labels and FORA's fixed cells) come from
+// src/data/content-marketplaces.ts. A claim cites its source inline, as a
+// link, or with cite(N), which links to entry N of the numbered SourceList at
+// the foot. SOURCES below is numbered in order of first citation, as the copy
+// numbers it, so an entry's position is its number; src(N) gives entry N's
+// URL for an inline link. Text with links is HTML and goes through set:html.
+import LandingLayout from '../../../layouts/LandingLayout.astro';
+import AudienceHero from '../../../components/landing/AudienceHero.astro';
+import Band from '../../../components/landing/Band.astro';
+import CardGrid from '../../../components/landing/CardGrid.astro';
+import Callout from '../../../components/landing/Callout.astro';
+import ForaGlance from '../../../components/landing/ForaGlance.astro';
+import KeyFacts from '../../../components/landing/KeyFacts.astro';
+import MarketMap from '../../../components/landing/MarketMap.astro';
+import MoneyTiles from '../../../components/landing/MoneyTiles.astro';
+import PullQuote from '../../../components/landing/PullQuote.astro';
+import PointList from '../../../components/landing/PointList.astro';
+import StepList from '../../../components/landing/StepList.astro';
+import Figure from '../../../components/landing/Figure.astro';
+import Split from '../../../components/landing/Split.astro';
+import StatusTag from '../../../components/landing/StatusTag.astro';
+import SourceList from '../../../components/landing/SourceList.astro';
+import SeriesNav from '../../../components/landing/SeriesNav.astro';
+import ClosingCta from '../../../components/landing/ClosingCta.astro';
+import { RESOURCES, resourceUpdated } from '../../../data/resources';
+import {
+ ABOUT_FORA, DEFINITIONS, SEARCH_FORA, FORA_CELLS, SEE_ABOUT, GLANCE_GROUPS, SERIES, POSITIONING, TAGLINE, type GlanceKey,
+} from '../../../data/content-marketplaces';
+import { cite, statusTag } from '../../../lib/resource-markup';
+
+const HREF = '/resources/content-marketplaces/';
+const IMG = '/resources/content-marketplaces/hub';
+const a = (href: string, text: string) => `${text}`;
+const ABOUT = 'About FORA';
+
+// The SourceList, numbered in order of first citation: an entry's position,
+// counted across the groups, is the N in cite(N).
+const SOURCES = [
+ {
+ name: 'FORA',
+ items: [
+ { title: 'Publisher onboarding', publisher: 'FORA documentation', href: '/getting-started/publisher-onboarding/', checked: '2026-11-15' },
+ { title: 'Edge function deployment', publisher: 'FORA documentation', href: '/components/edge-function/deployment/', checked: '2026-11-15' },
+ { title: 'Bot detection', publisher: 'FORA documentation', href: '/components/edge-function/bot-detection/', checked: '2026-11-15' },
+ { title: 'What is FORA?', publisher: 'FORA documentation', href: '/getting-started/what-is-fora/', checked: '2026-11-15' },
+ { title: 'Licensing terms', publisher: 'FORA documentation', href: '/protocol/licensing-terms/', checked: '2026-11-15' },
+ { title: 'Identity Service', publisher: 'FORA documentation', href: '/components/identity/overview/', checked: '2026-11-15' },
+ { title: 'Broker', publisher: 'FORA documentation', href: '/components/broker/overview/', checked: '2026-11-15' },
+ { title: 'For content marketplaces', publisher: 'FORA documentation', href: '/getting-started/existing-marketplace/', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'AI companies buying directly',
+ items: [
+ { title: '400 publications are now partnering with us on our News AI pilot program', publisher: 'Google', href: 'https://blog.google/products-and-platforms/products/news/news-ai-pilot-update-publishers/', checked: '2026-11-15' },
+ { title: 'Reddit, Inc. Form S-1', publisher: 'U.S. SEC, EDGAR', href: 'https://www.sec.gov/Archives/edgar/data/1713445/000162828024006294/reddits-1q423.htm', checked: '2026-11-14' },
+ { title: 'Google Search Console testing paying publishers for use of content in AI: AI Contribution Pilot', publisher: 'Search Engine Roundtable', href: 'https://www.seroundtable.com/google-al-contribution-pilot-42076.html', checked: '2026-11-15' },
+ { title: 'The Extended News Previews Program', publisher: 'Google Search Console Help', href: 'https://support.google.com/webmasters/answer/11317369?hl=en', checked: '2026-11-15' },
+ { title: 'Google is paying 100 publishers for AI answers, The Information reports', publisher: 'TNW', href: 'https://thenextweb.com/news/google-ai-contribution-pilot-publishers-payments', checked: '2026-11-15' },
+ { title: 'Building toward a sustainable content economy for the agentic web', publisher: 'Microsoft Advertising', href: 'https://about.ads.microsoft.com/en/blog/post/february-2026/building-toward-a-sustainable-content-economy-for-the-agentic-web', checked: '2026-11-15' },
+ { title: 'Who\'s suing AI and who\'s signing', publisher: 'Press Gazette', href: 'https://pressgazette.co.uk/platforms/news-publisher-ai-deals-lawsuits-openai-google/', checked: '2026-11-14' },
+ { title: 'Anthropic strikes its first licensing deal, with the AP, for election coverage', publisher: 'Adweek', href: 'https://www.adweek.com/media/anthropic-licensing-deal-ap-election/', checked: '2026-11-14' },
+ { title: 'OpenAI, Grupo Folha and Grupo UOL announce strategic content partnership', publisher: 'OpenAI', href: 'https://openai.com/index/grupo-folha-grupo-uol-partnership/', checked: '2026-11-14' },
+ { title: 'OpenAI signs first Brazilian content licensing deals with Folha and UOL', publisher: 'LatAm Journalism Review', href: 'https://latamjournalismreview.org/news/openai-signs-first-brazilian-content-licensing-deals-with-folha-and-uol/', checked: '2026-11-14' },
+ { title: 'How HTTP status codes affect Google\'s crawlers', publisher: 'Google Search Central', href: 'https://developers.google.com/crawling/docs/troubleshooting/http-status-codes', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Collectives and rights agencies',
+ items: [
+ { title: 'Agreement on the use of copyright-protected material in the training of Norwegian language models', publisher: 'Kopinor', href: 'https://kopinor.no/wp-content/uploads/2026/02/Agreement-on-the-use-of-copyright-protected-material-in-the-training-of-Norwegian-language-models.pdf', checked: '2026-11-14' },
+ { title: 'Collective licensing for the AI-first internet', publisher: 'Internet Licensing Collective', href: 'https://internetcollective.org/', checked: '2026-11-14' },
+ { title: 'AI Systems Training License: frequently asked questions (FY26)', publisher: 'CCC', href: 'https://www.copyright.com/crc/wp-content/uploads/sites/2/FY26-FAQ-ASTL-A4.pdf', checked: '2026-11-15' },
+ { title: 'CCC launching new AI content re-use rights for U.S. academic customers and transactional licensing capabilities for AI', publisher: 'CCC', href: 'https://www.copyright.com/media-press-releases/ccc-launching-new-ai-content-re-use-rights-for-u-s-academic-customers-and-transactional-licensing-capabilities-for-ai/', checked: '2026-11-15' },
+ { title: 'CCC Marketplace: title search and permission request', publisher: 'CCC', href: 'https://marketplace.copyright.com/rs-ui-web/mp/search', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Bot paywalls at your CDN',
+ items: [
+ { title: 'The Washington Post\'s Arc XP adds TollBit to help publishers make money from AI bot traffic', publisher: 'Digiday', href: 'https://digiday.com/media/the-washington-posts-arc-xp-adds-tollbit-to-help-publishers-make-money-from-ai-bot-traffic/', checked: '2026-11-14' },
+ { title: 'Content License Agreement (standard license)', publisher: 'TollBit', href: 'https://gateway.tollbit.com/license/j4ikxb8qqsu2qu91q78a9e70/ON_DEMAND_LICENSE_ka02vqvjacoy2i5vs8z90hxm', checked: '2026-11-15' },
+ { title: 'Setting rates', publisher: 'TollBit docs', href: 'https://docs.tollbit.com/docs/setting-rates', checked: '2026-11-14' },
+ { title: 'Platform overview', publisher: 'TollBit', href: 'https://tollbit.com/docs/', checked: '2026-11-15' },
+ { title: 'Announcing our Series A', publisher: 'TollBit blog', href: 'https://tollbit.com/blog/series-a/', checked: '2026-11-14' },
+ { title: 'TNL Mediagene announces early success in AI content licensing revenue model via TollBit marketplace integration and strategic partnership', publisher: 'PR Newswire', href: 'https://www.prnewswire.com/news-releases/tnl-mediagene-announces-early-success-in-ai-content-licensing-revenue-model-via-tollbit-marketplace-integration-and-strategic-partnership-302647966.html', checked: '2026-11-14' },
+ { title: 'Enable analytics', publisher: 'TollBit docs', href: 'https://docs.tollbit.com/docs/step-2-enable-analytics', checked: '2026-11-15' },
+ { title: 'Platform architecture', publisher: 'TollBit docs', href: 'https://docs.tollbit.com/docs/platform-architecture', checked: '2026-11-14' },
+ { title: 'Verifying a property', publisher: 'TollBit docs', href: 'https://docs.tollbit.com/docs/verifying-a-property', checked: '2026-11-14' },
+ { title: 'What is Pay Per Crawl?', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/what-is-pay-per-crawl/', checked: '2026-11-15' },
+ { title: 'Pay Per Use: when AI uses your work, you should get paid', publisher: 'Cloudflare blog', href: 'https://blog.cloudflare.com/pay-per-use/', checked: '2026-11-14' },
+ { title: 'Making AI search smarter', publisher: 'Cloudflare blog', href: 'https://blog.cloudflare.com/making-ai-search-smarter/', checked: '2026-11-15' },
+ { title: 'Analyze AI traffic', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/features/analyze-ai-traffic/', checked: '2026-11-15' },
+ { title: 'Set a pay per crawl price', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-site-owner/set-a-pay-per-crawl-price/', checked: '2026-11-15' },
+ { title: 'Enable in account settings', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-site-owner/enable-in-account-settings/', checked: '2026-11-15' },
+ { title: 'AI Crawl Control with WAF', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/configuration/ai-crawl-control-with-waf/', checked: '2026-11-15' },
+ { title: 'Manage payouts', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-site-owner/manage-payouts/', checked: '2026-11-15' },
+ { title: 'Communicating license terms to AI agents', publisher: 'AWS WAF Developer Guide', href: 'https://docs.aws.amazon.com/waf/latest/developerguide/waf-ai-traffic-monetization-license-terms.html', checked: '2026-11-14' },
+ { title: 'Getting started with AI traffic monetization', publisher: 'AWS WAF Developer Guide', href: 'https://docs.aws.amazon.com/waf/latest/developerguide/waf-ai-traffic-monetization-getting-started.html', checked: '2026-11-14' },
+ { title: 'AWS WAF Bot Control rule group', publisher: 'AWS WAF Developer Guide', href: 'https://docs.aws.amazon.com/waf/latest/developerguide/aws-managed-rule-groups-bot.html', checked: '2026-11-14' },
+ { title: 'How to control and monetize AI bot traffic using Fastly and TollBit', publisher: 'Fastly', href: 'https://www.fastly.com/blog/how-to-control-and-monetize-ai-bot-traffic-using-fastly-and-tollbit', checked: '2026-11-14' },
+ { title: 'How Skyfire and Akamai enabled 2.5 million agentic transactions', publisher: 'Akamai', href: 'https://www.akamai.com/blog/security/how-skyfire-akamai-enabled-25-million-agentic-transactions', checked: '2026-11-14' },
+ { title: 'Product', publisher: 'MonetizationOS', href: 'https://monetizationos.com/product', checked: '2026-11-14' },
+ { title: 'MonetizationOS demonstrates machine payments at Stripe Sessions 2026', publisher: 'MonetizationOS blog', href: 'https://monetizationos.com/blog/monetizationos-demonstrates-machine-payments-at-stripe-sessions-2026', checked: '2026-11-14' },
+ { title: 'MonetizationOS documentation', publisher: 'MonetizationOS', href: 'https://docs.monetizationos.com/', checked: '2026-11-14' },
+ { title: 'Control AI crawlers and assistants separately in Vercel Firewall', publisher: 'Vercel changelog', href: 'https://vercel.com/changelog/block-ai-crawlers-and-assistants-independently-with-managed-rules', checked: '2026-11-15' },
+ { title: 'Block AI crawlers and bots', publisher: 'Netlify Docs', href: 'https://docs.netlify.com/build/build-with-ai/block-ai-crawlers/', checked: '2026-11-15' },
+ { title: 'Bot management overview', publisher: 'Google Cloud Armor documentation', href: 'https://docs.cloud.google.com/armor/docs/bot-management', checked: '2026-11-15' },
+ { title: 'Configure bot protection for Web Application Firewall with Azure Front Door', publisher: 'Microsoft Learn', href: 'https://learn.microsoft.com/en-us/azure/web-application-firewall/afds/waf-front-door-policy-configure-bot-protection', checked: '2026-11-15' },
+ { title: 'AWS (S3, CloudFront, ALB)', publisher: 'TollBit docs', href: 'https://docs.tollbit.com/docs/aws-s3-cloudfront-alb', checked: '2026-11-14' },
+ { title: 'Select crawlers to charge', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-site-owner/select-crawlers-to-charge/', checked: '2026-11-15' },
+ { title: 'TollBit homepage', publisher: 'TollBit', href: 'https://tollbit.com/', checked: '2026-11-14' },
+ { title: 'Web Bot Auth', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/', checked: '2026-11-15' },
+ { title: 'Redefine trust with Web Bot Authentication', publisher: 'Akamai', href: 'https://www.akamai.com/blog/security/redefine-trust-web-bot-authentication', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Agent-payment rails',
+ items: [
+ { title: 'KYAPay Token (draft-skyfire-oauth-kyapay-token)', publisher: 'IETF Datatracker', href: 'https://datatracker.ietf.org/doc/draft-skyfire-oauth-kyapay-token/', checked: '2026-11-14' },
+ { title: 'Payments and settlement', publisher: 'Skyfire docs', href: 'https://docs.skyfire.xyz/docs/payments-settlement', checked: '2026-11-14' },
+ { title: 'Service directory (public API)', publisher: 'Skyfire', href: 'https://api.skyfire.xyz/api/v1/directory/services', checked: '2026-11-14' },
+ { title: 'The "Payment" HTTP Authentication Scheme (draft-httpauth-payment)', publisher: 'IETF Datatracker', href: 'https://datatracker.ietf.org/doc/draft-httpauth-payment/', checked: '2026-11-15' },
+ { title: 'x402 overview', publisher: 'Coinbase Developer Platform', href: 'https://docs.cdp.coinbase.com/x402/welcome', checked: '2026-11-14' },
+ { title: 'Deploy at the edge', publisher: 'Supertab Connect docs', href: 'https://connect-docs.supertab.co/guides/deploy-cdn', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Retrieval marketplaces',
+ items: [
+ { title: 'Dappier data_model_id list: publisher search models and prices', publisher: 'Dappier', href: 'https://agents.dappier.com/zcj/cv3gcduzbjkm/guides/publisher-data-models.md', checked: '2026-11-15' },
+ { title: 'Use cases', publisher: 'Cashmere', href: 'https://cashmere.io/use-cases', checked: '2026-11-14' },
+ { title: 'Cashmere.io wants better AI licensing deals for publishers', publisher: 'Publishers Weekly', href: 'https://www.publishersweekly.com/pw/by-topic/digital/content-and-e-books/article/99705-the-stealthy-startup-promising-better-ai-publishing-licensing-deals.html', checked: '2026-11-14' },
+ { title: 'Creating and configuring collections', publisher: 'Cashmere support', href: 'https://cashmere.io/support/creating-and-configuring-collections', checked: '2026-11-14' },
+ { title: 'Full-stack AI distribution', publisher: 'Valyu', href: 'https://www.valyu.ai/rev-share-partner-programme', checked: '2026-11-14' },
+ { title: 'Wiley Health & Life Sciences', publisher: 'Valyu docs', href: 'https://docs.valyu.ai/guides/wiley-hls', checked: '2026-11-14' },
+ { title: 'AskNews partners with top publishers to serve booming news analytics market', publisher: 'AskNews', href: 'https://asknews.app/en/blog-articles/asknews-partners-with-top-publishers-to-serve-booming-news-analytics-market', checked: '2026-11-14' },
+ { title: 'Publishers quietly cut \'six-figure\' deals via Snowflake\'s AI licensing platform', publisher: 'Digiday', href: 'https://digiday.com/media/publishers-quietly-cut-six-figure-deals-via-snowflakes-ai-licensing-platform/', checked: '2026-11-14' },
+ { title: 'Cortex Knowledge Extensions', publisher: 'Snowflake documentation', href: 'https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-knowledge-extensions/cke-overview', checked: '2026-11-15' },
+ { title: 'Dow Jones Factiva surpasses 8,000 licensed sources for GenAI use', publisher: 'Dow Jones', href: 'https://www.dowjones.com/press-room/dow-jones-factiva-surpasses-8000-licensed-sources-for-genai-use/', checked: '2026-11-14' },
+ { title: 'Dow Jones Investor Briefing, March 16, 2026 (News Corp Form 8-K, Exhibit 99.1)', publisher: 'U.S. SEC, EDGAR', href: 'https://www.sec.gov/Archives/edgar/data/1564708/000156470826000057/dowjones2026investorbrie.htm', checked: '2026-11-14' },
+ { title: 'Discover services (Bazaar)', publisher: 'Coinbase Developer Platform', href: 'https://docs.cdp.coinbase.com/x402/bazaar', checked: '2026-11-15' },
+ { title: 'For publishers', publisher: 'xpay documentation', href: 'https://xpay.sh/docs/publishers', checked: '2026-11-15' },
+ { title: 'Model Context Protocol specification, revision 2026-07-28', publisher: 'Model Context Protocol', href: 'https://modelcontextprotocol.io/specification/2026-07-28', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Answer engines',
+ items: [
+ { title: 'Gist Ads discontinued', publisher: 'ProRata.ai', href: 'https://gist.ai/gist-ads-discontinued', checked: '2026-11-14' },
+ { title: 'ProRata Online Master Services Agreement (MSA)', publisher: 'ProRata.ai', href: 'https://gist.ai/support/ga/wpnewpartner', checked: '2026-11-15' },
+ { title: 'Gist Answers for WordPress: user guide', publisher: 'ProRata.ai', href: 'https://gist.ai/support/ga/wpuserguide', checked: '2026-11-14' },
+ { title: 'How Perplexity\'s new revenue model works, according to its head of publisher partnerships', publisher: 'Digiday', href: 'https://digiday.com/media/how-perplexity-new-revenue-model-works-according-to-its-head-of-publisher-partnerships/', checked: '2026-11-14' },
+ { title: 'Introducing Comet Plus', publisher: 'Perplexity', href: 'https://www.perplexity.ai/hub/blog/introducing-comet-plus', checked: '2026-11-15' },
+ { title: 'Perplexity Crawlers', publisher: 'Perplexity docs', href: 'https://docs.perplexity.ai/docs/resources/perplexity-crawlers', checked: '2026-11-15' },
+ { title: 'Index by Parallel', publisher: 'Parallel', href: 'https://index.parallel.ai/', checked: '2026-11-14' },
+ { title: 'Parallel Web Systems bots', publisher: 'Parallel', href: 'https://parallel.ai/parallel-web-systems-bots', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Training data',
+ items: [
+ { title: 'AI rights and the future of publishing with Created by Humans founder Trip Adler', publisher: 'Written Word Media', href: 'https://www.writtenwordmedia.com/ai-rights-and-the-future-of-publishing-with-created-by-humans-founder-trip-adler/', checked: '2026-11-14' },
+ { title: 'Author Overview', publisher: 'Created by Humans help center', href: 'https://support.createdbyhumans.ai/hc/en-us/articles/30891024362523-Author-Overview', checked: '2026-11-14' },
+ { title: 'Video', publisher: 'Protege', href: 'https://withprotege.ai/data-provider/video', checked: '2026-11-14' },
+ { title: 'How AI content licensing deals work: structures, terms, and what gets negotiated', publisher: 'Troveo', href: 'https://www.troveo.ai/resources/ai-data-licensing-deals', checked: '2026-11-14' },
+ { title: 'Turn your video library into recurring revenue', publisher: 'Troveo', href: 'https://www.troveo.ai/content-owners', checked: '2026-11-14' },
+ { title: 'llms.txt', publisher: 'Wirestock', href: 'https://wirestock.io/llms.txt', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Court settlements',
+ items: [
+ { title: 'Order granting final approval of class action settlement (Dkt. 680), Bartz v. Anthropic', publisher: 'U.S. District Court, Northern District of California', href: 'https://assets-us-01.kc-usercontent.com:443/1eeb16db-4934-006e-40a6-38fa91285ebb/36cce252-a32c-4cbb-a624-31dd8ac9574c/2026-07-20%20Order%20Granting%20Final%20_dckt%20680_0_.pdf', checked: '2026-11-15' },
+ { title: 'Bartz v. Anthropic settlement website', publisher: 'Settlement administrator', href: 'https://www.anthropiccopyrightsettlement.com/', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Changed, closed or announced',
+ items: [
+ { title: 'AI visibility measurement for publishers and brands', publisher: 'ScalePost', href: 'https://www.scalepost.ai/', checked: '2026-11-14' },
+ { title: 'Human Native is joining Cloudflare', publisher: 'Cloudflare blog', href: 'https://blog.cloudflare.com/human-native-joins-cloudflare/', checked: '2026-11-14' },
+ { title: 'Human Native is joining Cloudflare', publisher: 'Human Native', href: 'https://www.humannative.ai/', checked: '2026-11-14' },
+ { title: 'Human Native Ltd (15609120): persons with significant control', publisher: 'Companies House', href: 'https://find-and-update.company-information.service.gov.uk/company/15609120/persons-with-significant-control', checked: '2026-11-14' },
+ { title: 'Next Net home page', publisher: 'Next Net', href: 'https://www.nextnet.ai', checked: '2026-11-15' },
+ { title: 'Amazon may launch a marketplace where media sites can sell their content to AI companies', publisher: 'TechCrunch', href: 'https://techcrunch.com/2026/02/10/amazon-may-launch-a-marketplace-where-media-sites-can-sell-their-content-to-ai-companies/', checked: '2026-11-13' },
+ ],
+ },
+ {
+ name: 'Training and content signals',
+ items: [
+ { title: 'HTTP Message Signatures for automated traffic Architecture (draft-meunier-web-bot-auth-architecture)', publisher: 'IETF, individual Internet-Draft', href: 'https://datatracker.ietf.org/doc/draft-meunier-web-bot-auth-architecture/', checked: '2026-11-14' },
+ { title: 'Giving users choice with Cloudflare\'s new Content Signals Policy', publisher: 'Cloudflare blog', href: 'https://blog.cloudflare.com/content-signals-policy/', checked: '2026-11-14' },
+ { title: 'robots.txt controls', publisher: 'Anthropic', where: 'Anthropic help center, article 8896518 (no link)', checked: '2026-11-15' },
+ { title: 'Helping websites express AI training preferences', publisher: 'OpenAI', href: 'https://openai.com/index/helping-websites-express-ai-training-preferences/', checked: '2026-11-14' },
+ { title: 'Google\'s common crawlers', publisher: 'Google for Developers', href: 'https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers', checked: '2026-11-15' },
+ { title: 'Your content, your choice: clearer preferences for training and grounding', publisher: 'Microsoft, Bing blog', href: 'https://blogs.bing.com/search/2026/10/your-content-your-choice-clearer-preferences-for-training-and-grounding/', checked: '2026-11-15' },
+ ],
+ },
+];
+const FLAT: { href?: string }[] = SOURCES.flatMap((g) => g.items);
+/** Entry N's URL, for an inline link to the same source. */
+const src = (n: number, anchor = '') => `${FLAT[n - 1].href}${anchor}`;
+
+// What FORA takes: FORA's cells of the GlanceCard, under the shared row labels.
+const FORA_GLANCE: Record = {
+ payer: FORA_CELLS.payer,
+ fees: FORA_CELLS.fees,
+ reporting: `Each sale, and daily income as a CSV, in your operator's publisher console. No bot-traffic report ${cite(1)}.`,
+ contract: `An agreement with your Exchange operator. With each purchase the buyer signs an acceptance of your terms, which the console can check ${cite(1, 2)}.`,
+ status: `${statusTag('live')} ${SEE_ABOUT}`,
+ dns: `No record to add, and nothing delegated ${cite(1)}.`,
+ cdn: FORA_CELLS.cdn,
+ firewall: `Your rules run first. They must let signed requests and your FORA file through ${cite(1, 3)}.`,
+ site: `One file, fora.json, and a sitemap the operator imports your pages from. No keys to make, no catalog to push ${cite(1)}.`,
+ search: `Google's, Bing's and Apple's crawlers pass. The rest is your choice: see ${a('#together', 'Search traffic')} ${cite(2, 3)}.`,
+ upkeep: `Keep your terms current with your Exchange. A change to your FORA file needs no redeploy ${cite(1)}.`,
+ leaving: FORA_CELLS.leaving,
+};
+const GLANCE_TITLES = ['FORA for your revenue team', 'What FORA takes on your stack'];
+const GLANCE = GLANCE_GROUPS.map((g, i) => ({
+ title: GLANCE_TITLES[i],
+ group: g.name,
+ rows: g.rows.map((r) => ({ label: r.label, cell: FORA_GLANCE[r.key] })),
+}));
+
+const SHORT_ANSWER = [
+ { title: 'Seven kinds of channel sell future use, and court settlements pay for the past.', text: 'Some charge bots at your CDN, and some hold a copy of your content and sell search over it. Others are the AI company itself, paying a share, a fee or by contribution.' },
+ { title: 'They differ on who sets the price.', text: 'At a bot paywall you set it per page. In an answer engine\'s pool or Google\'s pilots, the buyer decides your share. In Microsoft\'s marketplace the terms aren\'t public.' },
+ { title: 'FORA lets anyone run a channel you price yourself.', text: 'It is an open protocol and free, open-source software, so any company can run a FORA marketplace, an Exchange. You sell through one, several or your own, and set terms and a price for each use of your pages. The operator bills the buyer and pays you. It runs beside your other deals.' },
+];
+
+const KEY_FACTS = [
+ { value: '400+', text: `publications Google pays in its News AI pilot ${cite(9)}` },
+ { value: '$203.0 million', text: `in aggregate AI licensing deals, in Reddit's S-1 filing ${cite(10)}` },
+ { value: 'NOK 45 million', text: `a year to Kopinor from the National Library of Norway ${cite(20)}` },
+ { value: 'Nearly 20%', text: `of nearly 7,000 TollBit sites have earned, by TollBit's CEO in April 2026, unaudited ${cite(25)}` },
+];
+
+// The map: FORA's row first, then one group per category of channel.
+const MAP_COLUMNS = ['Player', 'What\'s sold', 'Who pays today', 'Fee, payout and reporting', 'Who sets the price', 'Unit', 'What your engineers change', 'How FORA works with it'];
+const MAP_FORA = {
+ player: 'FORA',
+ cells: [
+ `A license to each page or file, under offers your Exchange signs ${cite(4)}`,
+ '—',
+ `FORA itself is free. Each sale in your operator's console ${cite(1)}. The console's fee and payout: see ${ABOUT}`,
+ `You, per term, by use, country and buyer type ${cite(5)}`,
+ `Free, flat, or per unit you name: text tokens (about ¾ of a word), pages, seconds or your own ${cite(4, 5)}`,
+ `An edge function and one file; Cloudflare, Fastly or CloudFront only ${cite(1, 2)}. See ${a('#fora', 'What FORA takes')}`,
+ '—',
+ ],
+};
+const MAP = [
+ {
+ name: '1. Bot paywalls at your CDN',
+ rows: [
+ { player: 'TollBit', cells: [
+ `A license to one page: summary, full display or custom; no training ${cite(26, 27)}`,
+ `Few buyers named, none confirmed as paying ${cite(28, 29)}. TNL Mediagene reports "initial revenue from AI buyers"; TollBit's CEO says nearly 20% of nearly 7,000 sites have earned (April 2026, unaudited) ${cite(25, 30)}`,
+ `The buyer pays a fee on top of your rate; its size isn't published ${cite(27)}. Shows bot traffic ${cite(31)}`,
+ 'You',
+ `Per page, rate set per 1,000 ${cite(27)}`,
+ `DNS records, a CDN rule and firewall allow rules; all your logs shared; the bot list kept by hand ${cite(32, 33)}`,
+ `Runs beside FORA's edge in a CDN rule order you write ${cite(32)}. Its rates shown to FORA agents: ${statusTag('design')}`,
+ ] },
+ { player: 'Cloudflare', cells: [
+ `Pay Per Crawl ${statusTag('closed-beta')}: each successful crawl ${cite(34)}. Pay Per Use ${statusTag('beta')}: a use the buyer defines ${cite(35)}`,
+ `Pay Per Use: Ceramic.ai and You.com in pilots ${cite(35, 36)}. No Pay Per Crawl buyer named; no amounts published`,
+ `Fee not published. Shows bot traffic ${cite(37)}`,
+ `Pay Per Crawl: you ${cite(38)}. Pay Per Use: the buyer ${cite(35)}`,
+ 'Per crawl; per reported use',
+ `Cloudflare's nameservers or Cloudflare-managed DNS ${cite(39)}, beta admission ${cite(34)}, security rules reconciled ${cite(40)}, a new Stripe Connect account ${cite(41)}`,
+ `FORA's edge runs as a Worker after Cloudflare's rules ${cite(1, 3)}`,
+ ] },
+ { player: 'AWS WAF', cells: [
+ `Access to requests a rule matches; no license ${cite(42)}`,
+ 'No buyer or publisher named',
+ `To a USDC wallet or a Stripe account; AWS lists each settlement ${cite(43)}`,
+ 'You',
+ `Per request, in USDC ${cite(43)}`,
+ `CloudFront, firewall rules per price, a wallet or Stripe account, your own log pipeline ${cite(43, 44)}`,
+ `FORA's edge runs on CloudFront after AWS WAF ${cite(1, 3)}`,
+ ] },
+ { player: 'Fastly, Akamai', cells: [
+ `Bot detection; the sale goes to TollBit, Skyfire or Supertab ${cite(45)}`,
+ `Through partners. Akamai reports 2.5 million Skyfire transactions by one unnamed data provider ${cite(46)}`,
+ 'The partner\'s',
+ 'The partner',
+ 'The partner\'s',
+ 'Bot management plus the partner\'s rule',
+ `FORA's edge runs on Fastly, not on Akamai ${cite(1, 2)}`,
+ ] },
+ { player: 'MonetizationOS', cells: [
+ `Access plans for readers and bots ${cite(47)}`,
+ 'No public case of a bot paying',
+ '—',
+ 'You',
+ 'A plan or meter',
+ 'A proxy on your CDN',
+ 'Runs in series with FORA\'s edge',
+ ] },
+ ],
+ },
+ {
+ name: '2. Agent-payment rails',
+ rows: [
+ { player: 'Skyfire (KYAPay)', cells: [
+ `Signed identity and payment passes, charged after delivery ${cite(59, 60)}`,
+ `No AI company named. 81 services listed, one news site at $0.01 a use ${cite(61)}`,
+ `Settles in up to about 51 hours ${cite(60)}`,
+ 'The seller',
+ 'The seller\'s price per service',
+ 'Register a seller service; check and charge passes',
+ 'Could fund an agent\'s account at a FORA Exchange; FORA ships no adapter',
+ ] },
+ { player: 'x402, MPP', cells: [
+ `Payment for one request ${cite(62, 63)}`,
+ 'No AI company named as a buyer of publisher content',
+ 'Settles per request',
+ 'The seller',
+ 'Per request',
+ 'A payment handler or gateway at your edge',
+ 'Could carry the payment for a FORA sale; FORA ships no adapter',
+ ] },
+ { player: 'Supertab Connect', cells: [
+ 'RSL licenses through a license server',
+ 'No licensee named',
+ '—',
+ 'You',
+ 'Per crawl, call, document, text token and more',
+ `A CDN SDK or WordPress plugin, and a License: line ${cite(64)}`,
+ 'Its RSL file can sit beside FORA\'s terms',
+ ] },
+ ],
+ },
+ {
+ name: '3. Retrieval marketplaces',
+ rows: [
+ { player: 'Dappier', cells: [
+ `Search over your corpus as a "data model" ${cite(65)}`,
+ 'Agents prepay credit through ZeroClick. No AI company named',
+ '—',
+ 'You',
+ `Per query, $0.003 to $0.02 ${cite(65)}`,
+ 'An RSS feed or a script tag',
+ 'Runs beside FORA, from its own copy of your content',
+ ] },
+ { player: 'Cashmere', cells: [
+ 'Search results over your catalog, which it hosts',
+ `Perplexity, named by Cashmere and press ${cite(66, 67)}. No payment confirmed by a buyer or publisher`,
+ '—',
+ `You, per collection ${cite(68)}`,
+ 'Per million text tokens',
+ 'Upload titles by API, S3 or SFTP',
+ 'Runs beside FORA, from its own copy of your content',
+ ] },
+ { player: 'Valyu', cells: [
+ 'Cited passages from your archive',
+ 'Buyers prepay',
+ `Payouts promised "monthly above a threshold"; none shown ${cite(69)}`,
+ `Valyu: Wiley's health and life sciences journals at $12 per 1,000 results ${cite(70)}`,
+ 'Per result',
+ 'Hand over files',
+ 'Runs beside FORA, from its own copy of your archive',
+ ] },
+ { player: 'AskNews', cells: [
+ 'Search over "synthetic" versions of your articles',
+ 'Buyers on published plans. No publisher confirms a payout',
+ `Said in 2025 that 50% of its revenue goes to publishers ${cite(71)}`,
+ 'AskNews',
+ 'Credits and text tokens',
+ 'It crawls you or reads your feed; its crawler\'s user agent and IP ranges aren\'t published',
+ 'Runs beside FORA, from its own copy of your content',
+ ] },
+ { player: 'Snowflake (CKE)', cells: [
+ 'A search service over your text, inside Snowflake',
+ `Buyers pay through Snowflake, or on terms struck with you directly. "six-figure deals" with financial institutions (Snowflake, via Digiday) ${cite(72)}`,
+ `By subscription; no usage-based billing ${cite(73)}`,
+ 'You',
+ 'Subscription',
+ 'Build the service in a Snowflake account',
+ 'Runs beside FORA: CKE sells inside Snowflake, FORA at your site',
+ ] },
+ { player: 'Dow Jones Factiva', cells: [
+ `Your articles, relicensed to companies for AI use ${cite(74)}`,
+ `"~20 GenAI deals" with companies, none named (Dow Jones) ${cite(75)}`,
+ 'Royalties to publishers by agreement',
+ 'Dow Jones',
+ 'A subscription per project, metered in text tokens',
+ 'Sign an agreement',
+ 'Runs beside FORA, from its own copy of your articles',
+ ] },
+ { player: 'Newstex, xpay', cells: [
+ `Newstex: "one full licensed story body" per call ${cite(76)}. xpay: search over your feed ${cite(77)}`,
+ `Newstex's story route: 3 calls by 1 payer in 30 days, by x402 Bazaar's count ${cite(76)}. xpay names no buyer`,
+ `xpay keeps 5% ${cite(77)}`,
+ 'Newstex; at xpay, you',
+ `Per call: Newstex $0.01 a search, $0.10 a story; xpay $0.01 to $1.00 a query ${cite(76, 77)}`,
+ `xpay: paste an RSS feed. "Your site, CDN, and DNS stay completely untouched", so nothing is enforced at your site ${cite(77)}`,
+ 'Runs beside FORA, from its own copy of your feed',
+ ] },
+ ],
+ },
+ {
+ name: '4. Answer engines that pay a share',
+ rows: [
+ { player: 'ProRata, Gist', cells: [
+ 'Use of your content in Gist answers',
+ `ProRata itself; no payout published. Its Gist Ads network ended 2026-09-01; Gist Answers still runs ${cite(79)}`,
+ `Monthly above $1,000, with monthly statements per article and an audit right ${cite(80)}`,
+ 'ProRata',
+ `A share of 50% of net revenue, split per answer by attribution ${cite(80)}`,
+ `A script tag or WordPress plugin; your feed open to its crawler, whose user agent and IP ranges aren't published ${cite(81)}`,
+ `Runs beside FORA on one site; its MSA is non-exclusive ${cite(80)}`,
+ ] },
+ { player: 'Perplexity', cells: [
+ 'Use in Perplexity\'s products',
+ `Perplexity itself. Of Comet Plus, its head of publisher partnerships said "Real cash payments starting immediately" (Digiday, 2025) ${cite(82)}. Comet Plus is on none of Perplexity's pricing pages`,
+ '—',
+ 'Perplexity',
+ `Comet Plus: a subscription pool by visits, citations and agent actions ${cite(83)}`,
+ `A contract; its two crawlers allowed by user agent and published IP ranges. Nothing metered at your site ${cite(84)}`,
+ `Runs beside FORA on one site; you choose what each of its crawlers gets at FORA's edge ${cite(3)}`,
+ ] },
+ { player: 'Index by Parallel', cells: [
+ 'Use in Parallel\'s agents\' work',
+ `Its home page marks monetization "Coming Soon" ${cite(85)}`,
+ 'Terms private',
+ 'Parallel',
+ 'Each source\'s estimated contribution to the answer',
+ 'A partnership agreement',
+ `FORA's edge refuses its crawler on licensed paths unless you allow it ${cite(3)}`,
+ ] },
+ ],
+ },
+ {
+ name: '5. AI companies buying directly',
+ rows: [
+ { player: 'Google', cells: [
+ `News AI pilot: "enhanced content" for AI features ${cite(9)}. AI contribution pilot: content that "contributes significantly" to an AI answer ${cite(11)}. In the EU, previews (ENP) ${cite(12)}`,
+ `Google itself: "more than 400 publications" in the News AI pilot (Google); about 100 publishers in the contribution pilot (The Information, via TNW) ${cite(9, 13)}`,
+ `Contribution pilot: Google decides the amount and shows one monthly number in Search Console ${cite(11)}`,
+ 'Google',
+ 'Not public',
+ `A verified Search Console property, the program terms, payment details; Googlebot kept unblocked and unmetered ${cite(12)}`,
+ `FORA's edge passes Googlebot free; Google's AI uses stay under Google's own controls ${cite(3)}`,
+ ] },
+ { player: 'Microsoft PCM', cells: [
+ 'Grounding and display in Copilot and partners\' products',
+ `Copilot; Microsoft is "beginning to onboard" Yahoo. No payment confirmed by a primary source ${cite(14)}`,
+ 'Pricing, unit and fee not public',
+ 'Not public; pilot contracts negotiated one by one',
+ 'Not public',
+ 'A contract; nothing documented on your site',
+ 'Runs beside FORA on one site, if your PCM contract allows it',
+ ] },
+ { player: 'Direct deals', cells: [
+ 'Display, archive access, often training',
+ `Named buyers: OpenAI, Google, Meta, Amazon, Microsoft, Mistral, Anthropic ${cite(15, 16)}. Reddit filed $203.0 million in aggregate deals ${cite(10)}`,
+ 'Private contracts',
+ 'Negotiated',
+ 'Mostly a flat annual fee',
+ 'A contract; a feed or a crawl',
+ `The buyer can buy through FORA under a deal term ${cite(5)}`,
+ ] },
+ ],
+ },
+ {
+ name: '6. Training data',
+ rows: [
+ { player: 'Created by Humans', cells: [
+ 'AI rights to books, bundled per deal',
+ 'No deal confirmed',
+ `Its CEO: "we take a 20 % fee" ${cite(87)}`,
+ `Negotiated by CbH; you can opt out within 7 days ${cite(88)}`,
+ 'Per deal',
+ 'Claim your books by ISBN',
+ 'Runs beside FORA, from its own copy of your books',
+ ] },
+ { player: 'Defined.ai, Protege, Wirestock, Troveo', cells: [
+ 'Datasets for training',
+ `By their own figures: Protege "Tens of Millions", Wirestock "over $15 million" paid; Troveo gives two different totals ${cite(89, 90, 91, 92)}`,
+ '—',
+ 'Negotiated',
+ 'Per deal',
+ 'Hand over your archive',
+ `Runs beside FORA, from its own copy. Where a vendor holds an exclusive training grant, you can show a FORA training term only to that buyer ${cite(5)}`,
+ ] },
+ ],
+ },
+ {
+ name: '7. Collectives and rights agencies',
+ rows: [
+ { player: 'ILC, CLA, DPCMO, Kopinor', cells: [
+ 'A collective license across members',
+ `ILC: Yahoo Scout, its first licensee ${cite(21)}. Kopinor: NOK 45 million a year from the National Library of Norway ${cite(20)}`,
+ 'Split by each scheme\'s rule',
+ 'The collective',
+ 'A pool',
+ 'Join and accept the terms',
+ `A pool on FORA: see ${a('/resources/transparent-collective/', 'A fair licensing collective')}`,
+ ] },
+ { player: 'CCC', cells: [
+ `Rights only, no copy: annual licenses (a pool) and AI Summarization, one summary per order ${cite(22, 23)}`,
+ `Buyers pay CCC; no AI payment is public. One of nine titles probed sold AI Summarization, at 19.10 USD a summary ${cite(24)}`,
+ '—',
+ 'CCC for annual licenses; you, per order',
+ 'Per organization a year; per summary',
+ 'An agreement, a title list and a fee table in CCC\'s portal; nothing at your site',
+ 'A CCC order maps to a FORA term; CCC documents no buyer API',
+ ] },
+ ],
+ },
+ {
+ name: '8. Court settlements (past use)',
+ rows: [
+ { player: 'Bartz v. Anthropic', cells: [
+ `Release of claims for past copying of 440,490 claimed books ${cite(93)}`,
+ `Anthropic, into a $1.5 billion fund the court approved ${cite(93)}`,
+ `About $3,000 a work, by the court's estimate; first payments "on or before November 15, 2026" ${cite(93, 94)}`,
+ 'The court',
+ 'Per work',
+ 'A claim through the administrator',
+ 'Neither: a one-time remedy, not a license',
+ ] },
+ ],
+ },
+ {
+ name: 'Changed or closed',
+ rows: [
+ { player: 'ScalePost', cells: [
+ `Was a licensing marketplace; now measures AI visibility ${cite(95)}`,
+ 'No content sale shown',
+ '—', '—', '—',
+ 'CDN logs',
+ 'Reads logs; runs beside FORA\'s edge',
+ ] },
+ { player: 'Human Native', cells: [
+ `Was a training-data marketplace ${cite(96)}`,
+ `Closed: its site is now one letter, "Human Native is joining Cloudflare" ${cite(97)}. Cloudflare holds 75% or more ${cite(98)}`,
+ '—', '—', '—', '—', '—',
+ ] },
+ ],
+ },
+];
+
+const RELATIONS = [
+ { title: 'Sell the same page.', text: 'Bot paywalls, retrieval marketplaces, AI companies buying directly, and Supertab Connect\'s license server each sell what a FORA Exchange sells. Each sale goes to one of them, and they run side by side on one site.' },
+ { title: 'Work alongside FORA.', text: 'The payment rails, at settlement; answer engines; and training-data deals.' },
+ { title: 'Could run on FORA.', text: 'A retrieval marketplace, a collective or a rights agency can run a FORA Exchange and Broker over its own catalog, keep its search, and reach every FORA agent.' },
+];
+
+const ENGINEERS_FULL = [
+ { title: 'TollBit and Cloudflare:', text: `the setup is on their deep pages, ${a('/resources/content-marketplaces/tollbit/', 'TollBit')} and ${a('/resources/content-marketplaces/cloudflare/', 'Cloudflare')}.` },
+ { title: 'AWS WAF:', text: 'the site on CloudFront. A global web ACL with Bot Control, its blocking rules set to Count so bots reach a price. One Monetize rule per price, on AWS\'s bot labels. A USDC wallet or Stripe account, and your own log pipeline.' },
+ { title: 'Fastly, Akamai:', text: 'for TollBit, a backend and VCL snippet (Fastly) or a Conditional Origin and Cloudlet (Akamai).' },
+ { title: 'Google:', text: 'for ENP, a DNS TXT record to verify the property. No CDN rule, feed or log export.' },
+ { title: 'Microsoft PCM:', text: 'no ingestion format, DNS or CDN change, bot rule or log feed is documented.' },
+ { title: 'CCC:', text: 'a rightsholder agreement. No DNS, CDN or log change, and nothing enforced at your site.' },
+ { title: 'FORA:', text: `see ${a('#together', 'What changes on your CDN')}.` },
+];
+
+// hub-4: how money reaches a publisher, one tile per channel and FORA's.
+const MONEY_TILES = [
+ { title: '1 · Bot paywalls', flow: ['AI bot', 'TollBit, Cloudflare', 'You'], lines: ['Pays per page or crawl, at your CDN', 'Price: yours. TollBit adds a buyer fee', 'whose size it doesn\'t publish'] },
+ { title: '2 · Payment rails', flow: ['Agent', 'x402, MPP', 'You'], lines: ['One payment for one request', 'No license travels with it', 'Skyfire: charged after delivery'] },
+ { title: '3 · Retrieval marketplaces', flow: ['Buyer', 'Marketplace, your copy', 'You'], lines: ['Pays per query or result', 'Price: yours at Dappier and Cashmere,', 'the marketplace\'s at Valyu and AskNews'] },
+ { title: '4 · Answer engines', flow: ['Their revenue', 'ProRata, Perplexity', 'You'], lines: ['Pays a share, from a pool', 'ProRata: 50% of net revenue', 'Split by the use they count'] },
+ { title: '5 · Buying directly', flow: ['Google, Microsoft, AI companies', 'You'], lines: ['Pays from its own programs or deals', 'Google decides the amount', 'Direct deals: mostly a flat annual fee'] },
+ { title: '6 · Training data', flow: ['AI lab', 'Dataset vendor', 'You'], lines: ['Pays per deal, for bulk copies', 'Read whether the grant is exclusive', 'Created by Humans: a 20% fee'] },
+ { title: '7 · Collectives', flow: ['Licensee', 'Collective', 'Members'], lines: ['One license across many members', 'Split by the scheme\'s own rule', 'Kopinor: NOK 45 million a year'] },
+ { title: '8 · Court settlements', flow: ['Anthropic', '$1.5 billion fund', 'Claimants'], lines: ['Paid once, for past copying', 'About $3,000 a work, court\'s estimate', 'No future price, no license'] },
+ { title: 'FORA', flow: ['Agent', 'Exchange operator', 'You'], lines: ['Charges the agent\'s own account', 'The operator bills and pays you'], fora: true },
+];
+
+const CAUTIONS = [
+ { title: 'TollBit\'s fetcher must get through.', text: `If its requests "are blocked, challenged, or rate-limited, your Agent Site will not work correctly" (${a(src(33), 'Verifying a property')}).` },
+ { title: 'Bot pages can reach readers.', text: `On CloudFront, steps done out of order mean "Agent Site responses can be cached and then served to human visitors" (${a(src(54), 'CloudFront')}).` },
+ { title: 'Your firewall decides first.', text: `At Cloudflare, "WAF custom rules are enforced before pay per crawl", so a crawler one of them blocks is never offered a price (${a(src(40), 'WAF')}).` },
+ { title: 'Search can suffer.', text: `Charging a search crawler "may negatively impact your site's SEO performance" (${a(src(55), 'Select crawlers')}).` },
+];
+
+// The seven sections after bot paywalls: a heading and HTML paragraphs.
+const KINDS = [
+ {
+ title: 'Payment rails: one payment per request',
+ paras: [
+ `x402 and MPP carry a payment for one request. Skyfire's passes are charged after delivery, and settlement takes up to about 51 hours (${a(src(60), 'Skyfire')}). No rail carries a license. Supertab Connect adds an RSL license server and names no licensee.`,
+ ],
+ },
+ {
+ title: 'Retrieval marketplaces: they hold a copy and sell search over it',
+ paras: [
+ `You hand over your archive or feed, and the marketplace sells search results. At Dappier and Cashmere you set the price; at Valyu and AskNews the marketplace does and pays you a share. Snowflake's Cortex Knowledge Extensions sell access by subscription: "Usage-based billing with CKEs isn't supported" (${a(src(73), 'Snowflake')}). Most reach agents over MCP, which carries no price or license ${cite(78)}. Newstex and xpay charge per call over x402.`,
+ ],
+ },
+ {
+ title: 'Answer engines: the buyer measures and pays a share',
+ paras: [
+ `ProRata pays a pool of 50% of its net revenue, split per answer by how much came from you (${a(src(80), 'MSA')}). Perplexity's Comet Plus pools subscription revenue by "human visits, search citations, and agent actions" (${a(src(83), 'Perplexity')}).`,
+ `Deep pages: ${a('/resources/content-marketplaces/prorata-gist/', 'ProRata and Gist')}, ${a('/resources/content-marketplaces/perplexity/', 'Perplexity')}.`,
+ ],
+ },
+ {
+ title: 'AI companies buying directly',
+ paras: [
+ `In October 2026, Google said its News AI pilot pays "more than 400 publications worldwide" for "enhanced content" (${a(src(9), 'Google')}). Its AI contribution pilot pays when content "contributes significantly" to an answer in Gemini, AI Overviews and AI Mode, by Google's help text as Search Engine Roundtable published it ${cite(11)}. Google decides the amount and shows one monthly number in Search Console. Microsoft says PCM publishers "will be paid on delivered value", with pricing, unit and fee not public ${cite(14)}. Direct deals are private contracts, and some end a lawsuit: Folha's deal with OpenAI, signed with UOL in May 2026, ended the suit Folha filed in 2025 ${cite(17, 18)}.`,
+ `Deep page: ${a('/resources/content-marketplaces/microsoft-pcm/', 'Microsoft PCM')}.`,
+ ],
+ },
+ {
+ title: 'Training data: bulk copies under contract',
+ paras: [
+ `Defined.ai, Protege, Wirestock and Troveo package archives for model training, deal by deal, and Created by Humans does the same for books. Exclusivity is the term to read: Troveo says "around 95 percent" of its rights holders license exclusively (${a(src(90), 'Troveo')}).`,
+ ],
+ },
+ {
+ title: 'Collectives and rights agencies: one license, many works',
+ paras: [
+ `A collective licenses many members' content at once and splits the money by its own rule. ${a('/resources/transparent-collective/', 'A fair licensing collective')} compares eight schemes. CCC sells rights only: "This is a rights-only license and does not provide access to or authorize scraping of content" (${a(src(22), 'CCC')}). Its AI Summarization sells one summary per order, at the rightsholder's price.`,
+ ],
+ },
+ {
+ title: 'Court settlements: paid once, for the past',
+ paras: [
+ `In Bartz v. Anthropic, the court approved a $1.5 billion fund for 440,490 claimed books on July 20, 2026. Its "estimated per-work payment" is "approximately $3,000" (${a(src(93), 'final approval order')}). It sets no price for future use and grants no license.`,
+ ],
+ },
+];
+
+const AHEAD = [
+ { title: 'The buyer comes with the contract.', text: 'Google buys in its pilots and Copilot in Microsoft\'s marketplace; at ProRata and Perplexity, the channel itself is the buyer. On FORA, any agent can buy under your terms.' },
+ { title: 'One integration reaches many sites.', text: `A TollBit buyer uses one key, one card and one search across the network. TollBit's homepage says "over 10,000 sites", up from the "nearly 7,000" its CEO cited in April 2026 (${a(src(56), 'TollBit')}, vendor's figures). A FORA agent opens an account at each Exchange it buys from (${a(src(4), 'What is FORA?')}).` },
+ { title: 'Blocking bots on sites FORA isn\'t installed on.', text: `Cloudflare can refuse a crawler on any site it fronts, and says "More than 20% of the web sits behind Cloudflare’s network" (${a(src(36), 'Cloudflare')}). FORA's edge function refuses unlicensed AI bots on sites that install it, and nowhere else.` },
+ { title: 'Less to install.', text: `Google, CCC, Microsoft and Perplexity work through a contract, a portal or Search Console, with no paywall on your CDN. Google and Perplexity need their crawlers left unblocked. TollBit changes nothing on your origin or CMS. FORA needs its edge function on your CDN and its file on your site (see ${a('#fora', 'What FORA takes')}).` },
+ { title: 'Paying by how much your content shaped the answer.', text: `Google's contribution pilot pays when content "contributes significantly"; ProRata scores each source's share of an answer; Parallel says it pays by each source's estimated contribution ${cite(11, 80, 85)}. FORA cannot: the charge is fixed at the sale, and "a usage report never re-prices a purchase" (${a(src(5, '#metering-modes'), 'Licensing terms')}).` },
+ { title: 'Seeing which bots visit before you sell.', text: `TollBit and Cloudflare show which bots fetch what ${cite(31, 37)}. FORA Server records transactions and makes no bot-traffic report. It's open source, so an operator can add a log of what agents search for and what its Exchange offers them.` },
+ { title: 'A warranty in the license.', text: `TollBit's ${a(src(26), 'standard license')} has you warrant "all rights necessary to provide the Site Content" and indemnify the buyer. FORA cannot state either as a term. A term's obligations are all the buyer's, so a warranty fits only in a license document the term points to (${a(src(5, '#obligations'), 'Licensing terms')}).` },
+ { title: 'Payment and bot identity come from other standards.', text: `x402 and MPP settle per request, and Web Bot Auth was first drafted at Cloudflare ${cite(101)}. FORA defines no payment rail, by design, and its agents sign their requests with Web Bot Auth.` },
+];
+
+// The eight questions: "Others:" and "FORA:" on separate lines.
+const qa = (others: string, fora: string) => `Others: ${others}FORA: ${fora}`;
+const QUESTIONS = [
+ { title: 'How do you say what\'s for sale?', text: qa(
+ `most channels hold your terms in a dashboard or a contract. Supertab and ILC use RSL, and AWS points to an RSL file ${cite(21, 42, 64)}. Cloudflare's Content Signals and the __usage_ai-training group in robots.txt state a preference and no price ${cite(102)}. Anthropic, OpenAI, Google and Microsoft committed to honor that group ${cite(103, 104, 105, 106)}.`,
+ `your FORA file names the Exchanges that sell your content, and each holds your terms per page. FORA's ${a('/resources/ai-crawlers/', 'rules generator')} writes the training group. The ${a('/resources/standards-map/', 'standards map')} compares them all.`,
+ ) },
+ { title: 'How does a buyer find your content?', text: qa(
+ `each channel runs its own index under its own rules: TollBit's search, Cloudflare's list of charging domains, Dappier's and Valyu's search. Coinbase's x402 Bazaar ranks by relevance and by "recent call volume and unique payers", and doesn't publish the weights (${a(src(76), 'Bazaar')}). Google, ProRata and Perplexity pick sources inside their own products.`,
+ `from your FORA file and your Exchange, or through a Broker that orders offers by relevance (see ${a('#broker-order', 'How a Broker orders offers')}). No index spans every FORA site.`,
+ ) },
+];
+const QUESTIONS_REST = [
+ { title: 'Who is the buyer, provably?', text: qa(
+ `most use an account and an API key; TollBit and MonetizationOS also match user agents. Cloudflare, AWS and Akamai check Web Bot Auth signatures, and Parallel's crawlers sign with it ${cite(44, 57, 58, 86)}.`,
+ `a signature on every request, checked against a key on the buyer's own domain. Cloudflare's bot verification doesn't recognize a FORA agent: it "will fail to verify a message if" it uses the later drafts' header form, which FORA's SDKs send (${a(src(57), 'Cloudflare')}). FORA's edge function checks the signed link itself, and your Cloudflare rules must let signed requests through.`,
+ ) },
+ { title: 'What lets a given use happen?', text: qa(
+ 'a pass only TollBit can check; a signed price header Cloudflare checks; an x402 payment AWS verifies; an API key.',
+ 'a signed link that expires and can be bound to the agent\'s key. Any edge holding the Exchange\'s public key can check it.',
+ ) },
+ { title: 'Who sets the price, in what unit?', text: qa(
+ 'you, at bot paywalls, Dappier, Cashmere, Snowflake and CCC\'s per-order sales. The channel itself, at answer engines, Google, Valyu, AskNews and Factiva. The buyer, in Pay Per Use. Units run from a page to a query, a summary, a share or a year.',
+ `you, per term. A term is free, flat or per unit, limited by use, country and buyer type, with caps (${a(src(5), 'Licensing terms')}). FORA has no revenue-share price. A buyer that already pays you a share under a contract buys under a deal term (${a(src(5, '#revenue-share-arrangements'), 'Revenue share')}).`,
+ ) },
+ { title: 'How does money move?', text: qa(
+ 'TollBit, Cloudflare, CCC and Snowflake collect from the buyer and pay you; Google pays you from its own programs; the rails move money per request.',
+ FORA_CELLS.money,
+ ) },
+ { title: 'What do you see?', text: qa(
+ `TollBit and Cloudflare show bot traffic ${cite(31, 37)}; AWS lists each settlement; Google shows one monthly earnings number; ProRata sends monthly statements per article.`,
+ 'each sale, in the publisher console your Exchange operator runs. No protocol call returns your sales.',
+ ) },
+ { title: 'What if the numbers are wrong?', text: qa(
+ 'TollBit and Cloudflare bill only on a delivered page and document no dispute call; ProRata grants an audit right.',
+ FORA_CELLS.disputes,
+ ) },
+];
+
+const SETUP = [
+ { title: 'Register your domain.', text: `On the publisher console, name your domain and the paths you license, then choose your terms (${a(src(1), 'Publisher onboarding')}).` },
+ { title: 'Serve your FORA file.', text: 'Serve it unchanged on your site. A later change to it needs no redeploy.' },
+ { title: 'Add the edge function.', text: 'The console builds it for Cloudflare or CloudFront, and it sits beside what your CDN already runs.' },
+ { title: 'Let two kinds of request through your firewall.', text: `Signed requests, and requests for your FORA file, must get past your WAF and bot product (${a(src(3, '#keeping-cdn-bot-protection-on'), 'Keeping CDN bot protection on')}).` },
+ { title: 'Keep a sitemap.', text: 'The operator imports your pages from it.' },
+];
+
+const BUY_STEPS = [
+ { text: 'You set your terms with your Exchange, and your FORA file names the Exchanges that sell your pages.' },
+ { text: `An AI agent signs every request with one key, published on its own domain. An assistant on MCP gets one from FORA's ${a(src(6), 'Identity Service')}.` },
+ { text: 'The agent asks a Broker, with a list of URLs or in plain words. For each URL, the Broker reads your FORA file and asks one of your Exchanges that it trusts.' },
+ { text: 'Your Exchange answers with offers it signed, each carrying your terms and price.' },
+ { text: 'The Broker checks every signature and returns the offers, grouped by URL. The agent chooses.' },
+ { text: `The agent signs one acceptance over every offer it picks, across Exchanges. The Broker splits the purchase per Exchange (${a(src(7, '#buying-through-the-broker'), 'Broker')}).` },
+ { text: 'Each Exchange charges the agent\'s own account and issues a signed link. The agent fetches the page from your CDN, which checks the link. The Broker never charges anyone and never sees the content.' },
+ { text: `Your Exchange operator pays you under your agreement. ${SEE_ABOUT}` },
+];
+
+const SELL_THROUGH = [
+ { title: 'Marketplaces with their own catalog.', text: `A retrieval marketplace, a collective or a rights agency can run a FORA Exchange and Broker over its own catalog and keep its search (${a(src(8), 'For content marketplaces')}).` },
+ { title: 'Buyers that pay a share or a fee.', text: `An AI company that pays you a share or a fee under a deal could buy as a FORA agent, under a deal term (${a(src(5, '#revenue-share-arrangements'), 'Revenue share')}).` },
+ { title: 'Rights agencies and rails.', text: 'A CCC order maps almost field for field to a FORA term; CCC documents no buyer API. An Exchange operator can collect over x402 or fund an agent\'s account through Skyfire; settlement stays outside the protocol.' },
+];
+
+const TODO = [
+ { title: 'Ask who has paid.', text: 'Ask each channel for named buyers and the totals they paid.' },
+ { title: 'Ask for the fee.', text: `TollBit's, Cloudflare's and Microsoft's aren't published. Ask what a buyer pays in total and what you keep. FORA itself is free, open-source software; for the fee at FORA\'s publisher console, see ${ABOUT}.` },
+ { title: 'List what you hand over.', text: 'A subdomain, your logs with your readers\' requests in them, a copy of your archive, a CDN rule. Ask how many engineer-days each one takes.' },
+ { title: 'Keep one price per page.', text: 'If a page is on sale in two places, know both prices.' },
+ { title: 'Order your CDN rules.', text: 'Let each partner\'s fetcher and the search crawlers through, and keep each paywall\'s rule off the others\' paying buyers.' },
+ { title: 'Sell to agents as well.', text: 'Register with an Exchange operator, serve your FORA file and install the edge function on Cloudflare, Fastly or CloudFront. Agents can then buy under your terms beside every channel above.' },
+];
+
+const LEGAL = [
+ { title: 'Exclusivity.', text: `Check whether a grant includes training, and whether it is exclusive. An exclusive training grant stops you selling training anywhere else. ProRata's MSA is non-exclusive (${a(src(80), 'ProRata MSA')}).` },
+ { title: 'Room for another channel.', text: 'Microsoft\'s PCM runs beside FORA on one site only if your PCM contract allows it.' },
+ { title: 'A record of each FORA sale.', text: `With each purchase the buyer signs an acceptance of your terms, and the publisher console can check that signature (${a(src(1, '#after-setup'), 'Publisher onboarding')}).` },
+];
+
+// Deep pages: the series' pages (their index summaries), with the collective
+// page from the Resources list, in the copy's order.
+const collective = RESOURCES.find((r) => r.href === '/resources/transparent-collective/');
+const series = SERIES.filter((p) => p.href !== HREF);
+const DEEP = [
+ ...series.filter((p) => p.href.startsWith(HREF)),
+ ...(collective ? [collective] : []),
+ ...series.filter((p) => !p.href.startsWith(HREF)),
+].map(({ href, title, summary }) => ({ href, title, summary }));
+
+const updated = resourceUpdated(HREF) ?? SERIES.find((p) => p.href === HREF)?.updated;
+---
+
+
+ See the map
+ What FORA takes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The map's "Who pays today" column has the rest, in each channel's own words.
+
+
+
+
+
Reading note. The rows compare channels built for different jobs: a rail carries no license, and a collective doesn't set your price. "Who pays today", "Who sets the price" and "What your engineers change" compare like for like. A dash means the channel has nothing to state there. Figures from a vendor are the vendor's own and directional.
+
+
Court settlements price no future use, so they fit none of the three.
+
+
Announced, not running. Next Net and Sundial's SAIL ledger (2026-07-14) names no buyer and publishes no specification ${cite(99)}. AWS hasn't announced the content marketplace The Information reported in February 2026 ${cite(100)}.`} />
+
+ What your engineers change, in full
+
+ {ENGINEERS_FULL.map((it) =>
{it.title}
)}
+
+
+
+
+
+
+
+
Bot paywalls: the bot pays at your door
+
tollbit.news.example.com, which TollBit runs. By default a bot without TollBit's pass gets HTTP 402, "payment required". The buyer pays your rate plus "a small transaction fee on top of the rates you set", whose size isn't published (${a(src(27), 'Setting rates')}).`} />
+
+
+
+
+
+
+
+ {KINDS.map((k) => (
+
+
{k.title}
+ {k.paras.map((p) => )}
+
+ ))}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Beside TollBit. TollBit says another marketplace can run "in parallel" (${a(src(32), 'TollBit')}). Let TollBit's fetcher through FORA's edge, and keep TollBit's rule off requests that carry a FORA signed link. You write that order; FORA ships no combined rule.`} />
+
Beside Cloudflare. FORA's edge runs as a Worker after Cloudflare's own rules.`} />
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
How a Broker orders offers
+
+
+
+
Your TollBit rates, shown to FORA agents
+
+
+
How other channels can use FORA
+
+
+
+
What FORA can't do with them
+
Settling a FORA sale through TollBit or Pay Per Crawl. TollBit's API bills at TollBit's rates, and Pay Per Crawl charges when a crawler fetches a page. Neither one's docs describe a way to bill an amount for a sale made elsewhere.`} />
+
Answer engines' and Google's content as offers. ProRata, Perplexity, Microsoft and Google license your content for their own products, and Microsoft for the partners it brings in. None offers it to any other agent.`} />
+
+
+
+
+
+
+
+
+ What is FORA?
+ Publisher onboarding
+ For content marketplaces
+
+
+
+
diff --git a/website/src/pages/resources/content-marketplaces/microsoft-pcm.astro b/website/src/pages/resources/content-marketplaces/microsoft-pcm.astro
new file mode 100644
index 00000000..b8012a19
--- /dev/null
+++ b/website/src/pages/resources/content-marketplaces/microsoft-pcm.astro
@@ -0,0 +1,436 @@
+---
+// Resource: Microsoft Publisher Content Marketplace (PCM) and FORA, one of the
+// deep pages of the content-marketplaces series (hub:
+// /resources/content-marketplaces/). Laid out in the vendor page template, as
+// the TollBit page: hero, at a glance, the short answer, how you're paid, key
+// facts, who has signed and been paid, what it takes on your site, search
+// traffic, where PCM is ahead, the eight questions, running both, what to do,
+// and About FORA with the sources and the series navigation.
+//
+// Shared texts (About FORA, the definitions, the search callout, the table
+// questions, the GlanceCard rows and FORA's fixed cells) come from
+// src/data/content-marketplaces.ts. A claim cites its source inline, as a
+// link, or with cite(N), which links to entry N of the numbered SourceList at
+// the foot; SOURCES below is numbered as the copy numbers it, so an entry's
+// position is its number. Text with links is HTML and goes through set:html.
+import LandingLayout from '../../../layouts/LandingLayout.astro';
+import AudienceHero from '../../../components/landing/AudienceHero.astro';
+import Band from '../../../components/landing/Band.astro';
+import GlanceCard from '../../../components/landing/GlanceCard.astro';
+import CardGrid from '../../../components/landing/CardGrid.astro';
+import Callout from '../../../components/landing/Callout.astro';
+import StepList from '../../../components/landing/StepList.astro';
+import Figure from '../../../components/landing/Figure.astro';
+import KeyFacts from '../../../components/landing/KeyFacts.astro';
+import PullQuote from '../../../components/landing/PullQuote.astro';
+import Split from '../../../components/landing/Split.astro';
+import PointList from '../../../components/landing/PointList.astro';
+import CompareTable from '../../../components/landing/CompareTable.astro';
+import CodeCard from '../../../components/landing/CodeCard.astro';
+import SourceList from '../../../components/landing/SourceList.astro';
+import SeriesNav from '../../../components/landing/SeriesNav.astro';
+import ClosingCta from '../../../components/landing/ClosingCta.astro';
+import { resourceUpdated } from '../../../data/resources';
+import {
+ ABOUT_FORA, DEFINITIONS, SEARCH_FORA, FORA_CELLS, SEE_ABOUT, compareRows, glanceGroups,
+} from '../../../data/content-marketplaces';
+import { cite, statusTag } from '../../../lib/resource-markup';
+
+const HREF = '/resources/content-marketplaces/microsoft-pcm/';
+const IMG = '/resources/content-marketplaces/microsoft-pcm';
+
+// Every external source the page links.
+const M = {
+ launch: 'https://about.ads.microsoft.com/en/blog/post/february-2026/building-toward-a-sustainable-content-economy-for-the-agentic-web',
+ product: 'https://preview-about.ads.microsoft.com/en/solutions/technology/publisher-content-marketplace',
+ bing: 'https://blogs.bing.com/search/2026/10/your-content-your-choice-clearer-preferences-for-training-and-grounding/',
+ kolar: 'https://digiday.com/media/qa-nikhil-kolar-vp-microsoft-ai-scales-its-click-to-sign-ai-content-marketplace/',
+ yahoo: 'https://www.yahooinc.com/press/introducing-yahoo-scout-a-new-ai-answer-engine',
+ sej: 'https://www.searchenginejournal.com/googles-ai-payment-pilot-vs-cloudflare-and-microsoft-models/589636/',
+ gannett: 'https://www.editorandpublisher.com/stories/gannett-announces-third-quarter-2025-results-new-ai-licensing-deal-with-microsoft-and-updated,258540',
+ iac: 'https://ir.iac.com/static-files/e2666073-0141-41f8-a45d-77ea800a65be',
+ ap: 'https://digiday.com/media/media-briefing-associated-press-deal-cements-microsofts-quiet-rise-in-ai-licensing',
+ bi: 'https://talkingbiznews.com/media-news/business-insider-joining-microsoft-content-marketplace/',
+ verge: 'https://www.theverge.com/news/873296/microsoft-publisher-content-marketplace-ai-licensing',
+};
+// FORA's docs, as the copy links them.
+const D = {
+ onboarding: '/getting-started/publisher-onboarding/',
+ afterSetup: '/getting-started/publisher-onboarding/#after-setup',
+ serveFile: '/getting-started/publisher-onboarding/#serve-your-discovery-file',
+ deployment: '/components/edge-function/deployment/',
+ providersDocs: '/components/edge-function/deployment/#the-providers-own-documents',
+ botDetection: '/components/edge-function/bot-detection/',
+ keepBotProtection: '/components/edge-function/bot-detection/#keeping-cdn-bot-protection-on',
+ whatIsFora: '/getting-started/what-is-fora/',
+ howItWorks: '/getting-started/what-is-fora/#how-it-works',
+ edgeOverview: '/components/edge-function/overview/',
+ terms: '/protocol/licensing-terms/',
+ metering: '/protocol/licensing-terms/#metering-modes',
+ revenueShare: '/protocol/licensing-terms/#revenue-share-arrangements',
+ broker: '/components/broker/overview/',
+ auth: '/protocol/authentication/',
+};
+const a = (href: string, text: string) => `${text}`;
+const NP = statusTag('not-public');
+
+const GLANCE = glanceGroups({
+ payer: [`Microsoft, for Copilot's use: "paid on delivered value" ${cite(1)}. When, and who pays for other buyers' use: ${NP}`, FORA_CELLS.payer],
+ fees: [`For Copilot's use, Microsoft is the buyer ${cite(1)}.`, FORA_CELLS.fees],
+ reporting: [
+ `"Usage-based reporting" ${cite(1)}. What a report contains: ${NP}`,
+ `Each sale, with gross, the Exchange fee and net, in your operator's publisher console (${a(D.afterSetup, 'Publisher onboarding')}).`,
+ ],
+ contract: [
+ `With Microsoft, negotiated one by one in the pilot. The standard contract wasn't final in February 2026 ${cite(12)}.`,
+ `Your agreement with your Exchange operator (${a(D.deployment, 'Deployment')}). Your terms go into each offer the Exchange signs.`,
+ ],
+ status: [`${statusTag('pilot')} No payment is public ${cite(1)}.`, `${statusTag('live')} ${SEE_ABOUT}`],
+ dns: [`No change documented ${cite(1, 2)}.`, `No record to add (${a(D.deployment, 'Deployment')}).`],
+ cdn: [
+ `No change documented ${cite(1, 2)}.`,
+ 'A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.',
+ ],
+ firewall: [
+ `No bot rule documented. What your CDN blocks stays your decision ${cite(1, 2)}.`,
+ `Your firewall and bot product run first. They must let signed requests and your FORA file through (${a(D.keepBotProtection, 'Bot detection')}).`,
+ ],
+ site: [
+ `You hand over content through "the pipes" Microsoft built ${cite(12)}. Feed, API or crawl: ${NP}`,
+ `One file on your site, fora.json, naming your Exchanges. The operator imports your pages from your sitemap (${a(D.afterSetup, 'Publisher onboarding')}).`,
+ ],
+ search: [
+ `Bing's crawl is separate from PCM ${cite(3)}. How Bing's settings affect a PCM license: ${NP} See Search traffic, below.`,
+ `Googlebot, Bingbot and Applebot always pass ${cite(6)}. See Search traffic, below.`,
+ ],
+ upkeep: [
+ `How often you send content, and who keeps it current: ${NP}`,
+ `A change to your FORA file takes effect with nothing to redeploy (${a(D.providersDocs, 'Deployment')}).`,
+ ],
+ leaving: [`"Participation is voluntary" ${cite(1)}. How you leave: ${NP}`, FORA_CELLS.leaving],
+});
+
+const SHORT_ANSWER = [
+ { title: 'PCM brings a buyer.', text: `Microsoft runs the marketplace and buys through Copilot, and says it is "beginning to onboard" Yahoo ${cite(1)}. You sign a contract and hand over your content. Microsoft documents no change to your site.` },
+ { title: 'FORA brings an open interface.', text: 'Any agent finds your offers, signs for the terms it picks and gets an expiring link for that purchase. You serve one file and install the edge function on your CDN.' },
+ { title: 'They run side by side.', text: 'PCM publishes no API for outside software, so FORA can\'t connect to it without Microsoft. Both can run on one site, if your PCM contract allows it.' },
+];
+
+const PAID_STEPS = [
+ { title: 'You register interest.', text: `Microsoft's product page says: "Register your interest in the Publisher Content Marketplace to receive updates as our work progresses" (${a(M.product, 'product page')}). How publishers are selected: ${NP}` },
+ { title: 'You sign a contract.', text: `"With the pilot, we did individual negotiations with the publishers," Microsoft's Nikhil Kolar told Digiday in February 2026. A standard contract is planned, "but we’ve not finalized it yet" (${a(M.kolar, 'Digiday interview')}).` },
+ { title: 'You hand over your content.', text: `Kolar describes the first phase as getting "the pipes working — how does the content come in". Publishers can "clean up the content", for example an image licensed from someone else ${cite(12)}. By feed, API or crawl: ${NP}` },
+ { title: 'You set the terms.', text: `"Publishers define licensing and usage terms", with no published vocabulary ${cite(1)}. The primary use, in Microsoft's words, is "Grounding and Display": content grounds the answer to a single query, "and that same content is also displayed as a citation URL" in it. "PCM is for Grounding and Display use cases, not training" ${cite(2)}.` },
+ { title: 'Copilot uses it.', text: `Microsoft "started with a focused set of scenarios in enterprise and consumer versions of Microsoft Copilot". It is "beginning to onboard demand partners, including Yahoo" ${cite(1)}. Yahoo said on January 27, 2026, that it "is also joining Microsoft’s Publisher Content Marketplace pilot" (${a(M.yahoo, 'Yahoo')}). Whether Yahoo buys through PCM yet: ${NP}` },
+ { title: 'You\'re paid, and you get a report.', text: `PCM "provides usage-based reporting" ${cite(1)}. What a report contains: ${NP} Search Engine Journal noted the gap: the post "doesn’t say who sets the price or what the reports show" (${a(M.sej, 'SEJ')}).` },
+];
+
+const KEY_FACTS = [
+ { value: '2', text: `versions of Copilot PCM started with, enterprise and consumer ${cite(1)}` },
+ { value: '7', text: `US publishers Microsoft names as co-designers, "among others" ${cite(1)}` },
+ { value: '4', text: `publishers that confirmed their deals in late 2025 ${cite(15, 16, 17, 18)}` },
+ { value: '1', text: `buyer beyond Copilot that Microsoft names: Yahoo, which it is onboarding ${cite(1)}` },
+];
+
+const SITE_PCM = [
+ { title: 'How content gets in:', text: `through "the pipes" Microsoft built ${cite(12)}. Feed format, ingestion API, CMS plugin or crawler: ${NP}` },
+ { title: 'DNS and CDN:', text: `no change documented. The product page promises "a single, trusted path to make content available for AI use cases while preventing unwanted crawling" ${cite(2)}. It doesn't say how.` },
+ { title: 'Who gets in:', text: `Microsoft onboards the other buyers, such as Yahoo ${cite(1)}. How your contract limits them: ${NP} PCM documents no bot rule, so what your CDN blocks stays your decision.` },
+ { title: 'What a bot gets back:', text: 'PCM documents no answer to a bot, neither a redirect nor a payment-required response.' },
+ { title: 'Logs:', text: `none documented. You get "usage-based reporting" ${cite(1)}.` },
+];
+const SITE_FORA = [
+ { title: 'How content gets in:', text: `it stays on your site. The Exchange reads your sitemap, and you set terms in its operator's console. Or you push the catalog to it (${a(D.howItWorks, 'What is FORA?')}).` },
+ { title: 'DNS and CDN:', text: `you serve one file that names your Exchanges, and install the edge function on your CDN (${a(D.deployment, 'Deployment')}).` },
+ { title: 'Who gets in:', text: `you choose the paths you license. There, the edge function refuses AI bots that come without a signed link. Readers and search crawlers pass as before ${cite(6)}.` },
+ { title: 'What a bot gets back:', text: `a refusal that tells the bot where to buy ${cite(8)}.` },
+ { title: 'Logs:', text: `each refusal states its reason, the same reason the edge function logs ${cite(8)}. The Exchange records each sale.` },
+];
+
+const ENGINEER_STEPS = [
+ { title: 'Serve the file.', text: `Your operator's console gives you the file that names your Exchanges. Serve it unchanged (${a(D.serveFile, 'Publisher onboarding')}).` },
+ { title: 'Add the edge function.', text: `The console builds it for your domain, for Cloudflare or CloudFront, and it sits beside what your CDN already runs (${a(D.deployment, 'Deployment')}).` },
+ { title: 'Let signed requests through.', text: `On most CDNs, the firewall and bot product run before the edge function, so a bot rule there can refuse an agent that has already bought. Let signed requests through it (${a(D.keepBotProtection, 'Bot detection')}).` },
+ { title: 'How the edge function decides.', text: `On the paths you license, it matches the name each bot sends, its User-Agent, against FORA's published list of AI bots. It never matches Googlebot, Bingbot or Applebot ${cite(6)}.` },
+ { title: 'What a refused bot gets.', text: `A 403, with a header that points it to the file naming your Exchanges ${cite(8)}. There is no 402: the agent buys at the Exchange, before it fetches.` },
+];
+
+const CAUTIONS = [
+ { title: 'Blocking Bingbot takes you out of Bing search.', text: 'Bing\'s own grounding refusal doesn\'t.' },
+ { title: 'Grounding is refused page by page.', text: 'You set it with a meta tag or a response header: "There is no site-wide robots.txt grounding preference." Training can be refused per site or path in robots.txt, with the shared AI-training group that other crawlers can honor too, or per page.' },
+ { title: 'Bing has to crawl to see your choice.', text: '"Microsoft must crawl the page to discover the setting."' },
+ { title: 'NoArchive and NoCache stop counting.', text: 'After March 1, 2027, Bing no longer reads these older tags for training and grounding. If you use them to stay out of AI answers, also set a temporary preference in Bing Webmaster Tools before that date.' },
+];
+
+const AHEAD = [
+ { title: 'The buyer comes with the marketplace.', text: `PCM's operator is also its first buyer. Copilot comes in two versions, "the M365 copilot from the enterprise side, and the MAI copilot from the consumer side" ${cite(12)}. On FORA, any agent can buy.` },
+ { title: 'No change to your site that Microsoft documents.', text: `PCM needs a contract and your content: "Instead of blocking bots or negotiating one-off deals, tap into a transparent marketplace" ${cite(2)}. FORA asks for a file and an edge function, as above.` },
+ { title: 'A price set by what the answer needed.', text: `Kolar: "Sometimes, the value may be: ‘I just need to know the score.’" For a source that is "not substitutable", a buyer is "willing to pay a lot more" ${cite(12)}. PCM is designed to price a use by its worth in the answer. FORA can't: its price is fixed at the sale, and a usage report "never re-prices a purchase" (${a(D.metering, 'Licensing terms')}).` },
+ { title: 'Reports from inside the AI product.', text: `Microsoft runs Copilot, so its reports can come from the answer itself. Kolar: "we wanted to build a feedback loop from the demand side on how the content was used" ${cite(12)}. FORA can't report that. It records each sale, and of the use in an answer it knows only what the agent reports (${a(D.howItWorks, 'What is FORA?')}, step 5).` },
+ { title: 'A use that includes the citation.', text: `Grounding and Display ties one answer to one shown link. FORA can state the same duty in a term, as below, but nothing in FORA observes that the link was shown. For an outside buyer such as Yahoo, how PCM learns of the citation: ${NP}` },
+ { title: 'Deals you\'ve already made.', text: `Kolar calls it "bring-your-own-license": PCM "can become the infrastructure to deliver any license that you have negotiated outside the marketplace". "Some of the larger partners we work with already have a licensing deal," he says ${cite(12)}. PCM is built to carry such deals, to buyers Microsoft contracts. FORA carries them as a deal term (${a(D.revenueShare, 'Licensing terms')}).` },
+];
+
+const COMPARE = compareRows([
+ [
+ `In your PCM contract: "publisher-defined content and license terms". Nothing on your site says so to anyone else ${cite(2)}.`,
+ `Your FORA file names the Exchanges that sell your content, and you set terms per resource in your operator's publisher console ${cite(7)}.`,
+ ],
+ [
+ `"AI builders discover and license content for specific grounding scenarios" ${cite(1)}. How: ${NP}`,
+ `An agent asks your Exchange, or a Broker. Each Broker operator chooses its search, and each agent chooses its Broker ${cite(10)}.`,
+ ],
+ [
+ `Copilot, Microsoft's own product. Microsoft is "beginning to onboard" Yahoo ${cite(1)}. Agent identification: ${NP}`,
+ `Each request carries a signature, checked against the signer's published key (Web Bot Auth, the IETF working group's -00 draft) ${cite(11)}.`,
+ ],
+ [
+ `The contract. Pilot contracts were negotiated one by one; the standard contract was not final in February 2026 ${cite(12)}.`,
+ `A signed offer the agent accepts and signs, and a link that expires, checked at your CDN ${cite(7)}.`,
+ ],
+ [
+ `Paid "on delivered value" ${cite(1)}. The unit and who sets the number: ${NP}`,
+ `You: free, per unit (an access, a token, a page) or a flat fee, signed on each offer. Fixed at the sale, by design ${cite(9)}.`,
+ ],
+ [`For Copilot's use, Microsoft is the buyer ${cite(1)}. Who pays for any other partner's use, when, and any minimum: ${NP}`, FORA_CELLS.money],
+ [
+ `"usage-based reporting" on how content is "valued, cited, and used" ${cite(1, 2)}. What a report contains: ${NP}`,
+ `The operator's console: your sales, with gross, fee and net. It is each operator's own; no protocol call returns your sales ${cite(4)}.`,
+ ],
+ [`No dispute process is described ${cite(1, 2, 12)}.`, FORA_CELLS.disputes],
+]);
+
+const WORKS = [
+ { title: 'Run both.', text: `"Participation is voluntary," Microsoft says ${cite(1)}. For exclusivity, see For legal, below. PCM stays a contract, and the file on your site names your FORA Exchanges.` },
+ { title: 'Sell the same use to every other agent.', text: 'Grounding and Display is one FORA term. In words: AI answers are allowed and training isn\'t, the article is shown as a cited link, and each access costs $0.05.' },
+];
+
+// The term as it reads on the wire: field, then value.
+const TERM_LINES: [string, string][] = [
+ ['restrictions:', 'FUNCTION permitted: ai-input prohibited: ai-train'],
+ ['obligations:', 'ATTRIBUTION, on use:\n"Show the article as a cited link to news.example.com"'],
+ ['pricing:', 'PER_UNIT unit: accesses rate: "0.05" currency: USD'],
+];
+
+const TODO = [
+ { title: 'Ask how you join.', text: 'Microsoft\'s product page has an interest form, and doesn\'t say how publishers are selected.' },
+ { title: 'Ask for the unit and the price.', text: 'Microsoft hasn\'t published what it pays per use, or who sets the number. Ask both, in writing.' },
+ { title: 'Ask how your content gets in.', text: 'Microsoft hasn\'t published the route: a feed, an API or a crawl. Ask what you send, how often, and who keeps it up to date.' },
+ { title: 'Ask what the report shows.', text: `Microsoft promises insight into how content is "valued, cited, and used" ${cite(2)}. Ask for a sample report.` },
+ { title: 'Ask how Bing\'s settings affect your license.', text: 'If you refuse grounding in Bing, do you lose PCM money? If you\'re in PCM, can you still refuse it? Ask before you choose a setting.' },
+ { title: 'Sell to other agents too.', text: `Name your FORA Exchanges in fora.json and put a grounding term with a citation duty on your articles. FORA itself is free, open-source software. For the publisher console's fees, ${SEE_ABOUT.replace('See', 'see')}` },
+];
+
+const LEGAL = [
+ { title: 'Who you sign with.', text: `Microsoft. Pilot contracts were "individual negotiations"; a standard contract is planned, "but we’ve not finalized it yet" ${cite(12)}.` },
+ { title: 'What you license.', text: `"PCM is for Grounding and Display use cases, not training" ${cite(2)}. The terms are in your contract; Microsoft publishes no vocabulary for them.` },
+ { title: 'Rights you may not hold.', text: `Agency photos and syndicated stories may not be yours to hand over. Kolar gives a licensed-in image as the example ${cite(12)}. List what you can't license before you sign.` },
+ { title: 'Exclusivity.', text: `"Participation is voluntary" ${cite(1)}. Whether the contract lets you sell the same articles through FORA or anyone else: ${NP} Ask before you do.` },
+ { title: 'Bing\'s settings aren\'t a license.', text: `Bing says its preferences "do not establish licensing or payment arrangements" ${cite(3)}. How they interact with a PCM license: ${NP}` },
+ { title: 'Law, venue, disputes and exit.', text: `${NP} No dispute process is described.` },
+ { title: 'Changes.', text: `PCM is a pilot. Kolar: "what we launch may not be what we end up with" ${cite(12)}.` },
+];
+
+// The SourceList, numbered as the copy numbers it: an entry's position,
+// counted across the groups, is the N in cite(N).
+const fora = (title: string, href: string) => ({ title, publisher: 'FORA documentation', href, checked: '2026-11-15' });
+const SOURCES = [
+ {
+ name: 'Microsoft',
+ items: [
+ { title: 'Building toward a sustainable content economy for the agentic web', publisher: 'Microsoft Advertising', href: M.launch, checked: '2026-11-14' },
+ { title: 'Publisher Content Marketplace', publisher: 'Microsoft Advertising, served on Microsoft\'s preview host (preview-about.ads.microsoft.com)', href: M.product, checked: '2026-11-15' },
+ { title: 'Your content, your choice: clearer preferences for training and grounding', publisher: 'Bing', href: M.bing, checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'FORA',
+ items: [
+ fora('Publisher onboarding', D.onboarding),
+ fora('Deployment', D.deployment),
+ fora('Bot detection', D.botDetection),
+ fora('What is FORA?', D.whatIsFora),
+ fora('Edge function overview', D.edgeOverview),
+ fora('Licensing terms', D.terms),
+ fora('Broker', D.broker),
+ fora('Authentication', D.auth),
+ ],
+ },
+ {
+ name: 'Press, filings and others',
+ items: [
+ { title: 'Q&A: Nikhil Kolar, vp Microsoft AI', publisher: 'Digiday', href: M.kolar, checked: '2026-11-14' },
+ { title: 'Introducing Yahoo Scout', publisher: 'Yahoo', href: M.yahoo, checked: '2026-11-14' },
+ { title: 'Google\'s AI payment pilot vs. Cloudflare and Microsoft models', publisher: 'Search Engine Journal', href: M.sej, checked: '2026-11-14' },
+ { title: 'Gannett announces third quarter 2025 results', publisher: 'Editor and Publisher', href: M.gannett, checked: '2026-11-14' },
+ { title: 'Third quarter 2025 results', publisher: 'IAC', href: M.iac, checked: '2026-11-14' },
+ { title: 'Associated Press deal cements Microsoft\'s quiet rise in AI licensing', publisher: 'Digiday', href: M.ap, checked: '2026-11-14' },
+ { title: 'Business Insider joining Microsoft content marketplace', publisher: 'Talking Biz News', href: M.bi, checked: '2026-11-14' },
+ { title: 'Microsoft\'s Publisher Content Marketplace', publisher: 'The Verge', href: M.verge, checked: '2026-11-14' },
+ ],
+ },
+];
+---
+
+
+ Where PCM is ahead
+ Use both
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Microsoft publishes no count of publishers. Neither Microsoft nor a publisher has said a payment was made.
+
+
+
+
+
+
PCM
+
+
+
+
FORA
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
PCM documents nothing that touches search crawlers. Bing's crawl, above, is a separate route into Copilot.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Works today
+
+
+
+ Grounding and Display as one FORA term.
+
+
+
Doesn't fit
+
Paying FORA sales through PCM. PCM is a marketplace with Microsoft as the payer, and no payment service for others. On FORA, the Exchange operator bills the buyer and pays you (${a(D.howItWorks, 'What is FORA?')}).`} />
+
Declaring PCM in a file. Microsoft publishes no file or tag that says a site is in PCM. Asked whether RSL could work with PCM, Microsoft's spokesperson didn't have "anything specific to share today" (${a(M.verge, 'The Verge')}, February 3, 2026). Say it on your licensing page, in words.`} />
+
+
+
+
+
+
+
+
+
+
+
Sources
+
Sources are checked on the date of publication.
+
+
+
+
+
+
+ Licensing terms
+ Run your own marketplace
+ All content marketplaces
+ What FORA takes on your CDN
+
+
+
+
diff --git a/website/src/pages/resources/content-marketplaces/perplexity.astro b/website/src/pages/resources/content-marketplaces/perplexity.astro
new file mode 100644
index 00000000..77701219
--- /dev/null
+++ b/website/src/pages/resources/content-marketplaces/perplexity.astro
@@ -0,0 +1,389 @@
+---
+// Resource: Perplexity's Publishers' Program and Comet Plus, and FORA, one of the deep pages of the
+// content-marketplaces series (hub: /resources/content-marketplaces/). Laid
+// out in the vendor page template, as the TollBit page is: hero, at a glance,
+// the short answer, how Comet Plus is meant to pay you, key facts, who has
+// been paid, what it takes on your site, what can go wrong, where Perplexity
+// is ahead, the eight questions, running both, what to do, the background,
+// the sources, and About FORA with the series navigation.
+//
+// Shared texts (About FORA, the definitions, the search callout, the table
+// questions, the GlanceCard rows and FORA's fixed cells) come from
+// src/data/content-marketplaces.ts. A claim cites its source inline, as a
+// link, or with cite(N), which links to entry N of the numbered SourceList;
+// SOURCES below is numbered in order of first citation, so an entry's
+// position is its number. Text with links is HTML and goes through set:html.
+import LandingLayout from '../../../layouts/LandingLayout.astro';
+import AudienceHero from '../../../components/landing/AudienceHero.astro';
+import Band from '../../../components/landing/Band.astro';
+import GlanceCard from '../../../components/landing/GlanceCard.astro';
+import CardGrid from '../../../components/landing/CardGrid.astro';
+import Callout from '../../../components/landing/Callout.astro';
+import StepList from '../../../components/landing/StepList.astro';
+import Figure from '../../../components/landing/Figure.astro';
+import KeyFacts from '../../../components/landing/KeyFacts.astro';
+import PullQuote from '../../../components/landing/PullQuote.astro';
+import Split from '../../../components/landing/Split.astro';
+import PointList from '../../../components/landing/PointList.astro';
+import CompareTable from '../../../components/landing/CompareTable.astro';
+import StatusTag from '../../../components/landing/StatusTag.astro';
+import SourceList from '../../../components/landing/SourceList.astro';
+import SeriesNav from '../../../components/landing/SeriesNav.astro';
+import ClosingCta from '../../../components/landing/ClosingCta.astro';
+import { resourceUpdated } from '../../../data/resources';
+import {
+ ABOUT_FORA, DEFINITIONS, SEARCH_FORA, FORA_CELLS, SEE_ABOUT, compareRows, glanceGroups,
+} from '../../../data/content-marketplaces';
+import { cite, statusTag } from '../../../lib/resource-markup';
+
+const HREF = '/resources/content-marketplaces/perplexity/';
+const IMG = '/resources/content-marketplaces/perplexity';
+
+// Every external source the page links.
+const X = {
+ comet: 'https://www.perplexity.ai/hub/blog/introducing-comet-plus',
+ partners: 'https://www.perplexity.ai/hub/blog/announcing-comet-plus-launch-partners',
+ program: 'https://www.perplexity.ai/hub/blog/introducing-the-perplexity-publishers-program',
+ pricing: 'https://www.perplexity.ai/hub/pricing',
+ crawlers: 'https://docs.perplexity.ai/docs/resources/perplexity-crawlers',
+ robots: 'https://www.perplexity.ai/help-center/en/articles/10354969-how-does-perplexity-follow-robots-txt',
+ bullying: 'https://www.perplexity.ai/hub/blog/bullying-is-not-innovation',
+ keys: 'https://www.perplexity.ai/.well-known/http-message-signatures-directory',
+ dowJones: 'https://www.perplexity.ai/hub/blog/about-the-dow-jones-lawsuit',
+ searchApi: 'https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service-search',
+ plans: 'https://www.perplexity.ai/help-center/en/articles/11187416-which-perplexity-subscription-plan-is-right-for-you',
+ digiday: 'https://digiday.com/media/how-perplexity-new-revenue-model-works-according-to-its-head-of-publisher-partnerships/',
+ gigazine: 'https://gigazine.net/gsc_news/en/20260219-perplexity-drops-ads-hurt-trust-ai',
+ hurdles: 'https://digiday.com/media/media-briefing-here-are-the-hurdles-to-perplexitys-pitch-as-the-publisher-friendly-llm',
+ cnn: 'https://storage.courtlistener.com/recap/gov.uscourts.nysd.664916/gov.uscourts.nysd.664916.1.0_1.pdf',
+ nyt: 'https://www.sec.gov/Archives/edgar/data/71691/000007169126000041/nyt-20260930.htm',
+ pressGazette: 'https://pressgazette.co.uk/news/perplexity-launches-ai-subscription-revenue-share-scheme-for-publishers/',
+ archive: 'https://web.archive.org/web/20251204132150/https://www.perplexity.ai/hub/blog/announcing-comet-plus-launch-partners',
+ thewrap: 'https://www.thewrap.com/industry-news/public-policy-legal/cnn-sues-perplexity-ai-stealing-news-chatbot-copyright/',
+};
+const a = (href: string, text: string) => `${text}`;
+
+const GLANCE = glanceGroups({
+ payer: [`Perplexity says it pays, from a pool of Comet Plus revenue, by its own counts. Schedule, threshold and currency: Not public ${cite(1)}.`, FORA_CELLS.payer],
+ fees: [`Perplexity keeps "a small portion" for compute; 20% in press reports ${cite(1, 12)}.`, FORA_CELLS.fees],
+ reporting: [
+ `No Comet Plus statement format is published ${cite(1, 2)}. 2024 partners got analytics on how Perplexity cites them ${cite(3)}.`,
+ `Each sale, in your operator's publisher console, with gross, the Exchange fee and net (${a('/getting-started/publisher-onboarding/', 'Publisher onboarding')}).`,
+ ],
+ contract: [
+ `A private contract, after an email to Perplexity. No standard agreement is published ${cite(1)}.`,
+ `Your agreement with your Exchange operator; your terms go into each offer it signs ${cite(21)}.`,
+ ],
+ status: [
+ `${statusTag('not-public')} Comet Plus isn't on Perplexity's ${a(X.pricing, 'pricing page')}. Whether it still pays out isn't public.`,
+ `${statusTag('live')} ${SEE_ABOUT}`,
+ ],
+ dns: [`No change in Perplexity's docs ${cite(5)}.`, `No record to add ${cite(20)}.`],
+ cdn: [
+ `No code in Perplexity's docs ${cite(5)}.`,
+ 'A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.',
+ ],
+ firewall: [
+ `An allow rule that matches each Perplexity crawler to its own IP ranges ${cite(5)}.`,
+ `Keep your bot protection, and let AI agents that name themselves reach the edge function. Or let signed requests and your discovery file through (${a('/components/edge-function/bot-detection/', 'Bot detection')}).`,
+ ],
+ site: [
+ `No feed, file or API. How your paywall lets a Comet Plus subscriber in: Not public ${cite(5, 6)}.`,
+ `One file that names your Exchanges, and a sitemap the operator imports your pages from ${cite(20)}.`,
+ ],
+ search: [
+ `PerplexityBot builds Perplexity's search index and follows robots.txt ${cite(5, 6)}.`,
+ `Googlebot, Bingbot and Applebot always pass ${cite(22)}. PerplexityBot is refused on licensed paths by default. See Search traffic, below.`,
+ ],
+ upkeep: [
+ `A scheduled job to refresh Perplexity's IP ranges, which Perplexity updates regularly ${cite(5)}.`,
+ `Change your Exchanges by editing your discovery file, with nothing to redeploy ${cite(20)}.`,
+ ],
+ leaving: ['Not public.', FORA_CELLS.leaving],
+});
+
+const SHORT_ANSWER = [
+ { title: 'Perplexity is the buyer.', text: 'Comet Plus is meant to share Perplexity\'s own revenue with the publishers it signs, for use in its answer engine, its Comet browser and Comet Assistant. No other AI company buys publisher content through its programs.' },
+ { status: 'not-public' as const, title: 'Whether Comet Plus still pays isn\'t public.', text: 'Comet Plus isn\'t on Perplexity\'s pricing page or plan guide. CNN, a launch partner, never got from its term sheet to a contract, its complaint says. CNN sued Perplexity on 2026-05-28.' },
+ { title: 'FORA prices the access, on the same site.', text: 'You set the price, the unit and the terms for each page. Any agent can buy, and each purchase is a signed record. You can let Perplexity\'s search crawler in and sell to other agents through FORA on one site.' },
+];
+
+const PAY_STEPS = [
+ { title: 'You email and sign.', text: `"Publishers interested in participating can join the program by emailing us via publishers@perplexity.ai" (${a(X.comet, 'Introducing Comet Plus')}). No standard agreement is published.` },
+ { title: 'Subscribers pay Perplexity.', text: `"Comet Plus will be a $5 standalone subscription. Pro and Max subscribers get Comet Plus included in their memberships" ${cite(1)}.` },
+ { title: 'Subscribers reach your site.', text: `They get "direct access to the sites and content of participating publishers", and their assistants can "complete tasks on those sites" ${cite(1)}. How your paywall recognizes a subscriber isn't public.` },
+ { title: 'Perplexity counts three kinds of traffic.', text: `Comet Plus "allocates revenue to our partners based on three types of internet traffic: human visits, search citations, and agent actions" ${cite(1)}. Digiday describes the visits as "direct visits to publisher's sites by people browsing using Comet". It describes agent actions as content "used to complete tasks by Comet's AI assistant" (${a(X.digiday, 'Digiday')}, published 2025-08-26). Perplexity counts all three in its own products, with no independent count described.` },
+ { title: 'The revenue becomes a pool.', text: `"We're distributing all of that revenue to participating publishers, minus a small portion for Perplexity's compute costs" ${cite(1)}. Digiday reported that "Perplexity keeps 20% of it" and that Perplexity is "opening up a pool of $42.5 million to publishers". Perplexity's own pages give neither figure.` },
+ { title: 'The pool is split by weights you don\'t see.', text: 'Asked whether one kind of use weighs more, Jessica Chan, Perplexity\'s head of publisher partnerships, told Digiday: "The details will be very specific to our partners, but you are thinking about it correctly." The weights aren\'t published.' },
+ { title: 'Perplexity says it pays.', text: 'No schedule, threshold, currency or statement format is published.' },
+];
+
+const KEY_FACTS = [
+ { value: '$5', text: `Comet Plus on its own; Pro and Max subscribers get it included ${cite(1)}` },
+ { value: '3', text: `Kinds of traffic Perplexity counts: human visits, search citations and agent actions ${cite(1)}` },
+ { value: '$42.5 million', text: `The pool Digiday reported; Perplexity's own pages don't give it ${cite(1, 12)}` },
+ { value: 'Not public', text: `The weight on each kind of traffic, per partner ${cite(12)}` },
+];
+
+const ENGINEERS = [
+ { title: 'How your content reaches Perplexity.', text: 'PerplexityBot crawls your pages for Perplexity\'s search index, and "Perplexity partners with third-party crawlers to help build our search index". Perplexity-User fetches a page when a user\'s question needs it. You publish no feed, file or API.' },
+ { title: 'The allow rule.', text: 'If your firewall screens bots, Perplexity asks for an allow rule that matches each crawler\'s user agent to its own published IP ranges. It advises an automated job to keep the ranges current.' },
+ { title: 'On Cloudflare.', text: 'A custom rule set to Skip, placed above the rules that block or challenge, lets both crawlers past them.' },
+ { title: 'With FORA on the same site.', text: `Apply Perplexity's IP-range rules in your CDN's firewall, which runs before FORA's edge function. The edge function knows both crawlers by the names they send, and a name can be copied (${a('/components/edge-function/bot-detection/', 'Bot detection')}).` },
+ { title: 'Nothing is metered at your site.', text: 'Perplexity\'s docs describe no payment response, no redirect and no signed link. It counts visits, citations and agent actions in its own products, and describes no log feed in either direction. Its one word on logs is to "Monitor your logs" to see that its crawlers get through.' },
+];
+
+const CAUTIONS = [
+ { title: 'A blocked page can still show.', text: `If robots.txt blocks a page, Perplexity "may still index the domain, headline, and a brief factual summary" ${cite(6)}.` },
+ { title: 'Changes take time.', text: `A robots.txt change "may take up to 24 hours" to apply ${cite(5)}.` },
+ { title: 'The ranges move.', text: `"These addresses are updated regularly", so an allow rule that isn't refreshed falls behind ${cite(5)}.` },
+ { title: 'Bot Fight Mode stays on.', text: `On Cloudflare, "Bot Fight Mode can't be skipped with WAF custom rules" ${cite(5)}.` },
+];
+
+const AHEAD = [
+ { title: 'You have a buyer from the day you sign.', text: `Perplexity is the buyer. The Financial Times reported "around $200 million in annual revenue" (via ${a(X.gigazine, 'Gigazine')}, published 2026-02-19). A Perplexity executive told it the service has "more than 100 million users", the vendor's own figure. On FORA, any agent your terms allow can buy from your Exchange.` },
+ { title: 'Joining asks only for crawler rules.', text: `Joining is an email and a contract, and the only technical ask Perplexity documents is the crawler rules above. FORA asks you to publish a file that names your Exchanges, sign with an Exchange, set your terms in its console and install its edge function on your CDN (${a('/getting-started/what-is-fora/', 'What is FORA?')}).` },
+ { title: 'It counts traffic FORA can\'t see.', text: `Two of Comet Plus's counts, human visits and agent actions, happen in the reader's browser, as Digiday describes them. Perplexity's position is that "Your AI assistant must be indistinguishable from you" (${a(X.bullying, 'Bullying is not innovation')}, published 2025-11-04). FORA's edge function knows AI bots by the names they send, and a request it doesn't recognize passes as a reader.` },
+ { title: 'Its share counts citations.', text: `Search citations are one of its three counts. FORA fixes the charge when the agent buys, and a usage report "never re-prices a purchase" (${a('/protocol/licensing-terms/#metering-modes', 'Licensing terms')}). A FORA usage report can record a citation, but no FORA pricing unit counts them.` },
+ { title: 'It sends paying readers to your own site.', text: `Comet Plus "is specifically designed to allow publishers to own the direct relationship with their audience" ${cite(2)}. FORA has no reader product. It licenses machine access.` },
+ { title: 'The pool is a set sum, if it still pays.', text: `Publishing executives told Digiday the model "does seem more developed than the ad revenue share program … mostly because the company is setting aside a specific pool of money" (${a(X.hurdles, 'Digiday')}, published 2025-08-28). On FORA, your income is the sum of what agents buy, with no floor.` },
+];
+
+const COMPARE = compareRows([
+ [`In a private contract. Nothing on your site states the terms to anyone else ${cite(1)}.`, `Your fora.json names the Exchanges that sell your content; you set terms per resource in the Exchange operator's console ${cite(21)}.`],
+ [`No outside buyer does. PerplexityBot and third-party crawlers build Perplexity's own index ${cite(5, 6)}.`, `An agent asks your Exchange, or a Broker, which returns your signed offers unchanged (${a('/resources/content-marketplaces/#broker-order', 'how a Broker orders offers')}) ${cite(24)}.`],
+ [`Two crawlers, known by name and published IP ranges ${cite(5)}. Perplexity's crawler docs describe no request signatures, and its site serves no signing-key directory ${cite(5, 8)}. Comet Assistant is meant to be "indistinguishable from you" ${cite(7)}.`, `Each request carries a signature, checked against a key the buyer publishes on its own domain (Web Bot Auth, the IETF working group's -00 draft) ${cite(21, 25)}.`],
+ [`The contract. PerplexityBot follows robots.txt; Perplexity-User, which fetches pages for a user, "generally ignores robots.txt rules" ${cite(5, 6)}.`, `A signed offer the agent accepts and signs, and a signed link that expires, checked at your CDN ${cite(21)}.`],
+ [`Perplexity: the pool, its own cut ("a small portion"; 20% in press reports) and each partner's weights. You set no price ${cite(1, 12)}.`, `You: free, per unit (an access, or text tokens, about ¾ of a word each) or a flat fee, signed on each offer. A revenue share is a term priced at zero that only agents naming the deal see, with a reporting duty (${a('/protocol/licensing-terms/#revenue-share-arrangements', 'Revenue share')}).`],
+ [`Perplexity pays from the pool, by its own account. Schedule, threshold and currency aren't published ${cite(1)}.`, FORA_CELLS.money],
+ [`2024 partners got analytics on how Perplexity cites them ${cite(3)}. No Comet Plus statement format is published ${cite(1, 2)}.`, `Each sale, with its signed offer and the agent's signed acceptance, in your Exchange operator's console (FORA Server's shows gross, fee and net). No protocol call returns your sales ${cite(20)}.`],
+ [`No dispute process is published. Publishers' disagreements with Perplexity have gone to court; see For legal ${cite(9, 15, 16)}.`, FORA_CELLS.disputes],
+]);
+
+const WORKS_TODAY = [
+ { title: 'Run both.', text: 'Your fora.json names your FORA Exchanges. Your Perplexity deal stays a private contract. Check it for exclusivity first; see For legal.' },
+ { title: 'Choose which Perplexity crawler gets in.', text: `On the paths you license, FORA's edge function refuses Perplexity-User without a signed link, as it does every bot that fetches a page because a user asked (${a('/components/edge-function/bot-detection/', 'Bot detection')}). It refuses PerplexityBot there too by default. If Perplexity sends you readers, let PerplexityBot in; it then reads those pages free.` },
+];
+
+const TODO = [
+ { title: 'Ask whether Comet Plus still pays.', text: 'It isn\'t on Perplexity\'s pricing page or plan guide. Ask before you plan on it.' },
+ { title: 'Ask how your share is computed.', text: 'Ask for your counts of human visits, search citations and agent actions each period, the weight on each, and the pool total. Without them you can\'t recompute your share.' },
+ { title: 'Ask what the pool holds.', text: `Digiday reported that Pro and Max revenue is pooled; Press Gazette reported "$5 from the more expensive Pro and Max subscriptions" (${a(X.pressGazette, 'Press Gazette')}, published 2025-10-02). Ask which.` },
+ { title: 'Ask how a subscriber gets past your paywall.', text: 'Perplexity doesn\'t document it, so ask before your team estimates the work.' },
+ { title: 'Ask how Comet\'s visits show in your numbers.', text: 'Perplexity doesn\'t document which user agent Comet sends. Ask whether its visits count as human pageviews in your analytics and ad reporting, and how to tell them apart. Ask your ad partners too.' },
+ { title: 'Read the contract for limits and exclusivity.', text: 'See For legal.' },
+ { title: 'Set your crawler rules.', text: 'Decide whether PerplexityBot reads your licensed pages, which FORA\'s edge refuses by default (see Search traffic). Keep Perplexity\'s published IP ranges current in your firewall.' },
+ { title: 'Sell to other agents as well.', text: `Name your FORA Exchanges in fora.json and set your price per resource. FORA itself is free, open-source software. For the publisher console's fees, see About FORA.` },
+];
+
+const LEGAL = [
+ { title: 'No standard agreement.', text: 'Joining is an email and a private contract. Perplexity publishes no standard agreement.' },
+ { title: 'Use in answers.', text: `CNN's complaint names "limits on Perplexity's use of CNN content in its answers to users" among the issues CNN and Perplexity couldn't agree on (${a(X.cnn, 'CNN\'s complaint')}, ¶47). Settle how Perplexity may use your content in answers.` },
+ { title: 'Exclusivity.', text: 'Whether a Comet Plus contract limits licensing the same content to other AI companies isn\'t public. Check yours before you set FORA terms for the same uses.' },
+ { title: 'Disputes.', text: `Perplexity publishes no dispute process. Publishers' disagreements with Perplexity have gone to court as copyright suits: CNN, The New York Times and Dow Jones, among others, have sued it ${cite(9, 15, 16)}.` },
+];
+
+const TIMELINE = [
+ { title: 'July 2024: an ad-revenue share.', text: `The Publishers' Program shared ad revenue "when Perplexity earns revenue from an interaction where a publisher's content is referenced" (${a(X.program, 'Publishers\' Program')}). Of that ad share, Chan told Digiday in August 2025: "we are not disclosing any of those numbers." Asked whether checks had gone out to publishers, she said: "Checks have gone out."` },
+ { title: 'From the end of 2025: no ads.', text: `The Financial Times reported, as Gigazine relayed, that Perplexity would phase out its ads from the end of 2025 ${cite(13)}.` },
+ { title: 'October 2025: CNN, a launch partner.', text: `CNN's deal began as a term sheet, "with an agreement to finalize the contract within sixty days" (¶46) ${cite(15)}. Perplexity's partner page listed CNN as a launch partner from 2025-10-02 until at least 2025-12-04 (${a(X.archive, 'Internet Archive, capture of 2025-12-04')}).` },
+ { title: 'November 2025: the term sheet ends.', text: `CNN's complaint says the term sheet never became a contract, over issues that include limits on use in answers (see For legal). It says the two agreed to end the term sheet on 2025-11-24 (¶47) ${cite(15)}.` },
+ { title: 'May 2026: CNN sues.', text: `CNN sued Perplexity on 2026-05-28. Perplexity's response, to TheWrap: "You can’t copyright facts." ${cite(19)}` },
+ { title: 'November 2026: off the pricing page.', text: `Perplexity's ${a(X.pricing, 'pricing page')} and ${a(X.plans, 'plan guide')} don't list Comet Plus, and Perplexity hasn't announced its end.` },
+];
+
+// The SourceList, numbered in order of first citation: an entry's position,
+// counted across the groups, is the N in cite(N).
+const SOURCES = [
+ {
+ name: 'Perplexity',
+ items: [
+ { title: 'Introducing Comet Plus', publisher: 'Perplexity', href: X.comet, checked: '2026-11-15' },
+ { title: 'Announcing Comet Plus launch partners', publisher: 'Perplexity', href: X.partners, checked: '2026-11-14' },
+ { title: 'Introducing the Perplexity Publishers\' Program', publisher: 'Perplexity', href: X.program, checked: '2026-11-14' },
+ { title: 'Pricing', publisher: 'Perplexity', href: X.pricing, checked: '2026-11-15' },
+ { title: 'Perplexity Crawlers', publisher: 'Perplexity', href: X.crawlers, checked: '2026-11-15' },
+ { title: 'How does Perplexity follow robots.txt?', publisher: 'Perplexity', href: X.robots, checked: '2026-11-15' },
+ { title: 'Bullying is not innovation', publisher: 'Perplexity', href: X.bullying, checked: '2026-11-14' },
+ { title: 'Signing-key directory address (returns HTTP 404)', publisher: 'Perplexity', href: X.keys, checked: '2026-11-15' },
+ { title: 'About the Dow Jones lawsuit', publisher: 'Perplexity', href: X.dowJones, checked: '2026-11-14' },
+ { title: 'API Terms of Service - Search Service', publisher: 'Perplexity', href: X.searchApi, checked: '2026-11-14' },
+ { title: 'Which Perplexity Subscription Plan is right for you?', publisher: 'Perplexity', href: X.plans, checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Press, filings and others',
+ items: [
+ { title: 'How Perplexity\'s new revenue model works, according to its head of publisher partnerships', publisher: 'Digiday', href: X.digiday, checked: '2026-11-14' },
+ { title: 'Perplexity will phase out ads introduced in 2024 from the end of 2025', publisher: 'Gigazine', href: X.gigazine, checked: '2026-11-14' },
+ { title: 'Media Briefing: Here are the hurdles to Perplexity\'s pitch as the publisher-friendly LLM', publisher: 'Digiday', href: X.hurdles, checked: '2026-11-14' },
+ { title: 'Cable News Network, Inc. v. Perplexity AI, Inc., complaint', publisher: 'U.S. District Court for the Southern District of New York', href: X.cnn, checked: '2026-11-14' },
+ { title: 'Form 10-Q for the quarter ended September 30, 2026', publisher: 'The New York Times Company', href: X.nyt, checked: '2026-11-14' },
+ { title: 'Perplexity launches AI subscription revenue-share scheme for publishers', publisher: 'Press Gazette', href: X.pressGazette, checked: '2026-11-14' },
+ { title: 'Announcing Comet Plus launch partners, capture of 2025-12-04', publisher: 'Internet Archive', href: X.archive, checked: '2026-11-14' },
+ { title: 'CNN Sues Perplexity for Unlawfully Distributing News Content, AI Company Responds: ‘You Can’t Copyright Facts’', publisher: 'TheWrap', href: X.thewrap, checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'FORA',
+ items: [
+ { title: 'Publisher onboarding', publisher: 'FORA documentation', href: '/getting-started/publisher-onboarding/', checked: '2026-11-15' },
+ { title: 'What is FORA?', publisher: 'FORA documentation', href: '/getting-started/what-is-fora/', checked: '2026-11-15' },
+ { title: 'Bot detection', publisher: 'FORA documentation', href: '/components/edge-function/bot-detection/', checked: '2026-11-15' },
+ { title: 'Licensing terms', publisher: 'FORA documentation', href: '/protocol/licensing-terms/', checked: '2026-11-15' },
+ { title: 'Broker', publisher: 'FORA documentation', href: '/components/broker/overview/', checked: '2026-11-15' },
+ { title: 'Authentication', publisher: 'FORA documentation', href: '/protocol/authentication/', checked: '2026-11-15' },
+ ],
+ },
+];
+---
+
+
+ Where Perplexity is ahead
+ Run both
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
PerplexityBot builds Perplexity's search index, and it follows robots.txt. How refusing it changes your Comet Plus share isn't public.
+
+
+
+
+
+
+
+
+
+
+
Both are ways to license Perplexity's use of your content, and they compose on your site, where you choose what each Perplexity crawler gets.
+
+
+
+
Works today
+
+
Doesn't fit
+
Comet Plus as a marketplace for FORA agents. A FORA Broker presents offers that a seller signs. Perplexity licenses no partner's article to other AI companies. Its Search API sells results that its terms say are "sourced from the public internet", and the customer doesn't own them (${a(X.searchApi, 'Search API terms')}). There is no signed license offer to present.`} />
+
Paying FORA sales through Comet Plus. Perplexity offers no payment service to anyone else. It allocates the pool from its own traffic counts.'} />
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Sources are checked on the date of publication.
+
+
+
+
+
+
+
+
+
+ What is FORA?
+ Run your own marketplace
+ Licensing terms
+ All content marketplaces
+
+
+
+
diff --git a/website/src/pages/resources/content-marketplaces/prorata-gist.astro b/website/src/pages/resources/content-marketplaces/prorata-gist.astro
new file mode 100644
index 00000000..51e3e3bc
--- /dev/null
+++ b/website/src/pages/resources/content-marketplaces/prorata-gist.astro
@@ -0,0 +1,369 @@
+---
+// Resource: ProRata.ai and Gist, and FORA, one of the deep pages of the
+// content-marketplaces series (hub: /resources/content-marketplaces/). Laid
+// out in the vendor page template, as the TollBit page is: hero, at a glance,
+// the short answer, how you're paid, key facts, how your articles get into
+// answers, who has been paid, what Gist Answers needs from your site, what can
+// go wrong, where ProRata is ahead, the eight questions, running both, what to
+// do, and About FORA with the sources and the series navigation.
+//
+// Shared texts (About FORA, the definitions, the search callout, the table
+// questions, the GlanceCard rows and FORA's fixed cells) come from
+// src/data/content-marketplaces.ts. A claim cites its source inline, as a
+// link, or with cite(N), which links to entry N of the numbered SourceList at
+// the foot; SOURCES below is numbered in order of first citation, so an
+// entry's position is its number. Text with links is HTML and goes through
+// set:html.
+import LandingLayout from '../../../layouts/LandingLayout.astro';
+import AudienceHero from '../../../components/landing/AudienceHero.astro';
+import Band from '../../../components/landing/Band.astro';
+import GlanceCard from '../../../components/landing/GlanceCard.astro';
+import CardGrid from '../../../components/landing/CardGrid.astro';
+import Callout from '../../../components/landing/Callout.astro';
+import StepList from '../../../components/landing/StepList.astro';
+import Figure from '../../../components/landing/Figure.astro';
+import KeyFacts from '../../../components/landing/KeyFacts.astro';
+import PullQuote from '../../../components/landing/PullQuote.astro';
+import PointList from '../../../components/landing/PointList.astro';
+import CompareTable from '../../../components/landing/CompareTable.astro';
+import StatusTag from '../../../components/landing/StatusTag.astro';
+import SourceList from '../../../components/landing/SourceList.astro';
+import SeriesNav from '../../../components/landing/SeriesNav.astro';
+import ClosingCta from '../../../components/landing/ClosingCta.astro';
+import { resourceUpdated } from '../../../data/resources';
+import {
+ ABOUT_FORA, DEFINITIONS, SEARCH_FORA, FORA_CELLS, SEE_ABOUT, compareRows, glanceGroups,
+} from '../../../data/content-marketplaces';
+import { cite, statusTag } from '../../../lib/resource-markup';
+
+const HREF = '/resources/content-marketplaces/prorata-gist/';
+const IMG = '/resources/content-marketplaces/prorata-gist';
+
+// Every external source the page links.
+const P = {
+ msa: 'https://gist.ai/support/ga/wpnewpartner',
+ ads: 'https://gist.ai/gist-ads-discontinued',
+ guide: 'https://gist.ai/support/ga/wpuserguide',
+ answers: 'https://gist.ai/products/gist-answers',
+ products: 'https://prorata.ai/products',
+ how: 'https://prorata.ai/how-it-works',
+ paper: 'https://prorata.ai/resources/without-attribution-quality-content-cannot-survive',
+ terms: 'https://gist.ai/terms-of-use',
+ nma: 'https://www.newsmediaalliance.org/prorata-licensing-partnership/',
+ dpcmo: 'https://dpcmo.dk/2025/12/10/prorata-partners-with-dpcmo-to-launch-the-first-decentralized-sovereign-ai-answer-engine/',
+};
+const a = (href: string, text: string) => `${text}`;
+
+const GLANCE = glanceGroups({
+ payer: [`ProRata itself, monthly, by bank transfer once you're owed more than $1,000. Its Gist Ads network ended on 2026-09-01; Gist Answers still runs. ProRata hasn't said what funds the pool since ${cite(1, 2)}.`, FORA_CELLS.payer],
+ fees: [`A share of a pool, not a rate: see How you're paid ${cite(1)}.`, FORA_CELLS.fees],
+ reporting: [
+ `A monthly statement, and per article: answers it was used in, its average attribution, citation clicks. Not the month's total revenue or answer count ${cite(1, 3)}.`,
+ `Each sale in your operator's console: gross, the Exchange fee and net, and a check of both signatures ${cite(9)}.`,
+ ],
+ contract: [
+ `ProRata's online MSA, accepted on a web form. Non-exclusive. ProRata can change it; if you object, you can only end it ${cite(1)}.`,
+ `Your agreement with your Exchange operator. Your terms go into each offer the Exchange signs ${cite(10)}.`,
+ ],
+ status: [
+ `${statusTag('live')} "150+" publishing partners, by ProRata's count. No payout total published ${cite(4)}.`,
+ `${statusTag('live')} ${SEE_ABOUT}`,
+ ],
+ dns: [`No change ${cite(3)}.`, `No record to add ${cite(9)}.`],
+ cdn: [
+ `No code. Cache rules must keep the feed working, and you purge the cache after a correction ${cite(3)}.`,
+ 'A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.',
+ ],
+ firewall: [
+ `An allow rule for ProRata's crawler. Its user agent and IP ranges aren't published: ask ProRata ${cite(3)}.`,
+ `Leave your licensed paths and your discovery file to the edge function, or keep your bot product on and let signed requests and the file through ${cite(11)}.`,
+ ],
+ site: [
+ `The WordPress plugin or one script tag. Posts only, by default. How other CMSs get in isn't documented ${cite(3, 4)}.`,
+ `One discovery file on your site, and a sitemap the operator imports your pages from ${cite(9)}. No WordPress plugin.`,
+ ],
+ search: [
+ `Gist blocks no bot ${cite(3)}.`,
+ `Googlebot, Bingbot and Applebot always pass ${cite(11)}. See Search traffic, below.`,
+ ],
+ upkeep: [
+ `WordPress's scheduler must run, or nothing is sent. Removals go by email ${cite(3)}.`,
+ `The operator imports your pages on a schedule. Editing your discovery file needs no redeploy ${cite(9)}.`,
+ ],
+ leaving: [`End the MSA. Content already ingested stays until you email the URLs ${cite(1, 3)}.`, FORA_CELLS.leaving],
+});
+
+const SHORT_ANSWER = [
+ { title: 'ProRata measures the answer.', text: `Its engine splits each Gist answer into claims, finds the sources that support them, and divides a pool of half its net revenue by those shares.` },
+ { title: 'FORA prices the access.', text: 'You set the price, the unit and the terms for each resource, and your Exchange signs each offer. Any agent your terms allow can buy on them, and each purchase is a signed record.' },
+ { title: 'They fit on one site.', text: 'ProRata\'s contract is non-exclusive, so you can sell through FORA on the same site. Gist needs its WordPress plugin or a script tag.' },
+];
+
+const PAID_STEPS = [
+ { title: 'Half the month\'s revenue becomes a pool.', text: `Half of ProRata's net revenue from its answer products goes to "the pool of all content partners" (${a(P.msa, 'MSA §5')}). That revenue comes from "advertising, subscriptions, and sponsorships (if any)" in ProRata's own products.` },
+ { title: 'Every answer that month is worth the same.', text: 'Each valid answer, as ProRata counts them, carries the month\'s revenue divided by the month\'s valid answers. So what one answer earned ProRata doesn\'t change what it pays you.' },
+ { title: 'Your share depends on how much of the answer is yours.', text: `You get that amount, times 50%, times your attribution percent: the share of the answer's claims your content supplied (${a(P.msa, 'MSA §5')}).` },
+ { title: 'You\'re paid above $1,000.', text: `ProRata sends a monthly statement and pays by bank transfer "once the amount due to Partner exceeds one thousand dollars ($1,000)" (${a(P.msa, 'MSA §5')}). Until then, your earnings carry over.` },
+];
+
+const KEY_FACTS = [
+ { value: '50%', text: `of ProRata's net revenue from its answer products goes to the partner pool ${cite(1)}` },
+ { value: '50%', text: `of the widget's ad revenue on your site is yours ${cite(1)}` },
+ { value: '1 year', text: `ProRata keeps the records you can have inspected ${cite(1)}` },
+ { value: '7 days', text: `"from kickoff to live for a typical site, depending on your CMS and catalog size", by ProRata's count ${cite(4)}` },
+];
+
+const ARTICLE_STEPS = [
+ { title: 'You sign.', text: `You accept ProRata's Online Master Services Agreement (MSA) on a web form, and an API key follows "within 2 business days upon approval" (${a(P.msa, 'sign-up page and MSA')}).` },
+ { title: 'ProRata reads your site.', text: `You paste one script tag or install the WordPress plugin. The plugin registers your public posts feed and sends each post's address when the post is saved. ProRata's crawler, a program that fetches your pages, then reads the post through the feed: "Gist Answers sees only what an anonymous visitor sees" (${a(P.guide, 'WordPress user guide')}).` },
+ { title: 'Readers ask.', text: `The Gist widget on your pages, and ProRata's own answer site, ask.gist.ai, answer readers' questions. You choose the sources: your site, your whole organization, or the "Full Gist network" (${a(P.answers, 'Gist Answers')}).` },
+ { title: 'The engine measures each answer.', text: `It breaks the answer into claims, "atomic units of fact", and matches them to the sources. Then it computes "the proportion of the answer's total claims provided by each source and creator" (${a(P.how, 'How it works')}). The white paper names three weights, for originality, specificity and commonality, and gives no values for them (${a(P.paper, 'white paper')}).` },
+];
+
+const ENGINEERS = [
+ { title: 'Content.', text: 'By default ProRata takes posts only, through your public posts feed, /wp-json/wp/v2/posts. Pages and custom post types need a filter in code, and "Adding a post type with a filter is not retroactive".' },
+ { title: 'Sending.', text: 'The plugin queues each post\'s address on save, and WordPress\'s scheduler sends the queue.' },
+ { title: 'Cache.', text: 'The feed must honor its date filter, which "a page or edge cache rule, a security rule, or a plugin that changes REST queries" can break. The plugin "does not bypass or purge any cache", so after a correction you purge the post and the feed yourself.' },
+ { title: 'Bot protection.', text: 'Your bot protection has to let ProRata\'s crawler read the feed: a 401 or 403 "means the crawl of the feed fails". The crawler\'s user agent and IP ranges aren\'t published, so an allow rule needs them from ProRata.' },
+ { title: 'Widget and logs.', text: 'Readers\' browsers load the widget from Gist\'s own CDN. There is no log stream; the console shows per-article numbers and the MSA adds the monthly statement.' },
+];
+
+const CAUTIONS = [
+ { title: 'Paywalled text arrives empty.', text: 'A password-protected post, or text a paywall plugin hides, reaches Gist empty: "Gist Answers can answer from neither".' },
+ { title: 'A stopped scheduler stops everything.', text: 'Sending runs on WordPress\'s scheduler: "Without it, queued content is never sent."' },
+ { title: 'No consent control.', text: 'For consent banners, "There is no consent setting and no JavaScript API to load or unload the widget".' },
+];
+
+// Six points; the edge function's define callout follows the fourth, the
+// point that first names it.
+const AHEAD_1 = [
+ { title: 'It measures how much of an answer you supplied.', text: `ProRata returns "attribution scorecards at claim, article, publication, and publisher levels" (${a(P.how, 'How it works')}). ProRata can pay you by your share of each answer; FORA cannot. A FORA price is fixed when the agent buys, and a usage report, the buyer's later account of its use, "never re-prices a purchase" (${a('/protocol/licensing-terms/#metering-modes', 'Licensing terms')}).` },
+ { title: 'It publishes its payout rule.', text: `The pool, the split per answer and the $1,000 threshold are in a contract anyone can read (${a(P.msa, 'MSA §5')}). The console shows each article's "Average attribution", "the percentage of an answer that an article's content makes up" (${a(P.guide, 'user guide')}). The attribution itself is ProRata's to compute: the weights' values aren't published. FORA is software and sets no payout terms: each Exchange operator pays you under its own agreement (${a('/getting-started/what-is-fora/', 'What is FORA?')}).` },
+ { title: 'It pays you itself, and gives your readers a product.', text: `You don't wait for an AI company to buy: ProRata pays the pool from its own answer products. The widget answers readers on your pages at no AI cost to you, and the MSA gives you half of the widget's ad revenue on your site (${a(P.msa, 'MSA §5')}). ProRata says readers who use Gist Answers on one McClatchy site, Woman's World, stay about three times as long. That's its own data, with no period given (${a(P.answers, 'Gist Answers')}). On FORA, any agent your terms allow buys from your Exchange, and your operator pays you.` },
+ { title: 'It puts no code on your CDN.', text: `Gist needs one script tag or plugin on your pages, and its WordPress plugin "handles ingestion, configuration, management and reporting" (${a(P.answers, 'Gist Answers')}). Your work is the feed, your cache rules and an allow rule for the crawler, whose identity you get from ProRata. FORA asks more: you set your terms in an Exchange operator's console, serve one file that names your Exchanges, and add FORA's edge function to your CDN (${a('/getting-started/publisher-onboarding/', 'Publisher onboarding')}). A WordPress plugin for FORA is planned ${statusTag('roadmap')}.` },
+];
+const AHEAD_2 = [
+ { title: 'It gives you an audit right.', text: `If you dispute a payment, an independent third party can inspect ProRata's records, kept for a year after each payment (${a(P.msa, 'MSA §6')}). FORA's protocol gives a publisher no audit right. ${SEE_ABOUT}` },
+ { title: 'It reaches you through your trade association.', text: `The News/Media Alliance, which by its own count represents "more than 2,200" news, magazine and digital media organizations, lets its members opt into a license with ProRata (${a(P.nma, 'N/MA')}, announced 2025-03-26). Denmark's DPCMO offers its members "a pre-negotiated partnership agreement" (${a(P.dpcmo, 'DPCMO')}, announced 2025-12-10). With FORA, an association can run an Exchange for its members.` },
+];
+
+const COMPARE = compareRows([
+ [`You click to accept the MSA, which grants fixed uses: answers in ProRata's products, and attribution. Nothing on your site says so to anyone else ${cite(1)}.`, `Your fora.json names the Exchanges that sell your content; you set terms per resource in the Exchange operator's console ${cite(9, 10)}.`],
+ [`No outside buyer does. ProRata's engine picks sources from its own index of partner content and doesn't publish how it picks them. On your widget, "Answers come from your content first" ${cite(4)}.`, `From your Exchange, or through a Broker (${a('/resources/content-marketplaces/#broker-order', 'how a Broker orders offers')}) ${cite(13)}.`],
+ [`There is no outside buyer. ProRata's crawler publishes no user agent or IP ranges ${cite(3)}.`, `Each request carries a signature, checked against a key the buyer publishes on its own domain (Web Bot Auth, the IETF working group's -00 draft for signed bot requests) ${cite(10)}.`],
+ [`The MSA grant, for every answer ProRata generates during the contract ${cite(1)}.`, `An offer the Exchange signs and the agent accepts, and a signed link that expires, checked at your CDN ${cite(10)}.`],
+ [`ProRata: 50% of net revenue, split per valid answer by attribution. The online MSA sets the same split for every partner who accepts it. ProRata can change the terms ${cite(1)}.`, `You: free, per unit (pages, text tokens, seconds or your own) or a flat fee, signed on each offer. No revenue-share price, by design: a share is a free term shown to agents that state the deal's scope, with a reporting duty (${a('/protocol/licensing-terms/#revenue-share-arrangements', 'Revenue share')}).`],
+ [`ProRata pays by bank transfer, monthly, once you're owed more than $1,000 ${cite(1)}.`, FORA_CELLS.money],
+ [`A monthly statement per partner, publication and article (above a minimum number of answers): answers, average attribution, revenue. Not the month's total revenue or answer count ${cite(1)}.`, `The operator's console: each sale with gross, fee and net, and a check of both signatures. The console is each operator's own; no protocol call returns your sales ${cite(9)}.`],
+ [`An independent inspection of one year of records, then the courts of Los Angeles County ${cite(1)}.`, FORA_CELLS.disputes],
+]);
+
+const ONE_SITE = [
+ { title: 'Run both.', text: `ProRata's licenses "are nonexclusive" (${a(P.msa, 'MSA §13')}), and Gist Answers "fits alongside anything else in your AI strategy" (${a(P.answers, 'Gist Answers')}). Your FORA discovery file names your FORA Exchanges; the ProRata deal stays a private contract.` },
+ { title: 'Let ProRata\'s crawler through your bot product.', text: `On most CDNs the bot product runs before FORA's edge function, so it can block the crawler first (${a('/components/edge-function/bot-detection/', 'Bot detection')}). Allow the crawler there, with the user agent and IP ranges you get from ProRata. FORA's edge function recognizes AI bots mainly by the name they give, and ProRata's crawler isn't on its list, so the edge lets it through (${a('/getting-started/publisher-onboarding/', 'Publisher onboarding')}).` },
+ { title: 'If you license your articles at the edge, license the feed too.', text: `Your WordPress posts feed serves the same article text to any client. If only the article pages are licensed, an AI bot can read the text from the feed instead. So license the feed's path with your articles (${a('/getting-started/publisher-onboarding/', 'Publisher onboarding')}). Before you do, ask your engineers what else reads the feed, such as your mobile app or your AMP pages, and test them after the change.` },
+];
+
+const TODO = [
+ { title: 'Ask for the pool totals.', text: 'Your statement doesn\'t show the month\'s total revenue or total valid answers, so you can\'t recompute your share. Ask for both, which answers count as valid, and where the share of each answer that no partner gets goes.' },
+ { title: 'Ask what funds the pool.', text: 'Ask which products pay into the pool now that Gist Ads has ended, and whether the widget on your pages still carries ads, and whose.' },
+ { title: 'Check the feed as a stranger would.', text: 'Open your posts feed in a private browser window, with and without a date filter, as the user guide shows. Ask support@gist.ai for the crawler\'s user agent and IP ranges, and allow it at your CDN.' },
+ { title: 'Keep your own removal list.', text: `The plugin sends no removal signal, so content stays in Gist until you email the URLs (${a(P.guide, 'user guide')}). Ask what happens to the content already ingested if you end the MSA.` },
+ { title: 'Audit within the year.', text: `ProRata keeps its records for one year after each payment (${a(P.msa, 'MSA §6')}).` },
+ { title: 'Sell to agents as well.', text: `ProRata's contract is non-exclusive. Choose an Exchange operator (see About FORA), name your FORA Exchanges in fora.json, set your price per resource, and cover the posts feed at the edge.` },
+];
+
+const LEGAL = [
+ { title: 'ProRata can change the terms.', text: `It amends the MSA by posting a new version. "If you object to any such changes, your sole recourse will be to terminate this Agreement" (${a(P.msa, 'MSA §13')}).` },
+ { title: 'Non-exclusive.', text: '"The rights and licenses that each Party grants to the other Party under this Agreement are nonexclusive" (MSA §13).' },
+ { title: 'Audit.', text: 'A partner that "reasonably disputes Revenue Share paid" can have "an independent third party confidentially inspect the Records", kept for a year after each payment (MSA §6).' },
+ { title: 'Removal.', text: 'After written notice, ProRata stops using the content "within one (1) business day" (MSA §7). The plugin sends no removal signal, so the notice is yours to send.' },
+ { title: 'Consent.', text: 'The widget has no consent setting (see What can go wrong).' },
+ { title: 'Venue.', text: '"The federal and state courts located in Los Angeles County will have sole and exclusive jurisdiction" (MSA §13).' },
+ { title: 'Version.', text: 'The MSA quoted here is the one "Last updated: October 27, 2026".' },
+];
+
+// The SourceList, numbered in order of first citation: an entry's position,
+// counted across the groups, is the N in cite(N).
+const SOURCES = [
+ {
+ name: 'ProRata.ai and Gist',
+ items: [
+ { title: 'ProRata Online Master Services Agreement (MSA)', publisher: 'ProRata.ai', href: P.msa, checked: '2026-11-15' },
+ { title: 'Gist Ads discontinued', publisher: 'ProRata.ai', href: P.ads, checked: '2026-11-14' },
+ { title: 'Gist Answers for WordPress: user guide', publisher: 'ProRata.ai', href: P.guide, checked: '2026-11-15' },
+ { title: 'Gist Answers', publisher: 'ProRata.ai', href: P.answers, checked: '2026-11-14' },
+ { title: 'Products', publisher: 'ProRata.ai', href: P.products, checked: '2026-11-14' },
+ { title: 'How it works', publisher: 'ProRata.ai', href: P.how, checked: '2026-11-14' },
+ { title: 'Without attribution, quality content cannot survive (white paper)', publisher: 'ProRata.ai', href: P.paper, checked: '2026-11-14' },
+ { title: 'Terms of Use', publisher: 'Gist', href: P.terms, checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'FORA',
+ items: [
+ { title: 'Publisher onboarding', publisher: 'FORA documentation', href: '/getting-started/publisher-onboarding/', checked: '2026-11-15' },
+ { title: 'What is FORA?', publisher: 'FORA documentation', href: '/getting-started/what-is-fora/', checked: '2026-11-15' },
+ { title: 'Bot detection', publisher: 'FORA documentation', href: '/components/edge-function/bot-detection/', checked: '2026-11-15' },
+ { title: 'Licensing terms', publisher: 'FORA documentation', href: '/protocol/licensing-terms/', checked: '2026-11-15' },
+ { title: 'Broker', publisher: 'FORA documentation', href: '/components/broker/overview/', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Press, filings and others',
+ items: [
+ { title: 'ProRata licensing partnership', publisher: 'News/Media Alliance', href: P.nma, checked: '2026-11-14' },
+ { title: 'ProRata partners with DPCMO', publisher: 'DPCMO', href: P.dpcmo, checked: '2026-11-14' },
+ ],
+ },
+];
+---
+
+
+ Where ProRata is ahead
+ Run both
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Gist doesn't block, meter, redirect or charge any bot, so every bot rule on your site stays yours, and search crawlers reach your site as today.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
On one site
+
+
Doesn't fit
+
Gist answers as FORA offers. Gist sells agents nothing: its terms forbid access by any "agent or other automatic device" (${a(P.terms, 'Terms of Use')}). A Gist answer is also written when someone asks, and FORA sells resources that exist before the sale (${a('/getting-started/what-is-fora/#scope', 'What is FORA?')}). ProRata offers no payment service to others either, so an Exchange can't settle through it.`} />
+
+
+
+
+
+
+
+
+
+
+
+
+
Sources
+
Sources are checked on the date of publication.
+
+
+
+
+
+
+ Licensing terms
+ Run your own marketplace
+ All content marketplaces
+
+
+
+
diff --git a/website/src/pages/resources/content-marketplaces/tollbit.astro b/website/src/pages/resources/content-marketplaces/tollbit.astro
new file mode 100644
index 00000000..e3d07e91
--- /dev/null
+++ b/website/src/pages/resources/content-marketplaces/tollbit.astro
@@ -0,0 +1,406 @@
+---
+// Resource: TollBit and FORA, one of the deep pages of the content-marketplaces
+// series (hub: /resources/content-marketplaces/). Laid out in the vendor page
+// template: hero, at a glance, the short answer, how you're paid, key facts,
+// who has been paid, what it takes on your site, what can go wrong, where
+// TollBit is ahead, the eight questions, running both, what to do, and About
+// FORA with the sources and the series navigation.
+//
+// Shared texts (About FORA, the definitions, the search callout, the table
+// questions, the GlanceCard rows and FORA's fixed cells) come from
+// src/data/content-marketplaces.ts. A claim cites its source inline, as a
+// link, or with cite(N), which links to entry N of the numbered SourceList at
+// the foot; SOURCES below is numbered in order of first citation, so an
+// entry's position is its number. Text with links is HTML and goes through
+// set:html.
+import LandingLayout from '../../../layouts/LandingLayout.astro';
+import AudienceHero from '../../../components/landing/AudienceHero.astro';
+import Band from '../../../components/landing/Band.astro';
+import GlanceCard from '../../../components/landing/GlanceCard.astro';
+import CardGrid from '../../../components/landing/CardGrid.astro';
+import Callout from '../../../components/landing/Callout.astro';
+import StepList from '../../../components/landing/StepList.astro';
+import Figure from '../../../components/landing/Figure.astro';
+import KeyFacts from '../../../components/landing/KeyFacts.astro';
+import PullQuote from '../../../components/landing/PullQuote.astro';
+import Split from '../../../components/landing/Split.astro';
+import PointList from '../../../components/landing/PointList.astro';
+import CompareTable from '../../../components/landing/CompareTable.astro';
+import StatusTag from '../../../components/landing/StatusTag.astro';
+import SourceList from '../../../components/landing/SourceList.astro';
+import SeriesNav from '../../../components/landing/SeriesNav.astro';
+import ClosingCta from '../../../components/landing/ClosingCta.astro';
+import { resourceUpdated } from '../../../data/resources';
+import {
+ ABOUT_FORA, DEFINITIONS, SEARCH_FORA, FORA_CELLS, SEE_ABOUT, compareRows, glanceGroups,
+} from '../../../data/content-marketplaces';
+import { cite, statusTag } from '../../../lib/resource-markup';
+
+const HREF = '/resources/content-marketplaces/tollbit/';
+const IMG = '/resources/content-marketplaces/tollbit';
+
+// Every external source the page links.
+const T = {
+ overview: 'https://tollbit.com/docs/',
+ tokens: 'https://docs.tollbit.com/docs/tokens',
+ settingRates: 'https://docs.tollbit.com/docs/setting-rates',
+ security: 'https://docs.tollbit.com/docs/security',
+ terms: 'https://tollbit.com/legal/publisher-platform-agreement/',
+ license: 'https://gateway.tollbit.com/license/j4ikxb8qqsu2qu91q78a9e70/ON_DEMAND_LICENSE_ka02vqvjacoy2i5vs8z90hxm',
+ verifying: 'https://docs.tollbit.com/docs/verifying-a-property',
+ cloudflare: 'https://docs.tollbit.com/docs/cloudflare',
+ integrations: 'https://docs.tollbit.com/docs/integrations',
+ botManagement: 'https://docs.tollbit.com/docs/bot-management',
+ licensedSearch: 'https://docs.tollbit.com/docs/licensed-search',
+ rates: 'https://docs.tollbit.com/docs/rates',
+ akamai: 'https://tollbit.com/blog/akamai-partnership/',
+ seriesA: 'https://tollbit.com/blog/series-a/',
+ home: 'https://tollbit.com/',
+ staticIps: 'https://tollbit.com/static-ips.txt',
+ architecture: 'https://docs.tollbit.com/docs/platform-architecture',
+ other: 'https://docs.tollbit.com/docs/other',
+ configure: 'https://docs.tollbit.com/docs/step-3-configure-agent-site',
+ cache: 'https://docs.tollbit.com/docs/content-cache',
+ defaults: 'https://docs.tollbit.com/docs/content-formatting-1',
+ aws: 'https://docs.tollbit.com/docs/aws-s3-cloudfront-alb',
+ devOverview: 'https://docs.tollbit.com/docs/dev-overview',
+ analytics: 'https://docs.tollbit.com/docs/step-2-enable-analytics',
+ content: 'https://docs.tollbit.com/docs/content',
+ edgeConfig: 'https://github.com/FORA-Protocol/reference-implementation/blob/main/src/edge/CONFIGURATION.md',
+ tnl: 'https://www.prnewswire.com/news-releases/tnl-mediagene-announces-early-success-in-ai-content-licensing-revenue-model-via-tollbit-marketplace-integration-and-strategic-partnership-302647966.html',
+ digiday: 'https://digiday.com/media/the-washington-posts-arc-xp-adds-tollbit-to-help-publishers-make-money-from-ai-bot-traffic/',
+};
+const a = (href: string, text: string) => `${text}`;
+
+const GLANCE = glanceGroups({
+ payer: [`TollBit, through Stripe, early each month, in US dollars ${cite(1, 2)}.`, FORA_CELLS.payer],
+ fees: [`You keep your full rate. The buyer pays a fee on top; its size isn't published ${cite(3)}.`, FORA_CELLS.fees],
+ reporting: [
+ `Daily bot analytics, and each sale: agent, page, price ${cite(3, 4)}.`,
+ `Each sale in your operator's publisher console, with totals and a daily CSV. No bot-traffic report ${cite(26)}.`,
+ ],
+ contract: [
+ `A license between you and each buyer; TollBit isn't a party ${cite(5)}. New York law ${cite(6)}. No dispute call.`,
+ `Your agreement with your Exchange operator. Your terms go into each offer the Exchange signs ${cite(26, 27)}. Disputes: see About FORA.`,
+ ],
+ status: [
+ `${statusTag('live')} A publisher reports revenue ${cite(36)}. No TollBit page names a big AI company as a buyer.`,
+ `${statusTag('live')} ${SEE_ABOUT}`,
+ ],
+ dns: [`A TXT record, and an NS record that hands a subdomain to TollBit ${cite(7)}.`, `No record to add ${cite(26)}.`],
+ cdn: [
+ `One forwarding rule for 69 AI user agents ${cite(8)}. Guides for 12 platforms ${cite(9)}.`,
+ 'A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it.',
+ ],
+ firewall: [
+ `An allow rule for TollBit's fetcher in every layer ${cite(7)}.`,
+ `On most CDNs they run first, so they must let signed requests and your two licensing files through. Keep them: the edge function knows AI agents mainly by the name they send ${cite(26, 28)}.`,
+ ],
+ site: [
+ `No change. TollBit fetches, cleans and serves the page. Your HTTP logs, readers' requests included, go to TollBit ${cite(1, 4)}.`,
+ `Serve one file, fora.json, from your site. The operator imports your pages from your sitemap ${cite(26)}.`,
+ ],
+ search: [
+ `Googlebot and Bingbot aren't on TollBit's list; they reach your site as today ${cite(8)}.`,
+ `Googlebot, Bingbot and Applebot always pass ${cite(28)}. See Search traffic, below.`,
+ ],
+ upkeep: [
+ `On most platforms, update the bot list by hand each quarter ${cite(10)}.`,
+ `Change your Exchanges by editing your FORA file, with nothing to redeploy ${cite(29)}.`,
+ ],
+ leaving: [`No offboarding page. You can end the terms only with no active license ${cite(5)}.`, FORA_CELLS.leaving],
+});
+
+const SHORT_ANSWER = [
+ { title: 'TollBit catches the bots that never asked.', text: 'Your CDN spots AI bots by the name they send and hands them to TollBit, which charges per page at your rate.' },
+ { title: 'FORA serves the agents that do ask.', text: 'An agent signs each request, buys under a signed offer, and fetches with a signed link, which your CDN checks. You price by use, country, buyer type and unit.' },
+ { status: 'design' as const, title: 'TollBit\'s rates behind a FORA Broker.', text: 'A Broker would call TollBit with each agent\'s own TollBit account and show TollBit\'s rates beside your FORA offers.' },
+];
+
+const PAID_STEPS = [
+ { title: 'You set rates per license, per 1,000 pages.', text: `Summarization covers "a summary, grounding, or citation with a single use license". Full Display lets a buyer "display the complete text of an article once". Custom is for a partner you have a deal with. Rates can differ by bot, page, keyword, time and directory (${a(T.settingRates, 'Setting rates')}).` },
+ { title: 'Buyers find you through TollBit and buy a pass for one URL.', text: `One API key searches TollBit's index, which covers sites "across the web" and flags TollBit's own. It shows each URL's licenses and prices (${a(T.licensedSearch, 'Licensed search')}, ${a(T.rates, 'Rates')}).` },
+ { title: 'The pass is short-lived.', text: `TollBit calls it a token: "Tokens expire 5 minutes after issuance." Each works once and names the buyer's agent, the license type and the most the buyer will pay (${a(T.tokens, 'Tokens')}).` },
+ { title: 'TollBit delivers the page.', text: `With a pass, TollBit fetches your page from your site, strips what you exclude, and returns Markdown or HTML (${a(T.security, 'Security')}; ${a(T.overview, 'Platform overview')}, §3.5).` },
+ { title: 'Billing waits for delivery.', text: `Nobody is billed "until the token is actually accepted and a 200 OK response is delivered" (${a(T.overview, 'Platform overview')}, §5.1).` },
+ { title: 'Your rate is your net.', text: `The buyer pays your rate plus "a small transaction fee on top of the rates you set" (${a(T.settingRates, 'Setting rates')}). TollBit doesn't publish the fee's size. You're paid through Stripe early each month, in US dollars (${a(T.overview, 'Platform overview')}, §1.4; ${a(T.tokens, 'Tokens')}).` },
+];
+
+const KEY_FACTS = [
+ { value: '1,000 pages', text: `The unit you set each rate in, per license type ${cite(3)}` },
+ { value: '5 minutes', text: `How long a buyer's pass for one URL lasts. It works once ${cite(2)}` },
+ { value: 'Nearly 20%', text: `Of TollBit's nearly 7,000 sites had earned money by April 2026. The CEO's figure, unaudited ${cite(37)}` },
+ { value: '37 million', text: `"content transactions" TollBit handled in Q2 2025, by its own count. It doesn't say how many were paid ${cite(13)}` },
+];
+
+const SETUP_STEPS = [
+ { title: 'Hand TollBit a subdomain.', text: `A TXT record proves you own the domain. An NS record delegates tollbit.news.example.com to TollBit's nameservers, so TollBit answers for that host under your name (${a(T.verifying, 'Verifying a property')}). TollBit's paywall for bots runs there, as your "Agent Site".` },
+ { title: 'Let TollBit\'s fetcher through.', text: `TollBit pulls your pages from your public site, through your CDN, and reads your sitemap from robots.txt when you add the site. The fetcher sends tollbot/1.0 from two ${a(T.staticIps, 'published addresses')}. Every firewall, rate limit and bot shield in front of your origin has to let it in.` },
+ { title: 'Stream your logs.', text: `The Platform overview requires them: "Every site that onboards to TollBit is required to send us their HTTP logs" (${a(T.overview, 'Platform overview')}, §1.3). Your CDN streams them with a secret key, or TollBit reads a storage bucket, which "takes up to 24 hours" to verify (${a(T.architecture, 'Platform architecture')}). TollBit's Cloudflare guide says the paywall works without them (${a(T.cloudflare, 'Cloudflare')}).` },
+ { title: 'Add one forwarding rule at your CDN.', text: `It tests the User-Agent header, the name a bot sends, against 69 AI user agents (${a(T.cloudflare, 'Cloudflare')}). On Cloudflare and Fastly the rule proxies the request, so the bot gets TollBit's answer at your URL. On CloudFront it switches the origin. On Vercel, Imperva, Google Cloud and Azure it redirects, and TollBit advises "a 302 (temporary) redirect" (${a(T.other, 'Other')}). TollBit has guides for 12 platforms (${a(T.integrations, 'Integrations')}).` },
+ { title: 'Decide what each bot gets.', text: `Your copy of the list decides which bots are forwarded at all. On Fastly, DataDome and Netacea you can pick agents one by one in a console instead. In TollBit's dashboard you "define which agents are allowed in, which are blocked, and which are subject to your paywall" (${a(T.configure, 'Configure Agent Site')}). Open Access serves bots or paths you choose a cached copy for free (${a(T.cache, 'Content cache')}). By default, any other forwarded bot without a pass gets a short message with HTTP 402, "payment required", and no price in it (${a(T.defaults, 'Default settings')}).` },
+];
+
+const CAUTIONS = [
+ { title: 'A blocked fetcher breaks the paywall.', text: `"If our requests are blocked, challenged, or rate-limited, your Agent Site will not work correctly" (${a(T.verifying, 'Verifying a property')}).` },
+ { title: 'Readers\' requests change too.', text: `On the recommended CloudFront setup, "Your regular origin will receive requests with its own domain as the Host rather than your public domain" (${a(T.aws, 'AWS')}).` },
+ { title: 'No fallback, even when you leave.', text: `One CloudFront setup "cannot fall back to your origin" when the Agent Site is down, so visitors get an error (${a(T.aws, 'AWS')}). TollBit's docs have no offboarding page; see "Plan the exit", below.` },
+ { title: 'Bots that hide their name get through.', text: `"We primarily focus on the big, self-identified bots" (${a(T.botManagement, 'Bot management')}). A bot that isn't on the list, or sends a browser's name, reaches your origin.` },
+ { title: 'The bot list goes stale.', text: `TollBit updates it "every quarter", and "publishers would then manually update their edge configurations" on most platforms (${a(T.botManagement, 'Bot management')}).` },
+];
+
+const AHEAD = [
+ { title: 'A buyer integrates once.', text: `One account, one card and one search reach every TollBit site that shows that buyer a rate (${a(T.devOverview, 'Developer overview')}). A FORA agent signs with one identity everywhere, but opens an account at each Exchange it buys from (${a('/getting-started/what-is-fora/', 'What is FORA?')}).` },
+ { title: 'It runs on more of your platforms.', text: `TollBit has setup guides for 12 platforms: CDNs, clouds, hosts and bot-security vendors. On Arc XP, WordPress VIP, DataDome and Netacea, forwarding bots is a setting in that vendor's console (${a(T.integrations, 'Integrations')}). FORA's publisher console sets up two networks, Cloudflare and AWS CloudFront (${a('/getting-started/publisher-onboarding/', 'Publisher onboarding')}).` },
+ { title: 'You see the bots before any sale.', text: `TollBit's dashboard shows scrapes, visits and referrals by agent, from your logs (${a(T.analytics, 'Enable analytics')}). FORA Server records transactions, not bot traffic or searches. It's open source, so an operator can add logs of Broker queries and Exchange offers to see what agents look for.` },
+ { title: 'It prepares content for buyers.', text: `TollBit converts pages to Markdown, holds back wire copy and embargoed articles, and tells buyers about new pages by webhook (${a(T.overview, 'Platform overview')}, §3). FORA leaves delivery to your CDN by design, and has no change feed to agents.` },
+ { title: 'Its license carries a warranty and an indemnity.', text: `FORA cannot state either as a term. Its obligations are duties of the agent, so a warranty fits only as prose in a license document a term points to (${a('/protocol/licensing-terms/', 'Licensing terms')}).` },
+];
+
+const COMPARE = compareRows([
+ [`Nowhere on your site. A forwarded bot gets a 402 by default; your rates live in TollBit's dashboard ${cite(3, 21)}.`, `Your fora.json names the Exchanges that sell your content, and you set terms with each ${cite(27)}.`],
+ [`TollBit's search, which covers sites across the web and flags its own network ${cite(11)}. How the index is built isn't documented.`, `From your file and your Exchange, or through a Broker ${cite(27, 31)}. No index spans the network.`],
+ [`Bots: by user agent, from a list of 69 ${cite(8)}. Buyers: a TollBit account, bound into each pass, which only TollBit can check ${cite(1, 2, 4)}.`, `A signature on each request, checked against the buyer's published key ${cite(32)}. The edge also matches the names bots send ${cite(28)}.`],
+ [`A pass for one URL, five minutes, one use, checked by TollBit alone ${cite(2, 4)}.`, `A signed link that expires and can be bound to the agent's key. Any edge with the Exchange's public key can check it ${cite(27, 33)}.`],
+ [`You: per 1,000 pages, per license type, by bot, page, keyword, time and directory. US dollars ${cite(2, 3)}.`, `You: free, per unit (pages, text tokens, seconds or your own) or flat, limited by use, country and buyer type, with caps. A currency per price ${cite(27, 30)}.`],
+ [`Through Stripe, monthly. You keep your full rate; the buyer pays an unpublished fee on top ${cite(1, 3)}.`, FORA_CELLS.money],
+ [`Daily bot analytics, and each sale: agent, page, price ${cite(3, 4)}.`, `Each sale, in the publisher console your Exchange operator runs ${cite(26, 27)}. No protocol call returns your sales.`],
+ [`No dispute call, and no charge without a delivered page ${cite(1)}. Then New York courts, or arbitration with TollBit ${cite(5, 6)}.`, FORA_CELLS.disputes],
+]);
+
+const BOTH_STEPS = [
+ { title: 'FORA\'s buyers skip TollBit\'s rule.', text: `So do requests for your FORA file. TollBit's rule looks for the link's signature and expiry (${a('/components/edge-function/signed-url-verification/', 'Signed URL verification')}). FORA's edge function then checks the link and serves the page from your origin.` },
+ { title: 'TollBit\'s own fetcher goes to your origin.', text: `FORA's edge function refuses user agents with a word ending in "bot" on the paths you license, and tollbot/1.0 is one. Add it to the edge function's allow list, beside your search crawlers (FORA Server's ${a(T.edgeConfig, 'edge configuration')}).` },
+ { title: 'Other AI bots get FORA\'s refusal or TollBit\'s paywall,', text: 'path by path.' },
+ { title: 'Readers go to your origin.', text: '' },
+];
+
+const TODO = [
+ { title: 'Ask what a buyer pays.', text: 'You keep your full rate, and TollBit\'s fee on top isn\'t published. Ask for the total a buyer pays for a page at your rate. FORA itself is free, open-source software.' },
+ { title: 'Read the license you accept.', text: `Activating rates accepts TollBit's standard license, warranty included (${a(T.settingRates, 'Setting rates')}). Send the points below to legal.` },
+ { title: 'Count what you hand over.', text: 'A subdomain under your name, and your HTTP logs, with your readers\' requests in them. On most platforms your engineers also update the bot list by hand each quarter.' },
+ { title: 'Check your rule order.', text: 'Let TollBit\'s fetcher through, and keep its rule off FORA links.' },
+ { title: 'Plan the exit.', text: 'Remove the forwarding rule before the DNS records, or setups without a fallback show visitors errors.' },
+ { title: 'Ask about Web Bot Auth.', text: `TollBit logs the signature headers that some AI agents send with each request (${a(T.cloudflare, 'Cloudflare')}). Ask whether it verifies them.` },
+ { title: 'Sell to agents as well.', text: `Name your FORA Exchanges in fora.json, with terms TollBit's rate card has no field for: a price by country or buyer type, or per text token (${a(T.rates, 'Rates')}).` },
+];
+
+const LEGAL = [
+ { title: 'TollBit isn\'t a party to the license.', text: `The license is a PDF contract between you and each buyer: "TollBit is not a party" (${a(T.terms, 'Publisher Terms')}).` },
+ { title: 'You give a warranty and an indemnity.', text: `You warrant that you have "all rights necessary to provide the Site Content". You indemnify the buyer against third-party claims that the content infringes a US copyright or trade secret. The license bars training, and passing content on without "express written consent". New York law (${a(T.license, 'standard license')}, §1.3, §6.2, §8.1, §9.4).` },
+ { title: 'Disputes.', text: `TollBit has no dispute call. Disputes with a buyer go to the courts of New York; disputes with TollBit go to arbitration (${a(T.terms, 'Publisher Terms')}).` },
+ { title: 'Your logs carry readers\' data.', text: `They cover "both bot and human requests". For sites that joined from Q4 2025 they include IP addresses, after TollBit revised its Data Processing Agreement (${a(T.overview, 'Platform overview')}, §1.3).` },
+ { title: 'Exit waits for active licenses.', text: `You can end the Publisher Terms only "if you are not a party to an active Content License Agreement" (${a(T.terms, 'Publisher Terms')}).` },
+ { title: 'Versions.', text: 'Publisher Terms updated October 29, 2025; standard license "Last Updated: September 23, 2024". TollBit can change both.' },
+];
+
+// The SourceList, numbered in order of first citation: an entry's position,
+// counted across the groups, is the N in cite(N).
+const SOURCES = [
+ {
+ name: 'TollBit',
+ items: [
+ { title: 'Platform overview', publisher: 'TollBit', href: T.overview, checked: '2026-11-14' },
+ { title: 'Tokens', publisher: 'TollBit docs', href: T.tokens, checked: '2026-11-14' },
+ { title: 'Setting rates', publisher: 'TollBit docs', href: T.settingRates, checked: '2026-11-15' },
+ { title: 'Security', publisher: 'TollBit docs', href: T.security, checked: '2026-11-15' },
+ { title: 'Publisher Terms of Service', publisher: 'TollBit', href: T.terms, checked: '2026-11-14' },
+ { title: 'Content License Agreement (standard license)', publisher: 'TollBit', href: T.license, checked: '2026-11-14' },
+ { title: 'Verifying a property', publisher: 'TollBit docs', href: T.verifying, checked: '2026-11-15' },
+ { title: 'Cloudflare', publisher: 'TollBit docs', href: T.cloudflare, checked: '2026-11-15' },
+ { title: 'Integrations', publisher: 'TollBit docs', href: T.integrations, checked: '2026-11-15' },
+ { title: 'Bot management', publisher: 'TollBit docs', href: T.botManagement, checked: '2026-11-15' },
+ { title: 'Licensed search', publisher: 'TollBit docs', href: T.licensedSearch, checked: '2026-11-14' },
+ { title: 'Rates', publisher: 'TollBit docs', href: T.rates, checked: '2026-11-14' },
+ { title: 'TollBit and Akamai partnership', publisher: 'TollBit blog', href: T.akamai, checked: '2026-11-14' },
+ { title: 'Announcing our Series A', publisher: 'TollBit blog', href: T.seriesA, checked: '2026-11-14' },
+ { title: 'TollBit homepage', publisher: 'TollBit', href: T.home, checked: '2026-11-14' },
+ { title: 'Static IPs', publisher: 'TollBit', href: T.staticIps, checked: '2026-11-14' },
+ { title: 'Platform architecture', publisher: 'TollBit docs', href: T.architecture, checked: '2026-11-15' },
+ { title: 'Other platforms', publisher: 'TollBit docs', href: T.other, checked: '2026-11-15' },
+ { title: 'Configure Agent Site', publisher: 'TollBit docs', href: T.configure, checked: '2026-11-15' },
+ { title: 'Content cache', publisher: 'TollBit docs', href: T.cache, checked: '2026-11-15' },
+ { title: 'Default settings', publisher: 'TollBit docs', href: T.defaults, checked: '2026-11-15' },
+ { title: 'AWS (S3, CloudFront, ALB)', publisher: 'TollBit docs', href: T.aws, checked: '2026-11-15' },
+ { title: 'Developer overview', publisher: 'TollBit docs', href: T.devOverview, checked: '2026-11-14' },
+ { title: 'Enable analytics', publisher: 'TollBit docs', href: T.analytics, checked: '2026-11-15' },
+ { title: 'Content (API)', publisher: 'TollBit docs', href: T.content, checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'FORA',
+ items: [
+ { title: 'Publisher onboarding', publisher: 'FORA documentation', href: '/getting-started/publisher-onboarding/', checked: '2026-11-15' },
+ { title: 'What is FORA?', publisher: 'FORA documentation', href: '/getting-started/what-is-fora/', checked: '2026-11-15' },
+ { title: 'Bot detection', publisher: 'FORA documentation', href: '/components/edge-function/bot-detection/', checked: '2026-11-15' },
+ { title: 'Edge function', publisher: 'FORA documentation', href: '/components/edge-function/overview/#forajson-and-rsltxt-pass-through', checked: '2026-11-15' },
+ { title: 'Licensing terms', publisher: 'FORA documentation', href: '/protocol/licensing-terms/', checked: '2026-11-15' },
+ { title: 'Broker', publisher: 'FORA documentation', href: '/components/broker/overview/', checked: '2026-11-15' },
+ { title: 'Authentication', publisher: 'FORA documentation', href: '/protocol/authentication/', checked: '2026-11-15' },
+ { title: 'Composition', publisher: 'FORA documentation', href: '/components/edge-function/composition/', checked: '2026-11-15' },
+ { title: 'Signed URL verification', publisher: 'FORA documentation', href: '/components/edge-function/signed-url-verification/', checked: '2026-11-15' },
+ { title: 'FORA Server edge configuration', publisher: 'FORA-Protocol on GitHub', href: T.edgeConfig, checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Press, filings and others',
+ items: [
+ { title: 'TNL Mediagene announces early success in AI content licensing', publisher: 'PR Newswire', href: T.tnl, checked: '2026-11-14' },
+ { title: 'The Washington Post\'s Arc XP adds TollBit', publisher: 'Digiday', href: T.digiday, checked: '2026-11-14' },
+ ],
+ },
+];
+---
+
+
+ Where TollBit is ahead
+ Run both
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
TollBit's rule forwards only the AI bots on its list. Googlebot and Bingbot aren't on it, so they reach your site as today.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
On one site
+
+
+
+
+
+
Behind a FORA Broker
+
+
Doesn't fit
+
Settling a FORA sale through TollBit. TollBit's API bills the calling account at TollBit's own rates, even for usage the buyer reports itself. It has no call that bills a price another Exchange set (${a(T.content, 'Content')}).`} />
+
+
+
+
+
+
+
+
+
+
+
+
+
Sources
+
Sources are checked on the date of publication.
+
+
+
+
+
+
+ What is FORA?
+ Run your own marketplace
+ All content marketplaces
+ Licensing terms
+
+
+
+
diff --git a/website/src/pages/resources/index.astro b/website/src/pages/resources/index.astro
index 956c1245..67c8e04b 100644
--- a/website/src/pages/resources/index.astro
+++ b/website/src/pages/resources/index.astro
@@ -1,11 +1,17 @@
---
-// /resources/: one card per topic, from src/data/resources.ts.
+// /resources/: one card per topic, from src/data/resources.ts. Topics without
+// a section first, then one band per section, with its heading and intro.
import LandingLayout from '../../layouts/LandingLayout.astro';
import AudienceHero from '../../components/landing/AudienceHero.astro';
import Band from '../../components/landing/Band.astro';
import ResourceCards from '../../components/landing/ResourceCards.astro';
import ClosingCta from '../../components/landing/ClosingCta.astro';
-import { RESOURCES } from '../../data/resources';
+import { RESOURCES, SECTIONS } from '../../data/resources';
+
+const loose = RESOURCES.filter((r) => !r.section);
+const sections = SECTIONS
+ .map((s) => ({ ...s, items: RESOURCES.filter((r) => r.section === s.name) }))
+ .filter((s) => s.items.length > 0);
---
-
+
+ {sections.map((s) => (
+
+
+
+ ))}
+
`${text}`;
+
+// The standards' own pages, linked from the table's first column.
+const S = {
+ robots: 'https://www.rfc-editor.org/rfc/rfc9309',
+ aipref: 'https://datatracker.ietf.org/wg/aipref/about/',
+ tdmrep: 'https://www.w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510/',
+ rsl: 'https://rslstandard.org/rsl',
+ comp: 'https://github.com/IABTechLab/CoMP',
+ llms: 'https://llmstxt.org/',
+ wba: 'https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/',
+ mcp: 'https://modelcontextprotocol.io/specification/2026-07-28',
+ c2pa: 'https://c2pa.org/',
+ x402: 'https://www.x402.org/',
+ mpp: 'https://mpp.dev/',
+ spur: 'https://github.com/SPUR-Coalition/telemetry',
+ socw: 'https://m4ow.uk/socw/',
+};
+
+const STANDARDS = [
+ { name: 'robots.txt', href: S.robots, job: 'Declare terms: allow or block, per crawler', status: `IETF standard, RFC 9309 (2022). Its rules "are not a form of access authorization" ${cite(1)}`, users: `On sites using TollBit, 30% of AI bot scrapes in Q4 2025 ignored it (TollBit's own data) ${cite(2)}` },
+ { name: 'AIPREF', href: S.aipref, job: 'Declare terms: a preference about AI training and AI use', status: `IETF working-group draft -08 (September 2026), without group consensus yet; the robots.txt training token is an individual draft ${cite(4, 5)}`, users: `Anthropic has recognized the training token since October 30, 2026; Microsoft from February 1, 2027; Google intends to in early 2027; OpenAI "will honor" it ${cite(6, 7, 8, 9)}` },
+ { name: 'TDMRep', href: S.tdmrep, job: 'Declare terms: reserve text-and-data-mining rights', status: `W3C Community Group final report (2024), "not a W3C Standard" ${cite(11)}`, users: `More than 50 adopters on the group's own list, among them Hachette Livre, Elsevier, Springer Nature, Wiley and Radio France ${cite(12)}` },
+ { name: 'RSL', href: S.rsl, job: 'Declare terms: state license terms and prices; it also specifies a license server (OLP)', status: `RSL 1.0, a Recommendation of RSL's Technical Steering Committee, December 2025 ${cite(14, 15)}`, users: `More than 3,000 supporters, says ILC; one AI company licensed through ILC, Yahoo Scout ${cite(16)}` },
+ { name: 'IAB Tech Lab CoMP', href: S.comp, job: 'Declare terms: describe content, its price and where its license is, for a marketplace API', status: `IAB Tech Lab, final V1, April 2026 ${cite(21)}`, users: `FORA carries CoMP: its fields travel whole on each FORA offer ${cite(22)}` },
+ { name: 'llms.txt', href: S.llms, job: 'Help discovery: a curated index for AI readers', status: `A proposal by Jeremy Howard, v2 August 2026; no standards body ${cite(31)}`, users: `"thousands of sites publish an llms.txt file", by its author's count ${cite(31)}` },
+ { name: 'Web Bot Auth', href: S.wba, job: 'Identify the caller: a signature on each agent request', status: `IETF working-group draft, October 2026 ${cite(32)}`, users: `ChatGPT Work's cloud browser signs with it ${cite(33)}. Cloudflare verifies, and FORA agents sign, under two different earlier drafts ${cite(23, 34)}` },
+ { name: 'MCP', href: S.mcp, job: 'Connect: how an agent calls a tool or a seller', status: `The Agentic AI Foundation, under the Linux Foundation; revision of July 28, 2026 ${cite(35, 36)}`, users: `Cashmere, AskNews and Newstex sell content through MCP servers; FORA's Identity Service is one ${cite(22, 37, 38, 39)}` },
+ { name: 'C2PA', href: S.c2pa, job: 'Prove origin: who made this, and has it changed', status: `C2PA 2.5 (October 2026), a Linux Foundation project; ISO 22144 at committee draft ${cite(41, 42, 43)}`, users: `Steering-committee members include Adobe, BBC, Google, Meta, Microsoft and OpenAI ${cite(44)}` },
+ { name: 'FORA', fora: true, job: 'Declare terms, transact and report: a signed offer per term, the buyer\'s signed acceptance, a signed link, and the buyer\'s usage report', status: `The open protocol this site describes. Apache-2.0, release v1.2.1, with FORA Server, an open-source implementation ${cite(22, 24)}`, users: 'Any company can run its own marketplace on it. See About FORA' },
+ { name: 'x402', href: S.x402, job: 'Settle, which moves money: payment over HTTP 402', status: `x402 Foundation, under the Linux Foundation; 40 members by July 2026, Visa, Mastercard and American Express among them ${cite(48)}`, users: `In AWS WAF on CloudFront since June 2026; in Cloudflare's Monetization Gateway, a closed beta since September 30, 2026 ${cite(49, 50)}` },
+ { name: 'MPP', href: S.mpp, job: 'Settle, which moves money: payment over HTTP 402, per charge, session or subscription', status: `Co-authored by Tempo and Stripe; its core scheme is an individual Internet-Draft ${cite(52, 53)}`, users: `Cloudflare's Agents SDK names it as one of its two payment protocols; AWS called MPP support "coming soon" in June 2026 ${cite(49, 54)}` },
+ { name: 'SPUR Content Telemetry', href: S.spur, job: 'Report: what an AI system did with content after the fetch', status: `SPUR Coalition, 1.0, September 2026 ${cite(55)}`, users: `AskNews says it weights its publisher pool by its events ${cite(56)}` },
+];
+
+const KEY_FACTS = [
+ { value: '30%', text: `of AI bot scrapes ignored robots.txt on sites using TollBit, in Q4 2025, by TollBit's own data ${cite(2)}` },
+ { value: '3,000+', text: `RSL supporters, by ILC's count ${cite(16)}` },
+ { value: '4', text: `AI companies committed to honor AIPREF's training refusal ${cite(6, 7, 8, 9)}` },
+ { value: '1', text: `AI company paying under an RSL-based license: Yahoo Scout ${cite(16)}` },
+];
+
+const STANDING = [
+ { title: 'Blocking is a request, and a growing share of AI bot scrapes ignore it.', text: `On sites using TollBit, the share that bypassed robots.txt rose from 3.3% in Q4 2024 to 12.9% in Q1 2025, then to 30% ${cite(2, 10)}. AIPREF says so of itself: a receiver "has a choice whether to follow those preferences" ${cite(4)}.` },
+ { title: 'Declaring has thousands of supporters, four committed AI companies and one buyer.', text: `The four commitments promise to honor a refusal, and carry no payment. Yahoo Scout pays under ILC's blanket license, announced on November 12, 2026 ${cite(16)}. No AI company is known to pay under a publisher's own RSL terms.` },
+ { title: 'Transacting and settling are available in a few places.', text: `FORA transacts on every Exchange that runs it. x402 settles in AWS WAF and Cloudflare's closed beta, MPP in Cloudflare's Agents SDK. Supertab sells an RSL license server, and no AI company is named as buying through it ${cite(25, 49, 50, 54, 57)}.` },
+];
+
+const TODO = [
+ { title: 'Write down what training, grounding and display are each worth to you.', text: 'Grounding means an AI answer uses your page as its source. None of these standards can tell you that.' },
+ { title: 'Generate your rules.', text: `The ${a('/resources/ai-crawlers/#generator', 'AI rules generator')} writes robots.txt groups for AI crawlers, AIPREF's training refusal, the line that attaches the search-only contract, and TDMRep's header and tag.` },
+ { title: 'Adopt the search-only contract, with your legal team.', text: `Set your fee in your site's terms and point robots.txt at the contract: ${a('/getting-started/search-only-contract/', 'the steps')}.` },
+ { title: 'Publish RSL if you have license terms to state.', text: `Behind FORA's edge function, keep it at /rsl.txt, which the edge passes through to every client ${cite(27)}.` },
+ { title: 'See what an agent would be offered.', text: `Paste one of your pages on ${a('/publishers/', 'For Publishers')}. No account needed.` },
+];
+
+const LEGAL = [
+ { title: 'Formed by conduct.', text: `Under the contract, "agreement is formed through conduct, simply by accessing" the site ${cite(63)}.` },
+ { title: 'Law.', text: `Under the law of England and Wales, the fee is "a contractual debt which becomes immediately due" ${cite(63)}. Whether it holds where you publish is a question for your lawyer.` },
+];
+
+const DIFFER = [
+ { title: 'A price and a credit together.', text: `In RSL, a license asks for money or for credit, not both. Its schema (RSL 1.0, Appendix A) allows one payment element with one type, and attribution is one of the types ${cite(14)}. CoMP keeps citation in a field of its own, beside the price ${cite(20)}. A FORA term can charge per access and require credit ${cite(28)}.` },
+ { title: 'Caps.', text: `FORA states a cap as a metric, a limit and a window: ten seats a month, say. The buyer agrees to it; the Exchange doesn't meter it ${cite(28)}. RSL's schema has no cap element (Appendix A) ${cite(14)}. CoMP has a yes-or-no field that says a crawl limit exists ${cite(20)}.` },
+ { title: 'A menu for one asset.', text: `A FORA resource carries up to 32 terms, and each one a buyer may see is its own signed offer ${cite(28)}. RSL allows several licenses for the same content, but tells processors to "evaluate all applicable licensing terms together" ${cite(14)}. A CoMP response carries one package with one price ${cite(20)}.` },
+ { title: 'Saying what you want first.', text: `CoMP lets an AI system state its intended use ${cite(20)}. FORA lets a buyer state the uses, places and kind of user it accepts, and an Exchange may return only the offers that fit ${cite(28)}.` },
+];
+
+const EXPLORER = [
+ { title: 'Price and credit.', text: 'Pick "AI answers, pay per crawl": RSL loses the credit, CoMP keeps it.' },
+ { title: 'Caps and reports.', text: 'Pick "Annual AI access deal": the cap is in neither file.' },
+ { title: 'A shared license.', text: 'Pick "Collective blanket license": neither RSL nor CoMP can pin the document\'s version.' },
+];
+
+const ENGINEERS = [
+ { title: 'Pairs that compose.', text: `RSL adds a License: line to robots.txt; AIPREF's training token is a robots.txt group ${cite(5, 14)}. x402's "exact" flows "map directly onto MPP's charge intent", and MPP can charge for MCP tool calls ${cite(52)}. MCP defines no price or license: each seller adds its own ${cite(35)}.` },
+];
+
+const FAQ = [
+ { q: 'Do I have to choose between RSL and FORA?', a: 'No. FORA doesn\'t replace RSL or CoMP. RSL publishes your terms in a file anyone can read. FORA sells under the terms you set in the publisher console, one signed offer at a time.' },
+ { q: 'Is TDMRep enough to reserve AI training in the EU?', a: `TDMRep is a machine-readable form of the reservation the EU's copyright directive recognizes. In the TDMRep report's summary of Article 4, mining is allowed unless "expressly reserved by their rightsholders in an appropriate manner, such as machine-readable means" ${cite(11)}. Whether yours meets the test is a question for your lawyer.` },
+ { q: 'What isn\'t on the map?', a: `IPTC's photo metadata has a data-mining property inside the image file ${cite(60)}. ODRL is the policy language TDMRep uses ${cite(11, 61)}. The European Commission's consultation lists Liccium's TDM·AI among opt-out protocols. The Commission hasn't published its list of generally agreed ones ${cite(62)}.` },
+];
+
+// The SourceList, numbered in order of first citation: an entry's position,
+// counted across the groups, is the N in cite(N).
+const SOURCES = [
+ {
+ name: 'robots.txt and AIPREF',
+ items: [
+ { title: 'RFC 9309: Robots Exclusion Protocol', publisher: 'IETF', href: S.robots, checked: '2026-11-14' },
+ { title: 'State of the Bots, Q3–Q4 2025', publisher: 'TollBit', href: 'https://tollbit.com/state-of-the-bots/q3-q4-2025/', checked: '2026-11-14' },
+ { title: 'AI Preferences (aipref) working group', publisher: 'IETF', href: S.aipref, checked: '2026-11-15' },
+ { title: 'A Vocabulary For Expressing AI Usage Preferences, draft -08', publisher: 'IETF AIPREF working group', href: 'https://datatracker.ietf.org/doc/draft-ietf-aipref-vocab/', checked: '2026-11-15' },
+ { title: 'Machine-Readable Training Preference Signal', publisher: 'IETF, individual Internet-Draft', href: 'https://datatracker.ietf.org/doc/draft-kelley-aipref-training-preference-signal/', checked: '2026-11-15' },
+ { title: 'robots.txt controls', publisher: 'Anthropic', where: 'Anthropic help center, article 8896518 (no link)', checked: '2026-11-15' },
+ { title: 'Your content, your choice: clearer preferences for training and grounding', publisher: 'Microsoft, Bing blog', href: 'https://blogs.bing.com/search/2026/10/your-content-your-choice-clearer-preferences-for-training-and-grounding/', checked: '2026-11-15' },
+ { title: 'Google\'s common crawlers', publisher: 'Google for Developers', href: 'https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers', checked: '2026-11-15' },
+ { title: 'Helping websites express AI training preferences', publisher: 'OpenAI', href: 'https://openai.com/index/helping-websites-express-ai-training-preferences/', checked: '2026-11-14' },
+ { title: 'State of the Bots, Q1 2025', publisher: 'TollBit', href: 'https://tollbit.com/state-of-the-bots/q1-2025/', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'TDMRep',
+ items: [
+ { title: 'TDM Reservation Protocol (TDMRep), Final Community Group Report', publisher: 'W3C TDMRep Community Group', href: S.tdmrep, checked: '2026-11-14' },
+ { title: 'TDMRep adopters', publisher: 'W3C TDMRep Community Group, on GitHub', href: 'https://github.com/w3c/tdm-reservation-protocol/blob/main/docs/adopters.md', checked: '2026-11-14' },
+ { title: 'Text and Data Mining Reservation Protocol Community Group', publisher: 'W3C', href: 'https://www.w3.org/community/tdmrep/', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'RSL and ILC',
+ items: [
+ { title: 'Really Simple Licensing (RSL) 1.0 specification', publisher: 'RSL Technical Steering Committee', href: S.rsl, checked: '2026-11-14' },
+ { title: 'RSL AI Licensing 1.0 now an official industry standard', publisher: 'RSL, press release', href: 'https://rslstandard.org/press/rsl-1-specification-2025', checked: '2026-11-14' },
+ { title: 'The Internet Licensing Collective launches with Yahoo Scout as first commercial partner', publisher: 'Internet Licensing Collective, press release', href: 'https://internetcollective.org/press/ilc-launch-2026', checked: '2026-11-14' },
+ { title: 'RSL quickstart', publisher: 'RSL', href: 'https://rslstandard.org/', checked: '2026-11-14' },
+ { title: 'The ILC Platform', publisher: 'Internet Licensing Collective', href: 'https://internetcollective.org/platform', checked: '2026-11-13' },
+ { title: 'ILC\'s RSL file', publisher: 'Internet Licensing Collective', href: 'https://internetcollective.org/rsl.xml', checked: '2026-11-13' },
+ ],
+ },
+ {
+ name: 'CoMP',
+ items: [
+ { title: 'CoMP 1.0: Content Metadata Marketplace Supply Specification', publisher: 'IAB Tech Lab, on GitHub', href: S.comp, checked: '2026-11-14' },
+ { title: 'CoMP: Content Monetization Protocols initiative', publisher: 'IAB Tech Lab', href: 'https://iabtechlab.com/standards/comp-content-monetization-protocols-initiative/', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'FORA',
+ items: [
+ { title: 'What Is FORA?', publisher: 'FORA documentation', href: '/getting-started/what-is-fora/', checked: '2026-11-15' },
+ { title: 'Authentication', publisher: 'FORA documentation', href: '/protocol/authentication/', checked: '2026-11-15' },
+ { title: 'FORA protocol repository', publisher: 'FORA-Protocol on GitHub', href: 'https://github.com/FORA-Protocol/protocol', checked: '2026-11-15' },
+ { title: 'Broker', publisher: 'FORA documentation', href: '/components/broker/overview/', checked: '2026-11-15' },
+ { title: 'Search-Only Contract', publisher: 'FORA documentation', href: '/getting-started/search-only-contract/', checked: '2026-11-15' },
+ { title: 'FORA Server', publisher: 'FORA-Protocol on GitHub', href: 'https://github.com/FORA-Protocol/reference-implementation', checked: '2026-11-15' },
+ { title: 'Licensing Terms', publisher: 'FORA documentation', href: '/protocol/licensing-terms/', checked: '2026-11-15' },
+ { title: 'The licensing core explorer', publisher: 'FORA', href: '/protocol/#licensing-core', checked: '2026-11-15' },
+ { title: 'Publisher Onboarding', publisher: 'FORA documentation', href: '/getting-started/publisher-onboarding/', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'llms.txt',
+ items: [
+ { title: 'The /llms.txt file', publisher: 'Jeremy Howard, llmstxt.org', href: S.llms, checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Web Bot Auth',
+ items: [
+ { title: 'HTTP Message Signatures for automated traffic (draft-ietf-webbotauth-httpsig-protocol)', publisher: 'IETF webbotauth working group', href: S.wba, checked: '2026-11-14' },
+ { title: 'ChatGPT Work\'s cloud browser allowlisting', publisher: 'OpenAI Help Center', href: 'https://help.openai.com/en/articles/11845367', checked: '2026-11-14' },
+ { title: 'Web Bot Auth', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'MCP',
+ items: [
+ { title: 'Model Context Protocol specification, revision 2026-07-28', publisher: 'Model Context Protocol', href: S.mcp, checked: '2026-11-15' },
+ { title: 'MCP joins the Agentic AI Foundation', publisher: 'Model Context Protocol blog', href: 'https://blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation/', checked: '2026-11-15' },
+ { title: 'MCP server documentation', publisher: 'Cashmere', href: 'https://cashmere.io/docs/mcp', checked: '2026-11-14' },
+ { title: 'MCP server', publisher: 'AskNews docs', href: 'https://docs.asknews.app/en/mcp', checked: '2026-11-15' },
+ { title: 'Newstex MCP Server', publisher: 'Newstex', href: 'https://mcp.newstex.com/', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'C2PA',
+ items: [
+ { title: 'C2PA: Coalition for Content Provenance and Authenticity', publisher: 'C2PA', href: S.c2pa, checked: '2026-11-14' },
+ { title: 'C2PA Technical Specification 2.5', publisher: 'C2PA', href: 'https://spec.c2pa.org/specifications/specifications/2.5/specs/C2PA_Specification.html', checked: '2026-11-14' },
+ { title: 'About C2PA', publisher: 'C2PA', href: 'https://c2pa.org/about/', checked: '2026-11-14' },
+ { title: 'ISO/CD 22144, Authenticity of information: Content credentials', publisher: 'ISO', href: 'https://www.iso.org/standard/90726.html', checked: '2026-11-14' },
+ { title: 'Membership', publisher: 'C2PA', href: 'https://c2pa.org/membership/', checked: '2026-11-14' },
+ { title: 'C2PA founding press release', publisher: 'C2PA', href: 'https://c2pa.org/c2pa-founding-press-release/', checked: '2026-11-14' },
+ { title: 'Training and Data Mining Assertion 1.1', publisher: 'Creator Assertions Working Group', href: 'https://cawg.io/training-and-data-mining/1.1/', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Payments: x402 and MPP',
+ items: [
+ { title: 'x402', publisher: 'x402 Foundation', href: S.x402, checked: '2026-11-14' },
+ { title: 'Linux Foundation announces operational launch of x402 Foundation', publisher: 'x402 Foundation', href: 'https://x402.org/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications/', checked: '2026-11-14' },
+ { title: 'AWS WAF announces AI traffic monetization', publisher: 'AWS, What\'s New', href: 'https://aws.amazon.com/about-aws/whats-new/2026/06/aws-waf-ai-traffic-monetization/', checked: '2026-11-14' },
+ { title: 'Monetization Gateway beta: charge AI agents for consumption with HTTP 402', publisher: 'Cloudflare blog', href: 'https://blog.cloudflare.com/monetization-gateway-beta/', checked: '2026-11-14' },
+ { title: 'Machine Payments Protocol', publisher: 'MPP', href: S.mpp, checked: '2026-11-15' },
+ { title: 'Frequently asked questions', publisher: 'MPP', href: 'https://mpp.dev/faq', checked: '2026-11-15' },
+ { title: 'The "Payment" HTTP Authentication Scheme', publisher: 'IETF, individual Internet-Draft', href: 'https://datatracker.ietf.org/doc/draft-httpauth-payment/', checked: '2026-11-15' },
+ { title: 'Agentic Payments, Agents SDK', publisher: 'Cloudflare docs', href: 'https://developers.cloudflare.com/agents/tools/payments/', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'SPUR Content Telemetry',
+ items: [
+ { title: 'SPUR Content Telemetry 1.0', publisher: 'SPUR Coalition, on GitHub', href: S.spur, checked: '2026-11-14' },
+ { title: 'From Retrieval to Citation: How AskNews Makes Publisher Usage Traceable', publisher: 'AskNews blog', href: 'https://asknews.app/en/blog-articles/spur-telemetry-publisher-usage-and-revenue', checked: '2026-11-14' },
+ ],
+ },
+ {
+ name: 'Others mentioned',
+ items: [
+ { title: 'Supertab Connect', publisher: 'Supertab', href: 'https://www.supertab.co/', checked: '2026-11-13' },
+ { title: 'Daily Kos\'s RSL file', publisher: 'Daily Kos', href: 'https://www.dailykos.com/license.xml', checked: '2026-11-13' },
+ { title: 'Tokens', publisher: 'TollBit docs', href: 'https://docs.tollbit.com/docs/tokens', checked: '2026-11-14' },
+ { title: 'IPTC Photo Metadata Standard', publisher: 'IPTC', href: 'https://iptc.org/std/photometadata/specification/IPTC-PhotoMetadata', checked: '2026-11-15' },
+ { title: 'ODRL Information Model 2.2', publisher: 'W3C', href: 'https://www.w3.org/TR/odrl-model/', checked: '2026-11-15' },
+ { title: 'Stakeholder consultation on AI and copyright compliance', publisher: 'European Commission', href: 'https://digital-strategy.ec.europa.eu/en/faqs/stakeholder-consultation-ai-and-copyright-compliance', checked: '2026-11-15' },
+ ],
+ },
+ {
+ name: 'Contracts: the search-only contract',
+ items: [
+ { title: 'Search Only Terms Contract', publisher: 'Movement for an Open Web', href: S.socw, checked: '2026-11-14' },
+ ],
+ },
+];
+---
+
+
+ See the thirteen
+ Generate your rules
+
+
+
+
+
A machine-readable declaration is a request. TDMRep reserves rights that bind in the EU, and no technical layer enforces them. A declaration earns money only when a license server, an Exchange or a contract that access triggers stands behind it.
+
+
Ask your vendors. Put this to your CDN, bot-management vendor or marketplace, verbatim: "Which of these standards do you read, which do you enforce at the door, and who is paying under any of them through you today?"
+
+
+
+
+
+
+
+
+
How to read it. Each row does a different job, so the rows don't rank against each other: a road sign isn't worse than a till for not taking payment. The last column mixes kinds of adoption, and each cell says which.
+
Transacting agrees one sale; settling moves the money. RSL declares terms, and its specification describes a license server. FORA spans the terms, the transaction and the report, and leaves the money to your operator.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
license server included, carries the buyer's own signature on the terms it accepted.`} />
+
+
+
+
+
+
The rest of the page compares the specifications clause by clause. Everything above reads without it.
+
+
+
+
+
Three of the thirteen are license formats: RSL 1.0, CoMP and FORA's licensing core. All three say what you may do, who may buy, where, at what price, and what you owe afterward. TDMRep and AIPREF say only the first.
+
all to search ${cite(14)}. CoMP takes the same six names, four definitions word for word ${cite(20)}. FORA starts from RSL's use words and adds copyright uses such as reproduce and sync, 23 in all. It also accepts AIPREF's train-ai as a spelling of ai-train ${cite(28)}. RSL and FORA both scope a term by place and kind of user, and both can prohibit as well as permit ${cite(14, 28)}.`} />
+
+
+
+
+
<standard> element points at a legal text elsewhere, such as a Creative Commons license ${cite(14)}. FORA incorporates by reference too, with the document's digest beside its address, so the document can't be swapped after an offer is signed ${cite(28)}.`} />
+
+
See it clause by clause. The ${a('/protocol/#licensing-core', 'Licensing Core explorer')} shows 12 licenses, each as a FORA term, an RSL file and a CoMP package.`} />
+
+
+
+
+
+
+
+
+
<standard> takes an address with no digest (Appendix A) ${cite(14)}. TollBit's content tokens name a license type and a license ID, and TollBit signs them, not the buyer ${cite(59)}. CoMP records how a crawler plans to identify itself, which is not its assent ${cite(20)}.`} />
+
What ILC does with it. ILC, the collective that co-authored RSL, keeps the transaction out of the content path ${cite(16, 18)}. Its RSL file names no license server and points, through <standard>, at ILC's collective license ${cite(19)}. An AI company takes one blanket license, for a fee ILC doesn't publish, and reports its own use ${cite(18)}. Yahoo Scout, ILC's first licensee, pays under that contract ${cite(16)}. ${a('/resources/transparent-collective/', 'How ILC compares with other collectives →')}`} />
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Two pairs that can contradict each other. RSL states which uses are permitted; CoMP leaves uses to the license it links, so the two can disagree unseen ${cite(14, 20)}. If you publish both, check that they say the same thing. robots.txt governs fetching by crawler name and TDMRep reserves a use. The TDMRep group calls them complementary, but "this complementarity is not specified in the TDMRep document and remains subject to interpretation" ${cite(13)}.`} />
+
+
+
+
+
+
+
+
About FORA.`} />
+
+
+
+
+
+
+
+
+
+
Sources
+
+ All sources
+
+
+
Sources are checked on the date of publication.
+
+
+
+
+
+ Generate your rules
+ See your offers
+
+
+
+
+
+
diff --git a/website/src/pages/resources/transparent-collective.astro b/website/src/pages/resources/transparent-collective.astro
index a56e6e18..1a4ea864 100644
--- a/website/src/pages/resources/transparent-collective.astro
+++ b/website/src/pages/resources/transparent-collective.astro
@@ -628,7 +628,7 @@ const SOURCES = [
.scheme { padding: 1.75rem; border: 1px solid var(--lp-rule); border-radius: 12px; background: #fff; min-width: 0; }
.scheme.wide, .scheme:last-child:nth-child(even) { grid-column: 1 / -1; }
.scheme p { margin: 0; overflow-wrap: break-word; }
- .scheme .scheme-tag { font: 500 0.875rem var(--mono); letter-spacing: 0.06em; text-transform: uppercase; line-height: 1.4; color: var(--lp-link); margin-bottom: 0.625rem; }
+ .scheme .scheme-tag { font: 500 0.875rem var(--mono); letter-spacing: 0.06em; text-transform: uppercase; line-height: 1.4; color: var(--lp-label); margin-bottom: 0.625rem; }
.scheme.wide p:not(.scheme-tag), .scheme:last-child:nth-child(even) p:not(.scheme-tag) { max-width: 46rem; }
.world { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 1.25rem; align-items: start; margin-top: 2.5rem; }
.world-region { padding: 1.5rem 1.75rem; border: 1px solid var(--lp-rule); border-radius: 12px; background: #fff; min-width: 0; }
@@ -638,7 +638,7 @@ const SOURCES = [
.world-region li { display: grid; gap: 0.25rem; color: var(--lp-text); font-size: 1.0625rem; line-height: 1.6; overflow-wrap: break-word; }
.world-region b { color: var(--lp-strong); font-weight: 700; }
.world-region :global(a) { color: var(--lp-link); }
- .world-tag { font: 500 0.875rem var(--mono); letter-spacing: 0.06em; text-transform: uppercase; color: var(--lp-link); }
+ .world-tag { font: 500 0.875rem var(--mono); letter-spacing: 0.06em; text-transform: uppercase; color: var(--lp-label); }
/* The same look as PointList, for lists whose text carries links. */
.points { list-style: none; margin: 2rem 0 0; padding: 0; display: grid; gap: 1.25rem; max-width: 44rem; }
.points li { display: grid; grid-template-columns: auto 1fr; gap: 0.75rem; color: var(--lp-text); font-size: 1.125rem; line-height: 1.7; }
diff --git a/website/src/styles/landing.css b/website/src/styles/landing.css
index 77171dda..149e434a 100644
--- a/website/src/styles/landing.css
+++ b/website/src/styles/landing.css
@@ -191,6 +191,54 @@
outline-offset: 5px;
}
+/* ========= RESOURCE-PAGE ATOMS =========
+ Inline pieces that also land inside HTML strings (a GlanceCard cell, a
+ table cell, a step), so their styles can't be scoped to one component.
+ The markup comes from src/lib/resource-markup.ts. Both read the Band's
+ --lp-* variables, so they work on a black, near or light band. */
+
+/* Status tag: monochrome on purpose. The states differ by fill and line, so
+ they read on every band and never compete with FORA's blue. Live is filled;
+ Beta, Closed beta and Pilot are outlined; Design and Roadmap are dashed;
+ Not public is dotted and muted. Every icon box is the same size, so no
+ pill drops below the text line. */
+.status-tag {
+ display: inline-flex;
+ align-items: center;
+ gap: 0.4rem;
+ vertical-align: middle;
+ position: relative;
+ top: -0.08em;
+ font-family: var(--mono);
+ font-size: 0.6875rem;
+ font-weight: 500;
+ line-height: 1;
+ letter-spacing: 0.08em;
+ text-transform: uppercase;
+ white-space: nowrap;
+ padding: 0.3rem 0.6rem 0.3rem 0.5rem;
+ border-radius: 999px;
+ border: 1px solid var(--lp-heading);
+ color: var(--lp-heading);
+}
+.status-tag::before { content: ''; width: 0.5rem; height: 0.5rem; border-radius: 50%; flex: none; }
+.status-tag--live { background: var(--lp-heading); color: var(--lp-bg); }
+.status-tag--live::before { background: var(--lp-bg); }
+.status-tag--beta::before,
+.status-tag--closed-beta::before { background: linear-gradient(90deg, var(--lp-heading) 50%, transparent 50%); border: 1px solid var(--lp-heading); }
+.status-tag--pilot::before { border: 1px solid var(--lp-heading); }
+.status-tag--design,
+.status-tag--roadmap { border-style: dashed; }
+.status-tag--design::before { border: 1px dashed var(--lp-heading); }
+.status-tag--roadmap::before { border-radius: 0; background: linear-gradient(var(--lp-heading), var(--lp-heading)) center / 100% 1px no-repeat, linear-gradient(var(--lp-heading), var(--lp-heading)) right center / 1px 100% no-repeat; }
+.status-tag--not-public { border-style: dotted; border-color: var(--lp-muted); color: var(--lp-text); }
+.status-tag--not-public::before { border-radius: 0; background: linear-gradient(var(--lp-muted), var(--lp-muted)) center / 100% 1px no-repeat; }
+
+/* Citation marker: "[1, 2]", each number a link to the page's SourceList. */
+.cite { white-space: nowrap; font-size: 0.8125em; color: var(--lp-muted); font-variant-numeric: tabular-nums; }
+.cite a { color: var(--lp-link); text-decoration: none; }
+.cite a:hover { text-decoration: underline; }
+
@media (max-width: 768px) {
.hero-content { padding: 3rem 1.5rem; }