Ale dirèkteman nan kontni an
AGIRight.org

AICL — Kouch Otorizasyon Lisans Kontni AI

Lisans Kontni AI / Kouch Otorizasyon Lisans Kontni AI

Transfòme dwa deklare an lisans egzekitab: mande pri, peye, verifye, odite, revoke.

Draft v0.1.1 Chema ↓

01 · Definisyon

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

  • Konvèti deklarasyon dwa yo an yon mache lisans ki fonksyone, olye pou yon entènèt ki binè, swa louvri swa fèmen.
  • Estandadize fli machin-a-machin nan: dekouvri politik → mande yon pri → jwenn lisans → itilize → odite.
  • Kenbe peman ajan yo limite: bidjè, sèy apwobasyon, token ki lye ak chak demann, jounal odit konplè.
  • Bay founisè kontni yon chemen pou konpansasyon san yo pa fèmen sit yo pou AI.

03 · Etandi

00

Katalòg lisans — nivo pakè dwa avèk pri ak kondisyon

01

Pwen final pou demann pri / peye / verifye / revoke

02

Token lisans siyen ki lye ak moun k ap mande a, etandi a, ak tan

03

Jounal itilizasyon ak tras odit

04

Entewoperabilite avèk HTTP 402 « Payment Required »

05

Règ sekirite: AI pa gen dwa manyen done brit kat kredi, sèy apwobasyon moun

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 · Egzanp machin ka li

Pwòp lisans sit sa a — /.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 · Limitasyon

  • Sit sa a pa opere okenn pòtay peman; lisans komèsyal yo baze sou kontak nan v0.1.
  • AICL se yon pwopozisyon pwotokòl — li pa garanti ke antrepriz AI yo ap peye.
  • Konfòmite peman, taks, ak régilasyon finansye andeyò etandi avan-pwojè sa a.
  • Fòma token ak siyifikasyon pwen final yo eksperimantal e yo ka chanje.
  • 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.

Nòt sou non

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.