Internet-Draft AI Terms November 2026
Ovalles Expires 20 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-ovalles-ai-terms-01
Published:
Intended Status:
Informational
Expires:
Author:
D. Ovalles
AIPayGen

AI Terms: Per-Use Terms, Payment and Receipts for Automated AI Access to Web Content

Abstract

This document defines AI Terms: a JSON document published at the well-known URI /.well-known/ai-terms in which a website states, for each of four uses of its content by automated AI systems (search, answer, training and agent), whether the use is allowed, allowed for a price, or not allowed. It also defines an AI-Purpose request header with which a client declares the use it intends, a way to point to the terms from any HTTP response, and how a paid access produces a receipt that records the use. AI Terms is designed to sit alongside the Robots Exclusion Protocol and the usage-preference vocabulary of the IETF AI Preferences work, adding the pieces those leave out: price, payment binding, purpose declaration by the client, and a record of licensed use.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 20 May 2027.

▲

Table of Contents

1. Introduction

The Robots Exclusion Protocol [RFC9309] lets a site say whether a named crawler may fetch a path. Automated AI systems now access web content for several distinct purposes: indexing for AI search, fetching a page live to answer a person, collecting content to train models, and acting as autonomous agents. Sites increasingly want different treatment per purpose, and some want to permit a purpose in exchange for payment rather than refuse it.

The IETF AI Preferences working group [AIPREF] is defining a vocabulary for expressing usage preferences [I-D.ietf-aipref-vocab] and ways to attach them to content [I-D.ietf-aipref-attach]; its charter excludes technical enforcement, client authentication, and auditing. Individual drafts cover neighbouring ground: [I-D.car-ai-txt-wellknown] declares usage policy and links to a licensing or pricing page, and [I-D.reilly-aipref-compliance] defines verifiable compliance records while explicitly excluding licensing, compensation and payment. None defines how an automated client pays for a use, declares the use it intends, or receives a record of a paid use. This document is intended to fill that gap and to be complementary to all three. It addresses four things:

  1. Terms per use, including a price. A use can be allow, paid (with a price and unit) or deny.

  2. Payment binding. For paid uses, the terms name a payment protocol and endpoint. This document uses HTTP 402 with the x402 protocol [X402] as the first binding.

  3. Purpose declaration by the client. A request header, AI-Purpose, in which the client states its intended use and so accepts that use's terms.

  4. Receipts. A paid response carries proof of payment and the declared purpose, giving both parties a record of licensed use.

A reference implementation is deployed and serves terms for every site using it [REFIMPL].

1.1. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2. Uses

This document defines four uses. Every access by an automated AI system falls under exactly one of them.

search:

Indexing content in order to show links or excerpts in AI-powered search results.

answer:

Fetching content in real time to answer a question asked by a person.

training:

Collecting content to train or fine-tune machine-learning models.

agent:

An autonomous software agent reading content or invoking endpoints to complete a task.

These uses refine the categories of the AI Preferences vocabulary [I-D.ietf-aipref-vocab] (AI Training, AI Use, Search) as follows: search corresponds to Search, training to AI Training, and answer and agent are two kinds of AI Use. The split of AI Use into answer and agent exists because sites commonly want to treat a person's live question differently from an autonomous agent's task; the author welcomes the working group's view on whether that split belongs in the vocabulary instead (see Section 9).

3. The AI Terms Document

3.1. Location and Format

A site publishes its terms as a JSON [RFC8259] object at the well-known URI [RFC8615] /.well-known/ai-terms, served with media type application/json and UTF-8 encoding. The document MAY instead be hosted elsewhere and referenced as described in Section 4; such a reference MUST use HTTPS.

3.2. Members

ai_terms (string, REQUIRED):

The version of this specification, "0.1" for this document.

site (string, REQUIRED):

The origin the terms apply to.

updated (string, REQUIRED):

Date of the last change, YYYY-MM-DD.

uses (object, REQUIRED):

One member per use (search, answer, training, agent), each a Use Terms object (Section 3.3).

default (string, REQUIRED):

allow, paid or deny, applied to an automated AI client that declares no use or whose identity check fails.

paths (array, OPTIONAL):

Overrides for parts of the site (Section 3.4).

identity (object, OPTIONAL):

verify, an array of identity methods the site applies (Section 6).

