AICL — Urwego rwo Gutanga Uruhushya ku Birimwo vy'Ikoranabwenge
Uruhushya rw'Ibirimwo vy'Ikoranabwenge / Urwego rwo Gutanga Uruhushya ku Birimwo vy'Ikoranabwenge
Guhindura uburenganzira bwamenyekanishijwe bukaba uruhushya rushobora gushirwa mu ngiro: gusaba igiciro, kwishura, kugenzura, kugenzura, gukuraho.
01 · Insobanuro
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 · Intumbero
- Guhindura itangazo ry'uburenganzira kikaba isoko ry'uruhushya rikora, aho kuguma ku rubuga rw'ego-oya rufunze/rugaragara.
- Gutunganya mu buryo bumwe ikoranire ryo hagati y'imashini n'izindi: kuronka amabwiriza → gusaba igiciro → kuronka uruhushya → gukoresha → kugenzura.
- Gucungera kwishura kw'aba ejenti mu mbibe: amafaranga ateganijwe, imbibe z'ukwemera, tokene zifatanye n'ibisabwa, ivyandikwa vy'igenzura vyuzuye.
- Guha abatanga ibirimwo inzira yo kuronka ingurane, ata guhagarika imbuga zabo ku ikoranabwenge.
03 · Ubugari
Urutonde rw'uruhushya — ibipimo vy'ivyegeranyo vy'uburenganzira hamwe n'ibiciro n'ibisabwa
Aho usaba igiciro / ukwishura / ugupima / ugukuraho uruhushya
Tokene z'uruhushya zifise umukono, zifatanye n'uwasabye, ubugari, n'igihe
Ivyandikwa vy'Ikoreshwa n'Ivyandikwa vy'Igenzura
Ihuriro rya HTTP 402 „Ivyishurwa Bisabwa”
Amabwiriza y'umutekano: ikoranabwenge ntikigomba gukoraho amakuru y'ikarata mbisi, imbibe z'ukwemera kw'abantu
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 · Akarorero gasomwa n'imashini
Uruhushya rw'iyi urubuga bwite — /.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 · Imbibe
- Iyi urubuga ntirukoresha uburyo bwo kwishura; uruhushya rwo mu bucuruzi ni urw'ukuvugana muri v0.1.
- AICL ni ivyifuzo vy'iporotokole — ntibitegekanya ko amashirahamwe y'ikoranabwenge azokwishura.
- Ukurikizwa kw'amabwiriza y'ukwishura, imisoro, n'itegeko ry'amahera ntibiri muri iyi nyandiko itarahera.
- Imiterere ya tokene n'insobanuro y'aho hasakwa biracari mu kigeragezo kandi birashobora guhinduka.
- 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.
Icitonderwa ku mazina
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.