AICL — Omuzingo gw'Obuyisensi bw'Ebirimu bya AI
Layisensi y'Ebirimu bya AI / Omuzingo gw'Obuyisensi bw'Ebirimu bya AI
Kifuula eddembe erirangiddwa okuba obuyisensi obuyinza okukolebwa: okusaba omuwendo, okusasula, okukakasa, okwekenneenya, okuggyawo.
01 · Amakulu
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 · Ekigendererwa
- Fuula endagiriro z'eddembe akatale k'obuyisensi akakola, mu kifo ky'okuba yintaneeti eya ye/nedda okuggulwa/okuggalwa.
- Tongoza omutendera ogw'okuva ku kyuma okutuuka ku kyuma: zuula polisi → saba omuwendo → funa layisensi → kozesa → kenneenya.
- Kuuma okusasula kwa AI ez'obwannannyini nga kukomereddwa: ttegeka ry'ensimbi, ebipimo by'okukkiriza, token ezikwatagana ne kyekusaba, n'endagiriro z'okwekenneenya ezijjuvu.
- Wa abawaayi b'ebirimu ekkubo ery'okufuna empeera awatali kuggalira mikutu gyabwe eri AI.
03 · Ekipimo
Ekitabo kya Layisensi — Emitendera gy'Ebibinja by'Eddembe n'Ebbeeyi n'Ebisaanidde
Endagiriro za Kusaba Omuwendo / Kusasula / Kukakasa / Kuggyawo
Token za Layisensi Ezisiimiddwa Ezikwatagana n'Oyo Asaba, Ekipimo, n'Ekiseera
Endagiriro z'Okukozesa n'Endagiriro z'Okwekenneenya
Okukolagana kwa HTTP 402 "Okusasula Kwetaagisa"
Amateeka g'Obukuumi: AI tekikwata butereevu ku data ya kaadi, ebipimo by'okukkiriza kw'omuntu
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 · Ekyokulabirako ekisomeka za makina
Layisensi z'Omukutu Guno Zennyini — /.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 · Ebisaanyizo
- Omukutu guno teguddukanya mulyango gwa kusasula; layisensi ez'obusuubuzi ziri ku kutukwatagana mu v0.1.
- AICL nteekateeka ya protocol — teyeeyimirira nti kkampuni za AI zijja kusasula.
- Okugoberera amateeka g'okusasula, omusolo, n'amateeka g'ensimbi biri ebweru w'ekipimo ky'enteekateeka eno.
- Enkola za token n'amakulu g'endagiriro biri ku kugezesa era biyinza okukyuka.
- 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.
Ekiwandiiko ky'amannya
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.