Hön na Kontenü
AGIRight.org

AICL — Undêrê ti Licence ti Kontenü ti IA

Licence ti Kontenü ti IA / Undêrê ti Licence ti Kontenü ti IA

Agbïan dröa so a wärä ni aga licence so alîngbi tî sâra kua na ndö ni: hunda-ngêrë, futa, bâa-nzönî, audit, kanga.

Draft v0.1.1 Schéma ↓

01 · Nda-tënë

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 · Ndâlï

  • Gbïan wärängö ti dröa aga marché ti licence so ayeke sâra kua nzönî, aga internet so ayeke gï «azi/akanga» oko pëpe.
  • Sâra si lêgë ti masïni na masïni andïä: wara ndïä → hunda ngêrë → licence → sarango → audit.
  • Batä futa ti agent na yâ ti angbâti: abudget, angbâti ti yëngö, atoken so andïä na hunda, na ambeti ti audit so ayeke kûê.
  • Mû na awa-mû-kontenü lêgë ti futa, aga kanga site ti ala na IA pëpe.

03 · Portée

00

Catalogue ti Licence — anivo ti gbâ ti dröa na angêrë na ahunda

01

Aendpoint ti Hunda-Ngêrë / Futa / Bâa-Nzönî / Kanga

02

Atoken ti Licence so A Sû Iri na Ni, so Andïä na Wa-Hunda, Portée, na Ngbonga

03

Ambeti ti Sarango-Kua na Ambeti ti Audit

04

Sarango Kua Terê Na Terê na HTTP 402 «Payment Required»

05

Andïä ti Siriri: IA agbû donnée ti carte mvenî pëpe alâ, angbâti so zo mvenî amû yëngö ni

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 · Tapande so masïni alîngbi tî diko

Alicence ti Site So Mvenî — /.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 · Limites

  • Site so agbû lêgë ti futa pëpe; alicence ti mbongo ahunda contact na v0.1.
  • AICL ayeke tënë ti protocole so a fa — a mû garantie so société ti IA afuta pëpe.
  • Lïngbïngö ti futa, impôt, na ndïä ti nginza ayeke na yâ ti portée ti mbeti-kôzo so pëpe.
  • Aformat ti token na nda-tënë ti aendpoint ayeke ti tapande, na alîngbi tî changé.
  • 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.

Tënë ndâlï ti iri

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.