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.
your_website
HTML, APIs, content
lmlattice
MCP · manifest · context
ai_agents
Claude, ChatGPT, Gemini
// /.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 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.
three steps. total control.
create lattice.json
Define your content permissions, licensing terms, and AI usage policies in a single JSON file at your domain root.
bots discover it
AI agents check /.well-known/lattice.json before crawling — just like browsers check robots.txt. It's the new handshake.
you set the rules
Grant, restrict, or monetise access per-model, per-use-case. Training, inference, scraping — each on your terms.
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.
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
better data for everyone
AI agents are already visiting your site. Give them what they need — and get intelligence in return.
scraped HTML
~10,500 tokensFull page render with navigation, scripts, ads, and tracking. The agent parses noise to find signal.
parsed page
~800 tokensAccessibility tree extraction. Better, but still requires rendering the full page first.
lattice response
~200 tokensStructured JSON via MCP. No page render. Exactly what the agent needs, nothing it doesn't.
you control the narrative
Define exactly what data agents see. Your content, your structure, your terms.
demand intelligence
See what agents are asking for. Discover gaps in your content before your competitors do.
50x more efficient
Agents get answers in 200 tokens instead of 10,500. Faster responses, lower costs, happier users.
zero page load
No Playwright. No Chrome. No rendering. Data served directly via API.
simple, transparent pricing
open_source
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
setup
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
managed
Fully managed hosting, analytics, and MCP server.
- Everything in Setup
- Managed MCP server
- Context Bridge hosting
- Analytics dashboard
- PII filtering engine
- Priority support
enterprise
Dedicated infrastructure, SLAs, and onboarding.
- Everything in Managed
- Dedicated infrastructure
- Custom integrations
- SSO / SAML
- 99.9% SLA
- Onboarding + training
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.
open source · MIT licensed · no vendor lock-in