purpose_header (string, OPTIONAL):

"AI-Purpose" in this version.

payment (object, REQUIRED if any use is paid):

protocol, version, endpoint and protocol-specific members (Section 7).

receipts (string, OPTIONAL):

A description of the receipt a paid access returns.

report_only (boolean, OPTIONAL):

true if the site currently measures automated access without charging.

contact (object, OPTIONAL):

licensing, a URL for bulk or custom licensing.

Unknown members MUST be ignored.

3.3. Use Terms

access (string, REQUIRED):

allow, paid or deny.

price (object, REQUIRED when access is paid):

amount (decimal string), currency (ISO 4217 code; USD in this version) and per (page or request).

attribution (string, OPTIONAL):

required, requested or none: whether the client is to cite and link the source when content is shown to a person.

A client MUST NOT use content for a use whose access is deny. A client MUST NOT use content for a use whose access is paid unless it has paid for the access.

3.4. Paths

Each entry has match (a path pattern in which * matches any sequence of characters within one path segment), uses (a partial set of Use Terms) and optionally payment. The entry with the most literal characters in match that matches the request path applies; its uses replace the top-level terms for the uses it lists.

3.5. Example

{
  "ai_terms": "0.1",
  "site": "https://example.com",
  "updated": "2026-11-16",
  "uses": {
    "search":   { "access": "allow", "attribution": "required" },
    "answer":   { "access": "allow", "attribution": "required" },
    "training": { "access": "paid",
                  "price": { "amount": "0.002", "currency": "USD",
                             "per": "page" } },
    "agent":    { "access": "paid",
                  "price": { "amount": "0.002", "currency": "USD",
                             "per": "page" } }
  },
  "default": "paid",
  "identity": { "verify": ["published-ip-ranges"] },
  "purpose_header": "AI-Purpose",
  "payment": { "protocol": "x402", "version": 2,
               "endpoint": "https://pay.example/g/abc123def456",
               "network": "eip155:8453", "asset": "USDC" }
}

4. Discovery

In addition to the well-known URI, a server MAY reference the terms from any response with a Link header field [RFC8288] using the relation type ai-terms:

Link: <https://example.com/.well-known/ai-terms>; rel="ai-terms"

A server SHOULD include this link in HTTP 402 (Payment Required) responses [RFC9110] to automated clients, so that a client refused for payment can find the full terms.

A site MAY add a line AI-Terms: <URL> to its robots.txt. Section 2.2.4 of [RFC9309] allows records beyond the protocol's own; crawlers that do not interpret this one are unaffected by it.

5. Declaring the Purpose: the AI-Purpose Header Field

AI-Purpose is a request header field whose value is one of the use tokens defined in this document:

AI-Purpose = "search" / "answer" / "training" / "agent"

An automated AI client SHOULD send AI-Purpose with each request to a site that publishes AI Terms. By sending it, the client declares the use it intends and accepts the terms for that use. A server MAY record the declaration and MAY echo it in the response. Using content for a use other than the declared one is a breach of the published terms.

6. Identity

A client's claimed identity (for example a user-agent product token) is not by itself evidence of who operates it. The identity.verify member lists the methods a site applies:

published-ip-ranges:

The request's source address is within the address ranges the claimed operator publishes for that client.

web-bot-auth:

The request carries an HTTP message signature verifiable with a key the claimed operator publishes, as defined in [I-D.ietf-webbotauth-httpsig-protocol].

A client that fails every listed check is treated as unidentified, and the default terms apply to it.

7. Payment

When the applicable access is paid, a server answers a request that carries no valid payment with status 402 and the payment requirements of the protocol named in payment.protocol. For the x402 binding [X402], the requirements are carried in the PAYMENT-REQUIRED response header; the client retries with a signed authorization in the PAYMENT-SIGNATURE request header, and the content is returned only after the payment is verified. Settlement transfers the stated amount from the client's wallet to the site's.

Other payment protocols can be bound by defining their payment members in a future revision.

8. Receipts

A successful paid response SHOULD carry:

Together with the request URI and time, this forms a record of licensed use. The site can show which automated client accessed which content, for which use, and what was paid; the client's operator can show that it licensed the content it used. A future revision may define a signed receipt object independent of the payment protocol; the compliance records and transparency receipts of [I-D.reilly-aipref-compliance] are a candidate format to reuse rather than reinvent.

