Go Stret Long Konten
AGIRight.org

AICL — Level blong Laesensing blong AI Kontent

Laesens blong AI Kontent / Level blong Laesensing blong AI Kontent

Tanem ol raet we oli talemaot i kam laesensing we i save ranem: kwot, pem, vereifae, odit, ravok.

Draft v0.1.1 Skema ↓

01 · Definisen

AICL is the licensing and transaction layer built on top of AICR. Where AICR declares what is allowed, AICL defines how permission is actually obtained: license tiers and prices, quote and payment endpoints, signed license tokens, usage and audit logs, and revocation. It is designed to interoperate with emerging machine-payment mechanisms such as HTTP 402 flows and pay-per-crawl schemes, with agentic payment kept inside human-approved budgets and audit trails. Content License ⇏ Agent Action Authority, and the reverse also holds — valid Agent Authority (AADP) ⇏ Content License: an AICL credential proves content-use permission, not a general Agent authorization token.

02 · Porpos

  • Tanem ol stetmen blong raet i kam wan maket blong laesensing we i save wok, i no jas wan Wep we i open-o-klos nomo.
  • Mekem standad blong flo masin-i-go-masin: faenemaot polisi → askem kwot → laesens → yusum → odit.
  • Holem pemen blong ejent insaed long limit: badjet, treshold blong aprovol, token we i fitim risik nomo, fulwan rekod blong odit.
  • Givim ol man we oli providem kontent wan rod blong kasem pemen, wetaot klosem sait blong olgeta long AI.

03 · Skop

00

Katalog Blong Laesens — ol level blong bandel blong raet wetem praes mo kondisen

01

Ol Endpoint Blong Kwot / Pem / Vereifae / Ravok

02

Token Blong Laesens We Oli Saenem, Taengem Long Man We i Askem, Skop, mo Taem

03

Rekod Blong Yusum mo Trael Blong Odit

04

Fasin Blong Wok Gud Wetem HTTP 402 "Payment Required"

05

Rul Blong Seifti: AI i no save handlem stret detel blong kad, treshold blong aprovol blong man

06

principal / actor / authority_reference / aadp_authority_id — optional fields (v0.1.1) linking a license to the AADP authority context an Agent acted under, without making the license itself an authorization token

04 · Eksampol We Masin i Save Ridim

Ol Laesens Blong Sait Ia Wan — /.well-known/aicl.json

/.well-known/aicl.json
{
  "version": "0.1",
  "publisher": "AGIRight.org",
  "licenses": [
    {
      "id": "public_read_summary",
      "rights": ["read", "summarize", "quote"],
      "price": { "amount": "0", "currency": "USD" },
      "conditions": [
        "attribution_required",
        "no_model_training",
        "no_commercial_redistribution"
      ]
    },
    {
      "id": "research_rag",
      "rights": ["read", "summarize", "rag"],
      "price": { "amount": "0", "currency": "USD" },
      "conditions": [
        "attribution_required",
        "retention_days_30",
        "no_model_training"
      ]
    },
    {
      "id": "commercial_or_training_license",
      "rights": ["training", "commercial_use"],
      "requires_contact": true,
      "contact": "contact@agiright.org"
    }
  ]
}

05 · Ol Limitesen

  • Sait ia i no ranem wan getwe blong pemen; komesol laesens oli beis long kontak long v0.1.
  • AICL i wan propozol blong protokol — hem i no promes se ol kampani blong AI bae oli pem.
  • Komplaens blong pemen, taks, mo regiulesen blong faenens oli aotsaed long skop blong draft ia.
  • Fomat blong token mo semantik blong endpoint oli eksperimentol mo oli save jenis.
  • v0.1.1: an AICL license credential must not be interpreted as a general Agent authorization token, and a valid OAuth/MCP/AADP credential must not be interpreted as an automatic content-use license.

Notis Blong Nem

In earlier EveMissLab research, the acronym AICL also names the “AI Ingestion & Capability Layer” — an architectural layer for how AI systems read and invoke websites (manifest, corpus, capability, runtime control, governance sublayers). As of v0.2 of that paper (2026-08-15), the two meanings are formally disambiguated with suffixes: this protocol is now referenced as AICL-C (AI Content License / AI Content Licensing Layer) in cross-references and machine-readable metadata, while the ingestion architecture is AICL-I. This page keeps the plain "AICL" id and URL for continuity — no existing link breaks — but the AICL-C suffix is the disambiguated name going forward. See the AICL-I v0.2 whitepaper for the full ingestion/capability/runtime-control architecture, which is a separate integration layer, not a seventh rights protocol.