AICL — Umqinga Welayisensi Yokuqukethwe kwe-AI
Ilayisensi Yokuqukethwe kwe-AI / Umqinga Welayisensi Yokuqukethwe kwe-AI
Iguqulela amalungelo aziswako abe lilayisensi elisebenzako: cela inani, khokha, qinisekisa, hlola, hoxisa.
01 · Incazelo
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 · Umnqopho
- Guqula iinzaziso zamalungelo zibe yimakethe yelayisensi esebenzako kunokuba newebhu ye-binary evulekileko/evaliweko.
- Yenza kufane umgudu we-mitjhini-kuya-emitjhini: fumana umthetho → cela inani → thola ilayisensi → sebenzisa → hlolwa.
- Gcina iinkhokhelo zama-ejenti zinemikhawulo: iibhajethi, imikhawulo yemvumo, iitokheni ezibotjhelelwe emcelweni, amarekhodi apheleleko wokuhlolwa.
- Nikela abanikeli bokuqukethwe indlela eya esikhokhisweni ngaphandle kokuvala amasayidi wabo ku-AI.
03 · Ibanga
Ikhathalogu Yamalayisensi — amazinga wamaqoqo wamalungelo anamanani nemibandela
Iindawo Zokucela Inani / Ukukhokha / Ukuqinisekisa / Ukuhoxisa
Iitokheni Zelayisensi Ezisayinilweko Ezibotjhelelwe Kumceli, Ibanga, Nesikhathi
Amarekhodi Wokusetjenziswa Kanye Neemzila Zokuhlolwa
Ukusebenzelana kwe-HTTP 402 “Kudingeka Ikhokhelo”
Imithetho Yokuvikeleka: Akukho i-AI Esebenza Ngedatha Yekhadi Eluhlaza, Imikhawulo Yemvumo Yomuntu
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 · Isibonelo esifundeka yimitjhini
Amalayisensi Wale Sayidi Ngokwayo — /.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 · Imikhawulo
- Le sayidi ayisebenzisi isango lokukhokha; amalayisensi wokuthengiselana asekelwe ekuthintaneni ku-v0.1.
- I-AICL sisiphakamiso sephrothokholo — ayiqiniseki bona amakampani we-AI azokhokha.
- Ukuthobela imithetho yeenkhokhelo, iintela, kanye nokulawulwa kwezezimali kungaphandle kwebanga leli drafu.
- Iifomethi zeetokheni neencazelo zeendawo zokuhlanganisa zisesengcoceni begodu kungenzeka zitjhugulule.
- 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.
Inothi lokuthiywa
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.