AIFeed

English · Bahasa Indonesia · 中文

Signed content permissions for the AI web.
Declare, sign, and revoke what AI agents may do with your content — and let agents prove it.

▶ Watch: How AIFeed stops web scraping waste

Website · Protocol flow · Benchmark · Complete guide · Paper (PDF)

1-Minute Quickstart

Publisher side — sign what agents may do with your content:

npx aifeed keygen --out .aifeed                         # Ed25519 key pair
npx aifeed site build ./public --domain example.com \
  --key .aifeed/aifeed-private.pem --llms --inject      # manifest + page markdown + index
npx aifeed validate ./public --domain example.com       # verify locally

Prefer zero config? npx aifeed init --domain example.com --dir ./site creates the keys, a signed manifest, and the DNS/host setup guide in one step.

Agent side — verify any domain in 3 lines:

npm install @aifeed/verify

const { verifyRemote } = require('@aifeed/verify');
const out = await verifyRemote('example.com'); // discovery → signature → DNS anchor
console.log(out.result, out.anchor.status);    // VERIFIED anchored

TypeScript: import { verifyRemote } from '@aifeed/verify';

Where to go next: Why AIFeed? · agent quickstart · publisher AI guide · Studio publisher app · npm: aifeed CLI · @aifeed/verify

Why AIFeed?

AI agents now drive a large and growing share of web traffic, but the signals that say what they may do are unsigned text files. Anyone can edit them, nothing binds them to a domain, and there is no way to revoke them. The asymmetry is measurable:

• 1.9 billion crawls ignored robots.txt rules in a single half-year (one vendor).
• A 70,900 : 1 crawl-to-referral ratio was measured for a major AI provider.
• AI bots averaged 4.2 % of HTML requests in 2025, peaking at 6.4 %.

AIFeed replaces "please respect this file" with a cryptographically verifiable declaration, plus lean agent-ready content that cuts cost on both sides.

How it works

1. Generate an Ed25519 key pair — the private key never leaves the origin.
2. Publish a signed manifest at /.well-known/ai.json: per-use permissions (training, retrieval, quote, …), crawl limits, license, revision.
3. Anchor the key in DNS (`_aif

... View full README on GitHub