v1.0 protocol spec — now public

robots.txt was for search engines.

lattice.json is for AI.

The open protocol that tells language models what your content is, how to use it, and what's off-limits. One file. Total control.

$ read the spec view on github
scroll

your_website

HTML, APIs, content

lmlattice

MCP · manifest · context

ai_agents

Claude, ChatGPT, Gemini

// lattice.json [copy]
// /.well-known/lattice.json
{
  "lattice": "1.0",
  "entity": "acme_corp",
  "contact": "ai@acme.com",
  "permissions": {
    "training": false,
    "inference": "with_attribution",
    "scraping": false
  },
  "content_map": "/api/content",
  "context_bridge": {
    "enabled": true,
    "endpoint": "/lattice/ctx",
    "ttl_seconds": 86400
  }
}
// the_manifest

The robots.txt for AI agents.

Served at /lattice.json, this manifest tells arriving AI models exactly what they can and cannot do with your content.

  • Granular permissions: training, inference, scraping — each separately controlled.

  • Structured content maps expose your data without requiring crawling.

  • Context Bridge serves personalised, PII-filtered content via MCP.

// how_it_works

three steps. total control.

[1]

create lattice.json

Define your content permissions, licensing terms, and AI usage policies in a single JSON file at your domain root.

[2]

bots discover it

AI agents check /.well-known/lattice.json before crawling — just like browsers check robots.txt. It's the new handshake.

[3]

you set the rules

Grant, restrict, or monetise access per-model, per-use-case. Training, inference, scraping — each on your terms.

// features

built for the AI era

$

granular_permissions

Control training, inference, and scraping separately. Allow one model, block another.

>

context_bridge

Serve rich, structured context to AI models via MCP. Your content, your narrative, their answers.

/

content_map

Expose a structured index of your pages, products, and data. AI gets context without crawling.

[]

pii_filtering

Automatic detection and redaction of personal data before it reaches any model. GDPR-ready by default.

// comparison

the upgrade your content deserves

robots.txt

  • ✗ binary allow/disallow
  • ✗ no licensing information
  • ✗ no content structure
  • ✗ no per-model controls
  • ✗ designed for crawlers, not AI

lattice.json

  • ✓ granular permission model
  • ✓ licensing and attribution terms
  • ✓ structured content maps
  • ✓ per-model and per-agent rules
  • ✓ built for language models natively
// pricing

simple, transparent pricing

open_source

Free

Follow our docs to self-host lattice.json on your infrastructure.

  • lattice.json spec + schema
  • Step-by-step setup guide
  • Example configurations
  • Community support
  • MIT licensed
$ read the docs

setup

£500 one-off

We configure and deploy lattice.json on your servers.

  • Everything in Open Source
  • Professional installation
  • Custom config for your content
  • MCP server setup
  • 30 days support included
$ book setup
recommended

managed

£299 /mo

Fully managed hosting, analytics, and MCP server.

  • Everything in Setup
  • Managed MCP server
  • Context Bridge hosting
  • Analytics dashboard
  • PII filtering engine
  • Priority support
$ deploy now

enterprise

Custom

Dedicated infrastructure, SLAs, and onboarding.

  • Everything in Managed
  • Dedicated infrastructure
  • Custom integrations
  • SSO / SAML
  • 99.9% SLA
  • Onboarding + training
$ contact us

your content. your rules.

Join the growing number of publishers taking control of how AI interacts with their content. The lattice protocol is open, free, and ready to deploy.

$ deploy lattice.json read the docs

open source · MIT licensed · no vendor lock-in