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 (_aifeed TXT) so a manifest cannot be spoofed by another domain.
4. Agents verify the chain — TLS → domain → signature (JCS + Ed25519) → DNS anchor — and re-check a multi-signature revocation registry on every use.
5. Rotate keys safely — announce the successor with an old-key-signed directive (plus an advisory DNS pk2 cross-check), keep a bounded overlap, cut over, then revoke the old key permanently. Runbook: docs/rotation.md.
6. Serve lean content under one of two profiles (below), with a signed delta index so unchanged pages cost 0 bytes.

For AI agents: the check-first guide (discovery → verification → permission decisions → delta → failure handling) is in docs/agent-quickstart.md, with a runnable example at examples/agent/compliant-agent.js.

Verify from other stacks

Independent Python package (standard library only):

pip install aifeed

from aifeed import verify

report = verify.verify_directory('./my-site', domain='example.com')
print(report['result'], report['errors'])

Prefer the repository? The same CLI is here (zero dependencies, Node ≥ 20):

cd aifeed-protocol
node bin/cli.js keygen --out keys/
node bin/cli.js validate https://example.com
node bin/cli.js site build ./public --domain example.com --key keys/aifeed-private.pem

Two content profiles

Dual-stack origins serve both; cross-format replay is rejected by design.

Measured results

All numbers are reproducible from committed artifacts (npm run bench:mako, npm run bench:enforcement); the test environment is a single machine on loopback networking with a synthetic 60-page corpus. Honest baseline included.

The 30-day live pilot has not run yet; projections per 1,000 tenants are labeled as model extrapolations, and vendor claims of up to 94 % token reduction require semantic summarization this project does not perform automatically.

What's in this repository

Documentation

• Specifications: spec/en · spec/id · schemas
• Reference implementation: docs/REFERENCE.md
• Maintenance contract (AI agents & devs): AGENTS.md
• Architecture: docs/architecture.md · Release guide: docs/release.md
• Agent quickstart (client side): docs/agent-quickstart.md
• Publisher AI guide (owner side): docs/publisher-ai-guide.md
• Publisher Studio (local app): studio/README.md
• Agent skill: skills/aifeed/SKILL.md (installable via ClawHub: npx clawhub install aifeed)
• Complete guide: docs/penjelasan-aifeed.html (source of https://aifeed.md/penjelasan.html)
• Security policy: SECURITY.md
• Governance & open-core policy: GOVERNANCE.md
• Deploying the site: docs/deploy-site.md
• arXiv submission notes: paper/ARXIV-SUBMISSION.md

Status

• Release 1.0.0-draft — the specifications are not frozen yet. Wire versions: manifest 0.1/0.2, AIFeed Markdown 1.0, MAKO 0.2.
• Conformance: 34 manifest + 39 MAKO + 11 AIFeed Markdown vectors, executed by independent JavaScript and Python verifiers, plus PHP differential fixtures, 90,000+ fuzz executions, and a WordPress end-to-end test.
• Not claimed: external cryptographic review and a live pilot (both pending); origin+DNS compromise is undetectable on first contact.

License and contact

Specifications CC BY 4.0 · reference code and plugin MIT · vectors CC0. Contact: contact@aifeed.md — security reports per SECURITY.md.