Signed content permissions for the AI web
AIFeed is an open standard that lets a site declare, sign, and revoke what AI agents may do with its content — training, indexing, summarization, citation — and lets agents verify every claim independently.
Standar terbuka untuk deklarasi izin konten AI: bertanda tangan Ed25519, terverifikasi, dapat dicabut.
A signed declaration at /.well-known/ai.json: permissions, key discovery, contact, and revision history.
The native profile: text/aifeed+markdown (.aifeed.md) with an in-band permission block and token budgets.
Serve the external MAKO trust profile from the same publisher tooling — one origin, two signed formats.
Ed25519 + JCS signatures, revocation re-checks, delta indexes, and offline bundles — with 75 conformance vectors.
Zero-dependency CLI and SDK, plus an independent Python verifier that cross-checks every vector.
Static sites, nginx, Caddy, Apache, Node, Next.js, PHP, Python, Go — and a WordPress plugin.
New integrations are added over time — follow the repository for updates.
Animated walkthrough: declaration, verification, MAKO, delta indexes, and the two-sided savings.
Publisher and agent savings measured across four client profiles and 100 tenants.
The long-form English guide: problem, protocol, profiles, measured savings, revocation, and adoption.
A full publisher origin: signed manifest, dual-stack markdown, delta index, llms.txt.
A newsroom with signed triage metadata and EN/ID alternates inside the frontmatter.
An e-commerce catalog that denies commercial use and publishes media assets.
A public portal that allows reproduction, with attribution optional.
Search-only, enforced live: 403 for training crawlers, 429 for non-compliant ones.
A multi-signature registry demonstrating suspended status and client behaviour.
Verify any origin in your browser: WebCrypto, DNS-over-HTTPS, no server round-trip.