Sote a kontenyen
AGIRight.org

AICL — Lakous Lisansman Kontenyen AI

Lisans Kontenyen AI / Lakous Lisansman Kontenyen AI

Konverti drwa deklare an lisansman egzekitab: devi, peye, verifye, verifikasyon (lodit), anile.

Draft v0.1.1 Sema ↓

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

  • Konverti deklarasyon drwa an en marse lisansman ki fonksyonn olye en web binèr ouver/ferme.
  • Estandardiz fliks masin-a-masin: dekouver politik → demann devi → lisansye → servi → verifye.
  • Gard bann peman azantik limite: bidze, so aprouvasyon, zeton lye avek demann, rezis lodit konplè.
  • Donn bann founiser kontenyen en semen ver konpansasyon san ferm zot sit avek AI.

03 · Oportye

00

Katalog lisans — nivo lo pake drwa avek pri ek kondisyon

01

Pwen final pour devi / peye / verifye / anile

02

Zeton lisans sinnyen ki lye avek demandeur, oportye, ek letan

03

Rezis servis ek pist lodit

04

Entèroperabilite avek HTTP 402 „Payment Required”

05

Regleman sekirite: AI pa manipile done kart brit, so aprouvasyon imen

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 · Legzanp ki masin i kapab lir

Lisans sa sit-la limenm — /.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-la pa opere en pòrtay peman; lisans komersyal i baze lo kontak dan v0.1.
  • AICL i en propozisyon protokol — i pa garanti ki bann konpanyi AI pou peye.
  • Konformite peman, taks, ek regilasyon finansye i andeor oportye sa brouyon.
  • Format zeton ek semantik pwen final i eksperimantal e i kapab sanze.
  • 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.

Remark lo nonmen

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.