Yi Ɖe Nuŋlɔŋlɔa Gbɔ Tẽ
AGIRight.org

AICL — AI Nuŋlɔŋlɔ Laesensnana Ƒe Akpa

AI Nuŋlɔŋlɔ Laesens / AI Nuŋlɔŋlɔ Laesensnana Ƒe Akpa

Trɔa gomekpɔkpɔ siwo woɖe gbeƒã wozua laesensnana si ate ŋu awɔ dɔ: biabia, fetu, dzesidede, dzodzro, gbɔyiyi.

Draft v0.1.1 Skema ↓

01 · Gɔmeɖeɖe

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 · Taɖodzinu

  • Trɔ gomekpɔkpɔwo ƒe gbeƒãɖeɖe wòazu asi si laesensnana ate ŋu awɔ dɔ le, ɖe "eʋu / etu" Wɛb tsɔtsɔ teƒe.
  • Wɔ ale be makina-yi-makina dɔwɔmɔ nasɔ gbe ɖeka: kpɔ sedede → bia asixɔxɔ → xɔ laesens → zã → dzro eme.
  • Na dɔwɔlawo ƒe fetu nanɔ seɖoƒe me: gaɖoɖowo, lɔlɔ̃nu seɖoƒewo, token siwo ku ɖe biabia ŋu, kple dzodzro-nuŋlɔɖi bliboawo.
  • Na mɔ nuŋlɔŋlɔ nalawo be woaxɔ fetu, wometu woƒe saetwo ɖe AI nu o.

03 · Nutsɔamedziɖoƒe

00

Laesens Katalɔg — gomekpɔkpɔ habɔbɔwo ƒe dzidziɖoƒewo kple asixɔxɔ kple kondisenwo

01

Biabia / Fetu / Dzesidede / Gbɔyiyi Endpointwo

02

Laesens Token Siwo Gbɔ Dzesi, Siwo Ku Ɖe Biabialaa, Nutsɔamedziɖoƒe, Kple Ɣeyiɣi Ŋu

03

Zazã-Nuŋlɔɖiwo Kple Dzodzro-Nuŋlɔɖiwo

04

HTTP 402 "Fetu Hiã" Dɔwɔɖekae

05

Dedienɔnɔ Sewo: AI mate ŋu akpɔ kad ƒe nyatakaka tẽ o, amegbetɔ ƒe lɔlɔ̃nu seɖoƒewo

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 · Kpɔɖeŋu si makina ate ŋu axlẽ

Saet Sia Ŋutɔ Ƒe Laesenswo — /.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 · Seɖoƒewo

  • Saet sia mewɔa fetu ʋɔtru aɖeke dɔ o; asitsatsa laesenswo to kadodo me le v0.1 me.
  • AICL nye protokɔl ɖaŋunɔnɔ ko — mele kakaɖe ɖem be AI kompaniwo axe fe o.
  • Fetu ƒe sewɔwɔ, adzɔ, kple ga ŋuti sewo mele drafi sia ƒe nutsɔamedziɖoƒe me o.
  • Token ƒomeviwo kple endpoint gɔmesese le dodokpɔ me eye woate ŋu atrɔ.
  • 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.

Nya tso ŋkɔdada ŋu

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.