Index of every page on this site: llms.txt

Set aiReady.aiTerms to publish your policy at /.well-known/ai-terms. The feature follows the AI Terms 0.1 draft. It stays disabled until you configure a policy.

Set site.url and give all four uses an access rule. Set default for clients that omit the AI-Purpose header. Set updated to the date you last changed the policy, in YYYY-MM-DD format.

nuxt.config.ts
export default defineNuxtConfig({
  modules: ['nuxt-ai-ready'],
  site: { url: 'https://example.com' },
  aiReady: {
    aiTerms: {
      updated: '2026-11-18',
      default: 'deny',
      uses: {
        search: { access: 'allow', attribution: 'required' },
        answer: { access: 'allow', attribution: 'required' },
        training: { access: 'deny' },
        agent: { access: 'allow' },
      },
    },
  },
})

After you start the server, substitute your site URL and fetch the policy. Check that the response contains your rules and that site matches your site's origin.

curl -i https://example.com/.well-known/ai-terms

The endpoint supports GET, HEAD, and cross-origin discovery. Check a page's response for a Link header with rel="ai-terms". Check robots.txt for an AI-Terms directive. Prerendering writes a static policy file. AI Terms also works with database: false.

With app.baseURL: '/docs/', the discovery URL becomes https://example.com/docs/.well-known/ai-terms. Nuxt redirects origin-root discovery requests to that route. The document's site remains https://example.com, because the draft describes an origin policy. On static hosting, configure that origin-root redirect if your host does not provide it. Nuxt Robots disables robots.txt generation for apps with a base URL. Add the AI-Terms directive to the origin's own robots.txt file in that case.

AI Terms publishes a statement of your policy. Your server or gateway must enforce access rules, verify client identities, collect payments, and issue receipts. Existing robots.txt rules and content signals still apply. Publishing an allow rule does not override those restrictions.

Uses and path overrides

UsePurpose
searchIndex pages for AI search links and snippets
answerFetch a page to answer a person's current question
trainingCollect content for model training or fine-tuning
agentRead pages or call endpoints to complete a task

Each use requires access: allow, deny, or paid. Optional attribution accepts required, requested, or none. Use paths to override selected uses:

paths: [
  {
    match: '/members/*',
    uses: {
      search: { access: 'deny' },
      answer: { access: 'deny' },
    },
  },
]

In the draft, * matches within one path segment. The most specific matching entry wins and overrides only the uses it lists. Configure Nuxt route rules separately if your site needs them.

Describe an existing payment setup

If your gateway already enforces x402 payments, describe its price and endpoint:

export default defineNuxtConfig({
  modules: ['nuxt-ai-ready'],
  site: { url: 'https://example.com' },
  aiReady: {
    aiTerms: {
      updated: '2026-11-18',
      default: 'deny',
      uses: {
        search: { access: 'allow' },
        answer: { access: 'allow' },
        training: { access: 'deny' },
        agent: {
          access: 'paid',
          price: { amount: '0.002', currency: 'USD', per: 'page' },
        },
      },
      payment: {
        protocol: 'x402',
        version: 2,
        endpoint: 'https://pay.example.com/x402',
        network: 'eip155:8453',
        asset: 'USDC',
      },
    },
  },
})

A paid use needs a decimal string price and an absolute HTTPS payment endpoint. Use an endpoint URL without credentials, query parameters, or a fragment. Path overrides can provide their own endpoint or inherit the top-level payment. A paid default requires a top-level endpoint. The module rejects invalid configuration during Nuxt setup.

The configuration also accepts the draft's identity, receipts, contact, report_only, and preview fields. Paid and denied uses can declare a verified client's free allowance. Publish these fields only when they describe your server's behavior. Set aiTerms: false to disable an inherited policy.

Was this page helpful?