demo.aifeed.md · live demonstration
This site practices what AIFeed preaches
Every page is published twice: polished HTML for readers, and signed, agent-ready markdown for machines. Permissions are Ed25519-signed, pinned to the domain through DNS, and revocable.
Verify this site in the browser Run it from the CLI
Ed25519 + JCSDNS anchor
_aifeedMulti-signature revocationZero dependenciesWhat this origin declares
| Use | Decision | Why |
|---|---|---|
| search, retrieval, input | allow | Fetching and grounding is welcome. |
| quote, summarize | allow | Attribution is required. |
| training | deny | Model training is not permitted. |
| modify, embed, commercial_use | deny | Derivative and resale uses are not. |
Built for agents that check before they fetch
Signed manifest
A single /.well-known/ai.json with per-use permissions, limits, and a revocation pointer.
Dual-stack content
The same bytes under text/aifeed+markdown and text/mako+markdown, separate signature contexts.
Delta index
Per-page digests and triage fields so agents skip what did not change.
Revocation
Status documents signed by two governance keys; bounded staleness rules.
Endpoints robots should read first
| Path | Method | Expected | Content type |
|---|---|---|---|
/.well-known/ai.json | GET | 200 | application/json |
/.well-known/ai-signature.json | GET | 200 | application/json |
/.well-known/aifeed-index.json | GET | 200 | application/json |
any page with Accept: text/aifeed+markdown | GET | 200 | text/aifeed+markdown |
/llms.txt | GET | 200 | text/plain |
Fetch it in one command
node examples/agent/compliant-agent.js https://demo.aifeed.md --use retrieval --fetch
The agent discovers the manifest, verifies the chain, checks permissions, and only then reads signed content.