AHTMLthe contract layer of the agent web

AHTML (Agentic HTML) lets a website declare a single semantic snapshot of a page and emit, from that one source, every protocol an AI agent might want: an MCP tool manifest, an OpenAPI 3.1 document, JSON-LD, an llms.txt shim, an RSL 1.0 license, a Markdown view, and a token-optimal, optionally signed snapshot with typed, priced actions. One config in, every agent-readable protocol out. RSS, but for AI agents. It is a sixteen-package npm scope (@ahtmljs/*) at v1.1.0, plus the ahtml Python SDK, and its universal extractor lets agents consume any site today, with or without adoption.

npx @ahtmljs/cli init           # detects Next/Astro/SvelteKit/Vite/Hono, wires everything
npm install @ahtmljs/next       # Next.js plugin
npm install @ahtmljs/astro      # Astro integration
npm install @ahtmljs/sveltekit  # SvelteKit hook
npm install @ahtmljs/vite       # Vite / SolidStart / vanilla Vite
npm install @ahtmljs/hono       # Hono · Node · Bun · Deno · Workers · Lambda
npm install @ahtmljs/agent      # typed client SDK for agents (dry-run sandbox)
npm install @ahtmljs/langchain  # RAG document loader
pip install ahtml               # Python SDK, LangChain loader included
npx @ahtmljs/cli mcp <url>      # turn ANY site into MCP tools, no adoption needed

• How do I add MCP to a Next.js app?

  Install @ahtmljs/next and wrap your config. The plugin auto-discovers routes and emits an MCP tool manifest at /ahtml/mcp.json from the same snapshot it uses for OpenAPI, JSON-LD, and llms.txt. No separate MCP server to write or deploy.

• Is AHTML a replacement for llms.txt or JSON-LD?

  No. It emits both, plus MCP and OpenAPI, from one config. llms.txt is a human-readable index and JSON-LD targets search engines; AHTML adds typed actions, cost and reversibility metadata, freshness, and a signed snapshot on top, and generates the others for you.

• Does it work outside Next.js?

  Yes. Dedicated adapters cover Astro (@ahtmljs/astro), SvelteKit (@ahtmljs/sveltekit), and other Vite-based apps like SolidStart (@ahtmljs/vite), and @ahtmljs/hono covers Node, Bun, Deno, Cloudflare Workers, and AWS Lambda, all with byte-identical output. `npx @ahtmljs/cli init` detects your framework and wires everything.

• Do the sites my agent reads need AHTML installed?

  No. The consumer side works on any URL today: @ahtmljs/agent's fetchPage() and the ahtml Python SDK fall back to extracting typed entities from ordinary HTML (schema.org, OpenGraph, microdata), and `npx @ahtmljs/cli mcp <url>` turns any site into MCP tools for Claude, ChatGPT, or Cursor.

• Can a site charge AI agents or verify who is calling?

  Yes. Actions declare typed cost with x402 payment rails behind a standards-compliant HTTP 402 flow, sites can require RFC 9421-signed requests from verified agents, and content licensing ships via an RSL 1.0 file plus Content Signals, with a dry-run sandbox so agents rehearse priced or irreversible actions before paying.

npm scope →GitHub →

Compare vs llms.txt

Klinder-OSS · Diffcore · whatbroke · Roy UI · Fresco · all work · about the maker