9. Relation to Other Work

Robots Exclusion Protocol:

Unchanged. A disallowed path remains disallowed; AI Terms governs the use and price of content that is fetched.

AI Preferences [I-D.ietf-aipref-vocab] [I-D.ietf-aipref-attach]:

The vocabulary expresses whether a usage category is permitted, and the attachment draft carries that in a Content-Usage header field and robots.txt rule. A site can keep expressing preferences that way; AI Terms adds a price and payment binding for categories the site permits for a fee, client-side purpose declaration, and receipts. Where both are present for the same content, a deny expressed through either SHOULD be honored.

AI.TXT [I-D.car-ai-txt-wellknown]:

Declares usage policy per category and per agent, with a Training-Fee member that links to a pricing page. AI Terms adds a machine-actionable price and payment binding, client purpose declaration and receipts. If preferred, the Use Terms, payment and purpose members of this document could be defined as an extension of the ai.json format instead of a separate well-known URI; the author is open to that.

Verifiable Compliance Records:

[I-D.reilly-aipref-compliance] records what a processor observed and decided, and excludes payment. AI Terms receipts record paid uses; the two can coexist, and a later revision may reuse its record format.

Really Simple Licensing [RSL]:

RSL 1.0 expresses licensing terms as an XML document discovered through a License: line in robots.txt, a Link header field with rel="license", or markup. It defines payment types (including per-crawl and per-use), a license server protocol based on OAuth 2.0, and can advertise x402 as an accepted payment method. RSL is the more complete licensing framework and has publisher backing; AI Terms is deliberately smaller: one JSON document with a directly actionable price per use, no license server, a purpose declaration by the client and a receipt on each paid response. The two can be published side by side, and a site with an RSL license can point to it from contact.licensing. Where both are present and disagree, the more restrictive SHOULD be followed. A mapping between the RSL payment types and the uses in this document is future work, and the author would welcome doing it with the RSL community.

Web Bot Auth [I-D.ietf-webbotauth-httpsig-protocol]:

Used as an identity method (Section 6).

x402:

Used as the first payment binding (Section 7).

10. Security Considerations

Terms are statements, not enforcement. Sites that require them to hold SHOULD enforce them at the server or edge, for example by answering 402 for paid uses and verifying identity for allowed ones.

A client can misstate its identity or purpose. Identity verification limits the former; receipts and independent detection of copied content make the latter visible.

A malicious or compromised terms document can state any price. Clients MUST apply their own spending limits per request and per period and MUST NOT pay without such limits.

Terms referenced from another origin MUST be fetched over HTTPS. Clients SHOULD cache terms for a bounded time and respect HTTP caching headers.

11. Privacy Considerations

The AI-Purpose header reveals the client's intended use to the server; this is its purpose. Receipts may link a payer's account or wallet to the content it accessed; operators that consider this sensitive should use payment accounts dedicated to automated access.

12. IANA Considerations

12.1. Well-Known URI

IANA is requested to register the following in the "Well-Known URIs" registry [RFC8615]:

  • URI Suffix: ai-terms

  • Change Controller: IETF

  • Reference: this document

  • Status: provisional

  • Related Information: none

12.3. HTTP Field Name

IANA is requested to register the following in the "Hypertext Transfer Protocol (HTTP) Field Name Registry" [RFC9110]:

  • Field Name: AI-Purpose

  • Status: provisional

  • Reference: this document

13. References

13.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8615]
Nottingham, M., "Well-Known Uniform Resource Identifiers (URIs)", RFC 8615, DOI 10.17487/RFC8615, , <https://www.rfc-editor.org/rfc/rfc8615>.
[RFC8288]
Nottingham, M., "Web Linking", RFC 8288, DOI 10.17487/RFC8288, , <https://www.rfc-editor.org/rfc/rfc8288>.
[RFC9110]
Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., "HTTP Semantics", STD 97, RFC 9110, DOI 10.17487/RFC9110, , <https://www.rfc-editor.org/rfc/rfc9110>.
[RFC9309]
Koster, M., Illyes, G., Zeller, H., and L. Sassman, "Robots Exclusion Protocol", RFC 9309, DOI 10.17487/RFC9309, , <https://www.rfc-editor.org/rfc/rfc9309>.
[RFC8259]
Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, DOI 10.17487/RFC8259, , <https://www.rfc-editor.org/rfc/rfc8259>.

