# agent-preview/v1 — One Fetch, Every URL, Open Invitation — Mnemom Research
```json
{"@context":"https://schema.org","@type":"Article","headline":"agent-preview/v1 \u2014 One Fetch, Every URL, Open Invitation","name":"agent-preview/v1 \u2014 One Fetch, Every URL, Open Invitation","description":"We just published an IETF-style RFC for the agent-preview/v1 schema. It's vendor-neutral. Any site can adopt it \u2014 and we want them to.","url":"https://www.mnemom.ai/blog/mnemom-research/agent-preview-v1-open-invitation","inLanguage":"en-US","datePublished":"2026-05-14","dateModified":"2026-05-14","author":{"@type":"Organization","name":"Mnemom Research","url":"https://www.mnemom.ai/blog/mnemom-research"},"image":"https://www.mnemom.ai/api/og-image?type=blog&eyebrow=DISPATCHES&chip=Mnemom+Research+%C2%B7+3+min&author=Mnemom+Research&title=agent-preview%2Fv1+%E2%80%94+One+Fetch%2C+Every+URL%2C+Open+Invitation&subtitle=We+just+published+an+IETF-style+RFC+for+the+agent-preview%2Fv1+schema.+It%27s+vendor-neutral.+Any+site+can+adopt+it+%E2%80%94+and+we+want+them+to.","publisher":{"@id":"https://www.mnemom.ai#organization"},"keywords":["agents","open-protocols","spec","discoverability","infrastructure"]}
```
```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.mnemom.ai/"},{"@type":"ListItem","position":2,"name":"Dispatches","item":"https://www.mnemom.ai/blog"},{"@type":"ListItem","position":3,"name":"Mnemom Research","item":"https://www.mnemom.ai/blog/mnemom-research"},{"@type":"ListItem","position":4,"name":"agent-preview/v1 \u2014 One Fetch, Every URL, Open Invitation","item":"https://www.mnemom.ai/blog/mnemom-research/agent-preview-v1-open-invitation"}]}
```
[← Mnemom Research](/blog/mnemom-research)
# agent-preview/v1 — One Fetch, Every URL, Open Invitation
Mnemom Research
May 14, 2026
Mnemom now serves a structured `agent-preview/v1` manifest at every prerendered URL on the site — a one-fetch, MIME-tagged JSON sibling that tells an agent everything it needs to know about a link before deciding what to do with it: title, summary, canonical, type taxonomy, representations (HTML, markdown mirror, OG image, JSON-LD), and per-link context like author, published date, tags, reputation grade, claim status.
If you've ever watched an agentic client try to read a webpage, you know what's broken. The agent fetches HTML — usually 300 KB of layout chrome it doesn't need. Or it fetches the markdown mirror, which has body text but no metadata. Or it fetches the OG image, which is a 1200×630 PNG. Three round-trips, zero of them structured.
`agent-preview/v1` collapses that to one fetch. The shape is published at [mnemom.ai/spec/agent-preview/v1](/spec/agent-preview/v1). The same content framed as a proposed standard — Internet-Draft style, with schema, discovery, MIME registration, security considerations, and an explicit IANA path — is now live at [mnemom.ai/spec/agent-preview/v1/rfc](/spec/agent-preview/v1/rfc).
## Why an RFC, why now
We're the reference implementation. We're not the gatekeeper. The schema is intentionally vendor-neutral: nothing in it depends on Mnemom, our API, or our brand. Any site can publish manifests, advertise discovery via ``, and become one-fetch addressable for agents — no permission needed.
We wrote the RFC because we want to be wrong about being the only ones doing this. The MIME type starts as a vendor-tree entry per RFC 6838. If three or four independent implementations ship — different stacks, different domains — we'll file for promotion to the Standards Tree, drop the `vnd.` prefix, and the registered MIME becomes the canonical one. The schema doesn't change as a function of registration status; adopters can ship today.
## What's in the box
The substrate has been live since [PR #412](https://github.com/mnemom/mnemom-website/pull/412):
- **`scripts/build-preview-cards.mjs`** — the open-source build-time generator. Reads prerendered HTML, extracts metadata, writes the `.preview.json` sibling.
- **`client/lib/preview-types.ts`** — the normative TypeScript types.
- **Discovery via ``** — every prerendered page's head carries it; the agent never has to guess.
- **Nightly verification** — the `preview-surface` commitment on [/for-agents](/for-agents) validates every manifest against the v1 schema; if anything drifts, the watchdog files an issue.
[PR #414](https://github.com/mnemom/mnemom-website/pull/414) wired four dynamic-content surfaces (blog, research, agent reputation, coherence reports) through the same construction path so their per-link `context` carries real data — author, reading time, tags, grade, score — instead of empty stubs.
## Read it. Build it. Tell us.
If you ship structured metadata anywhere — a blog, a docs site, a profile directory — `agent-preview/v1` works for you. The schema is forgiving: required fields are minimal, every context field is optional, unknown types are tolerated. Start with the [implementer spec](/spec/agent-preview/v1), check the [RFC framing](/spec/agent-preview/v1/rfc) for the formal language, and the reference implementation is open at [github.com/mnemom/mnemom-website](https://github.com/mnemom/mnemom-website) — `scripts/build-preview-cards.mjs` is the only file you'd need to fork.
If you ship a preview surface on a domain you control, open an issue and we'll add you to the adopters list. The goal isn't ownership; it's that an agent fetching any URL in 2027 gets a structured answer in one round-trip — and nobody had to ask permission to make it true.
#agents#open-protocols#spec#discoverability#infrastructure
### Stay in the loop
New dispatches and product updates, no spam.
Subscribe
### Ready to verify your agents?
See it liveView plansTalk to us
[
Mnemom Research
All posts →
](/blog/mnemom-research)
---
_Source: /blog/mnemom-research/agent-preview-v1-open-invitation/index.html · Generated by build-markdown-mirrors.mjs · For agent-readability commitment #4 see https://www.mnemom.ai/for-agents_