Derbasî naverokê bibe
AGIRight.org

AICL — Qata Lîsanskirina Naveroka AI

Lîsansa Naveroka AI / Qata Lîsanskirina Naveroka AI

Mafên daxuyandî vediguherîne lîsanskirineke pêkanbar: bihadan, dravdan, verastkirin, teftîş, betalkirin.

Draft v0.1.1 Şema ↓

01 · Pênase

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

  • Daxuyaniyên mafan bike bazareke lîsanskirinê ya karebar, li şûna webeke binar a vekirî/girtî.
  • Herikîna makîne-bi-makîne standard bike: polîtîkayê vedît → bihayê bipirse → lîsans → bikar bîne → teftîş bike.
  • Dravdana ajanan sînordar bihêle: budce, senga pejirandinê, tokenên girêdayî daxwazê, tomarên teftîşê yên temam.
  • Ji dabînkerên naverokê re riyeke tezmînatê bide, bêyî ku malperên wan li ber AI werin girtin.

03 · Berfirehî

00

Katalogê lîsansê — astên pakêtên mafan bi biha û mercan

01

Xalên dawî yên bihadayîn / dravdan / verastkirin / betalkirin

02

Tokenên lîsansê yên îmzekirî, girêdayî daxwazkar, berfirehî, û dem

03

Tomarên bikaranînê û şopên teftîşê

04

Hevkariya HTTP 402 „Dravdan Pêwîst e”

05

Rêzikên ewlehiyê: AI daneyên xav ên kartê nagire dest, sengên pejirandina mirovan

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 · Mînaka makîne-xwendbar

Lîsansên vê malperê bi xwe — /.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 · Sînorkirin

  • Ev malper dergeheke dravdanê naxebitîne; lîsansên bazirganî di v0.1 de li ser bingeha têkiliyê ne.
  • AICL pêşniyareke protokolê ye — garantî nade ku pargîdaniyên AI ê bidin.
  • Lihevhatina dravdanê, bac, û rêziknameya aborî ji berfirehiya vê pêşnivîsê derve ne.
  • Formatên tokenê û wateya xalên dawî ezmûnî ne û dikarin biguherin.
  • 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 navlêkirinê

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.