Specification ยท Version 1.0

robots-trust.json Standard

The open specification for machine-readable AI trust certificates. Any website can implement this standard โ€” no registration required for the basic file.

Table of Contents

  1. Overview
  2. File Placement
  3. Full Schema Reference
  4. AI Training Permissions
  5. Complete Example
  6. Validation
  7. Registry & Certification

1. Overview

The robots-trust.json standard provides a machine-readable way for websites to declare their AI readiness, content access policies, and AI training permissions. It is placed at a well-known URL and can be read by any AI agent, crawler, or automated system.

The standard is inspired by robots.txt (crawl permissions) and sitemap.xml (page discovery), but designed specifically for the needs of AI systems that need to understand content structure, trust level, and training permissions.

Key principle: The file is designed to be self-descriptive and decentralized. Any website can publish a robots-trust.json without registering. Registration with Robot Trust Hub adds verified status and listing in the global registry.

2. Open Protocol โ€” Anyone Can Implement

The Robot Trust Protocol is open and decentralized. Any website can self-publish a robots-trust.json file without registering with any authority. The certificate_issuer field can be:

Issuer value Meaning Status
"self" Site self-attests its AI readiness Valid ยท unverified
"robot-trust.org" Verified by Robot Trust Hub โœ… Verified
"your-authority.org" Any other trusted issuer Depends on issuer trust
Design principle: robot-trust.org is the protocol creator and first trusted issuer, not a mandatory gatekeeper. This mirrors how HTTPS works โ€” anyone can self-sign a certificate, but browser-trusted CAs (like Let's Encrypt) provide verified status. The open list of trusted issuers is published at /trusted-issuers.json.

Minimal self-published certificate

{
  "robot_trust_version": "1.0",
  "site_identity": { "domain": "example.com" },
  "trust_status": {
    "robot_access": "allowed",
    "certificate_issuer": "self",
    "certificate_status": "pending"
  },
  "ai_training": {
    "training_allowed": true,
    "commercial_training_allowed": false
  }
}

This is a valid certificate AI agents can read and respect. Register with Robot Trust Hub to upgrade "self" โ†’ "robot-trust.org" and get certificate_status: "verified" with public registry listing.

2. File Placement

The file must be served at the following URL:

https://yourdomain.com/.well-known/robots-trust.json

The /.well-known/ path follows RFC 8615 โ€” the standard for well-known URIs. The file must be served over HTTPS and return Content-Type: application/json.

Optional companion files

File Path Purpose
robots-trust.json /.well-known/robots-trust.json Trust certificate Required
ai/index.json /ai/index.json Structured robot-readable content Optional
llms.txt /llms.txt Plain text site description for LLMs Optional

3. Full Schema Reference

Top-level fields

Field Type Description
robot_trust_version Required string Spec version. Must be "1.0"
site_identity Required object Site identification details
trust_status Required object Certificate and trust level
ai_readability Optional object Machine readability capabilities
access_points Optional object AI-accessible endpoints
ai_training Optional object AI training permissions
content_policy Optional object Content access policies
capabilities Optional object Supported AI interaction modes
update Optional object Issue and expiry dates

site_identity

Field Type Description
site_name string Human-readable site name
domain string Registered domain (e.g. example.com)
owner_type string company | individual | robot-operator | ai-platform
purpose string Plain text description of the site's purpose

trust_status

Field Type Description
robot_access string "allowed" | "restricted" | "denied"
certificate_issuer string Should be "robot-trust.org" for certified sites
certificate_status string "verified" | "pending" | "revoked"
trust_level string "basic" | "pro" | "enterprise" | "authority"
issued string ISO 8601 date of certificate issuance
expires string ISO 8601 date of certificate expiry (max 1 year)

access_points

Field Type Description
preferred_entry string Preferred URL path for AI agents (e.g. "/ai/")
robot_safe_endpoints array List of URL paths safe for AI access
rate_limit_policy string "ai-friendly" | "standard" | "strict"

4. AI Training Permissions

The ai_training section lets website owners explicitly declare whether their content may be used to train AI models โ€” including commercial models like LLMs. This is emerging as a critical signal for AI companies that need to respect content rights.

Field Type Default Description
training_allowed boolean true Whether AI models may train on this site's content
commercial_training_allowed boolean false Whether content may be used in commercial AI products
scraping_allowed boolean true Whether automated scraping for AI purposes is allowed
attribution_required boolean false Whether attribution is required when using the content
Why this matters: AI companies like OpenAI, Anthropic, and Google are actively looking for signals from website owners about training permissions. A standardized ai_training field in robots-trust.json provides a machine-readable way to express these preferences โ€” similar to how robots.txt expresses crawl preferences.

Example โ€” all training allowed

{
  "ai_training": {
    "training_allowed": true,
    "commercial_training_allowed": true,
    "scraping_allowed": true,
    "attribution_required": false
  }
}

Example โ€” no commercial training

{
  "ai_training": {
    "training_allowed": true,
    "commercial_training_allowed": false,
    "scraping_allowed": true,
    "attribution_required": true
  }
}

5. Complete Example

A complete robots-trust.json file implementing the full specification:

{
  "robot_trust_version": "1.0",

  "site_identity": {
    "site_name": "Acme Corp",
    "domain": "acme.com",
    "owner_type": "company",
    "purpose": "B2B software for logistics automation"
  },

  "trust_status": {
    "robot_access": "allowed",
    "certificate_issuer": "robot-trust.org",
    "certificate_status": "verified",
    "trust_level": "pro",
    "issued": "2026-03-07",
    "expires": "2027-03-07"
  },

  "ai_readability": {
    "machine_readable": true,
    "structured_data_available": true,
    "robot_priority_mode": true
  },

  "access_points": {
    "preferred_entry": "/ai/",
    "robot_safe_endpoints": ["/ai/", "/api/", "/data/"],
    "rate_limit_policy": "ai-friendly"
  },

  "ai_training": {
    "training_allowed": true,
    "commercial_training_allowed": false,
    "scraping_allowed": true,
    "attribution_required": false
  },

  "content_policy": {
    "human_site_available": true,
    "ai_generated_content_allowed": true,
    "automation_interaction_allowed": true
  },

  "capabilities": {
    "supports_ai_navigation": true,
    "supports_ai_generation": true,
    "supports_autonomous_agents": true
  },

  "update": {
    "last_updated": "2026-03-07",
    "expires": "2027-03-07"
  }
}

6. Validation

You can validate any domain's certificate using the Robot Trust verification tool:

โ†’ Verify a Certificate

The validator checks:

7. Registry & Certification

Any website can self-publish a robots-trust.json without registering. Registration with Robot Trust Hub adds:

Get Certified โ†’

9. Badge & Embed

Add a badge to your site or GitHub README to show AI agents and developers that your site implements the Robot Trust Protocol. The badge is live-verified โ€” it turns green automatically when your domain passes verification.

Default badge

<!-- Replace with your domain -->
<a href="https://robot-trust.org/validator.html?domain=example.com">
  <img src="https://robot-trust.org/api/badge?domain=example.com"
       alt="Robot Trust Protocol compatible">
</a>

Flat style

<img src="https://robot-trust.org/api/badge?domain=example.com&style=flat">

Mini badge

<img src="https://robot-trust.org/api/badge?domain=example.com&style=mini">

Markdown (GitHub README)

[![Robot Trust Protocol](https://robot-trust.org/api/badge?domain=example.com)](https://robot-trust.org/validator.html?domain=example.com)
Badge colours: ๐ŸŸข Green = verified by robot-trust.org  ยท  ๐Ÿ”ต Blue = compatible (self-published)  ยท  ๐ŸŸก Amber = file found but unverified  ยท  โšซ Grey = not found