Dem ci Content Bi
AGIRight.org

AICL — Wàllu Lisaansu Content AI

Lisaans bu Content AI / Wàllu Lisaansu Content AI

Dafay soppi sañ-sañ yu ñu dëklare ba doon lisaans bu man a doxal: quote, fey, wóolu, odit, génn.

Draft v0.1.1 Schema ↓

01 · Tekki

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 · Njëlbeen

  • Soppi dëklaraasion sañ-sañ ba doon marse bu lisaans bu man a doxal, du rekk web bu «ubbeeku/tëj» rekk.
  • Def bu wóor dayeb bu masin-ci-masin: xam politig → laaj quote → lisaans → jëfandiku → odit.
  • Denc fey bu agent yi ci suuf dayo: bidiye, dayo ci nangu, token yu jokkoo ci laaj bi, ak xët i odit bu mat sepp.
  • Jox ñi joxe content yoon jëm ci fey, bu dul tëj seen sit ci AI.

03 · Dayo

00

Katalog Lisaans — xët-xët yu paket sañ-sañ ak njëg ak sart

01

Dugub yu Quote / Fey / Wóolu / Génn

02

Token yu Lisaans yu Signé, Jokkoo ci Ki Laaj, Dayo, ak Jamono

03

Xët i Njëfandiku ak Odit

04

Dëppoo ak HTTP 402 « Payment Required »

05

Yoonu Kaaraange: AI mënul jël xibaaru karte yu wóor, dayo ci nangu bu nit

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 · Misaal bu masin man a jàng

Lisaans bu sit bii ci boppam — /.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 · Limit yi

  • Sit bii doxalul benn dugub bu fey; lisaans ci njëfandiku ci njëfandiku sukkandiku nañu ci kontak ci v0.1.
  • AICL mooy digal bu protokol — du wóolu ne sosiete AI yi dinañu fey.
  • Conformite ci fey, impo, ak yoonu alal mëkkuñu ci dayo bu brouyon bii.
  • Format yu token ak wërsëgu dugub yi eksperimantal lañu te man nañu soppeeku.
  • 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.

Nota ci tur wi

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.