Go Stret Long Kontent
AGIRight.org

AICL — Level blong Laesensing blong AI Kontent

Laesens blong AI Kontent / Level blong Laesensing blong AI Kontent

Tanem olketa raet wea oli talemaot, i kam laesensing wea save ranem: kwot, pem, verifae, odit, rivok.

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 · Purpos

  • Tanem olketa stetmen blong raet i kam wan maket blong laesensing wea save wok trufala, no jas wan Wep wea i open o klosum nomoa.
  • Standadaesim flow blong masin-go-masin: faendem polisi → askim kwot → laesens → yusum → odit.
  • Holem olketa pemen blong ejent insaed long limit: badjet, level blong aprovol, token wea fitim rikwest, fulwan rekod blong odit.
  • Givim olketa man wea providim kontent, wan rod i go long pemen, wetaot klosum sait blong olketa go long AI.

03 · Skop

00

Katalog Blong Laesens — olketa level blong bandol raet witim praes an kondisen

01

Endpoint Blong Kwot / Pem / Verifae / Rivok

02

Token Blong Laesens Wea Saenim, Fitim Man Wea Rikwestim, Skop, An Taem

03

Rekod Blong Yusum An Odit Trael

04

HTTP 402 "Pemen I Nidim" Wea I Wok Gud Wetem Narafala Sistem

05

Rul Blong Sefti: no AI save handolem stret detel blong kad, level blong aprovol wea man i mekem

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 Wea Masin Save Readim

Olketa Laesens Blong Sait Ia Seleva — /.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 · Olketa Limitesen

  • Sait ia i no ranem wan getwei blong pemen; olketa laesens blong bisnes oli bes long kontak, long v0.1.
  • AICL hem i wan propozol blong protokol — hem i no promisim sei olketa kompani AI bae oli pemem trufala.
  • Komplaens blong pemen, tax, an rigyulesen blong faenens, oli aotsaed long skop blong draft ia.
  • Fomat blong token an minim blong endpoint, oli eksperimentol, an 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.