13.2. Informative References

[X402]
"x402: an open payment protocol over HTTP 402", n.d., <https://www.x402.org>.
[AIPREF]
"AI Preferences (aipref) Working Group charter", , <https://datatracker.ietf.org/wg/aipref/about/>.
[I-D.ietf-aipref-vocab]
Keller, P. and M. Thomson, "A Vocabulary For Expressing AI Usage Preferences", Work in Progress, Internet-Draft, draft-ietf-aipref-vocab-08, , <https://datatracker.ietf.org/doc/html/draft-ietf-aipref-vocab-08>.
[I-D.ietf-aipref-attach]
Illyes, G. and M. Thomson, "Associating AI Usage Preferences with Content in HTTP", Work in Progress, Internet-Draft, draft-ietf-aipref-attach-05, , <https://datatracker.ietf.org/doc/html/draft-ietf-aipref-attach-05>.
[I-D.car-ai-txt-wellknown]
Cardillo, K., "AI.TXT: A Declaration File for AI Usage Preferences, Licensing, and Policy", Work in Progress, Internet-Draft, draft-car-ai-txt-wellknown-00, , <https://datatracker.ietf.org/doc/html/draft-car-ai-txt-wellknown-00>.
[I-D.reilly-aipref-compliance]
Reilly, L. J. R., "Verifiable Compliance Records for AI Usage Preferences", Work in Progress, Internet-Draft, draft-reilly-aipref-compliance-00, , <https://datatracker.ietf.org/doc/html/draft-reilly-aipref-compliance-00>.
[I-D.ietf-webbotauth-httpsig-protocol]
Meunier, T. and S. Major, "HTTP Message Signatures for automated traffic", Work in Progress, Internet-Draft, draft-ietf-webbotauth-httpsig-protocol-01, , <https://datatracker.ietf.org/doc/html/draft-ietf-webbotauth-httpsig-protocol-01>.
[RFC7942]
Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, , <https://www.rfc-editor.org/rfc/rfc7942>.
[RSL]
RSL Collective, "Really Simple Licensing (RSL) 1.0 Specification", , <https://rslstandard.org/rsl>.
[TOOLS]
AIPayGen, "AI Terms JSON Schema, test vectors and readers", , <https://github.com/Damien829/pay-per-crawl/tree/main/spec>.
[REFIMPL]
AIPayGen, "AI Terms reference implementation", , <https://aipaygen.com/ai-terms>.

Appendix A. Implementation Status

Note to the RFC Editor: please remove this section before publication.

This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.

A.1. AIPayGen gateway and site integrations

Organization:

AIPayGen (the author's).

Description:

Server side: generates the AI Terms document for each site from its settings, serves a site's own document at /.well-known/ai-terms, sends Link: rel="ai-terms" on 402 responses, verifies client identity against published IP ranges, settles with x402 and echoes AI-Purpose on paid responses. Client side: an agent tool that reads a site's document before paying, refuses a use the site denies or prices above the caller's limit, and sends AI-Purpose: agent.

Maturity:

Running in production on one site and offered to others; early.

Coverage:

All of this document except signed-request identity (Section 6), which is not yet implemented.

Licensing:

The site integrations (WordPress, Cloudflare Workers, Nginx, Apache, Next.js, Express, Django) are open source [REFIMPL]. The gateway is not.

Contact:

The author.

A.2. Python reader

Organization:

The author.

Description:

A single-file reader using only the Python standard library: fetches a document, resolves the terms for a use and path (Section 3.4), checks a price against a client limit, and validates a document.

Maturity:

New; written from this document's text.

Coverage:

Document parsing, Section 3.3 and Section 3.4. No payment.

Licensing:

MIT [TOOLS].

A.3. Interoperability aids

A JSON Schema for the document and a set of test vectors (validity cases, and path-resolution cases for Section 3.4) are published [TOOLS]. Both implementations above pass all vectors. They share an author, so they are not independent implementations; reports from others are welcome and will be listed.

Acknowledgments

Thanks to the site owners and developers whose public discussion of AI crawler access shaped the uses and the receipt design.

Author's Address

Damien Ovalles
AIPayGen