AICL — Muraḓo wa Mulanga wa Zwiṅwalwa zwa AI
Laisenisi ya Zwiṅwalwa zwa AI / Muraḓo wa Mulanga wa Zwiṅwalwa zwa AI
I shandukisa pfanelo dzo ḓivhadzwaho dza vha mulanga une wa shuma: khumbelo, mbadelo, u ṱolisisa, u ṱolwa, u dzhiela fhasi.
01 · Ṱhalutshedzo
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 · Ndivho
- Shandukisa u ḓivhadza ha pfanelo u vha bindu ḽa laisenisi ḽine ḽa shuma, hu si webu ya ee/hai ya u vulea kana u valwa.
- Ita uri tshimbila tsha mishini u ya kha mishini tshi vhe tsho lugaho: u wana mulayo → u humbela khumbelo → laisenisi → u shumisa → u ṱolwa.
- Vhulunga mbadelo dza vhathomi dzo vhewaho miringo: bajeti, miringo ya u tendelwa, token dzo tandwaho kha khumbelo, na dziredzhisiṱara dzo ḓalaho dza u ṱolwa.
- Ṋea vhaṋei vha zwiṅwalwa nḓila ya u wana mbadelo hu si na u valela AI kha webu dzavho.
03 · Mukovhe
Bugu ya laisenisi — maga a zwikwama zwa pfanelo zwi na ndugelo na milayo
Miṋe ya khumbelo / mbadelo / u ṱolisisa / u dzhiela fhasi
Token dza laisenisi dzo saenwaho dzo tandwaho kha muvhudzisi, mukovhe, na tshifhinga
Dziredzhisiṱara dza u shumiswa na dza u ṱolwa
U tshimbidzana na HTTP 402 "Mbadelo yo Ṱoḓea"
Milayo ya tsireledzo: AI a i fari data ya khadi ya vhukuma, miringo ya u tendelwa nga vhathu
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 · Tsumbo ine mishini ya kona u i vhala
Laisenisi dza webu heyi — /.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 · Milingo
- Webu heyi a i shumisi tshiṅwe tsha mbadelo; laisenisi dza bindu dzi tou ṱoḓa kwamano kha v0.1.
- AICL ndi tsivhudzo ya porotokholo — a i fulufhedzisi uri zwikwata zwa AI zwi ḓo lifha.
- U tevhedzwa ha mbadelo, mutshelo, na milayo ya masheleni a zwi ngomu ha mukovhe wa tshipangelo hetshi.
- Tshivhumbeo tsha token na ṱhalutshedzo dza muṋe wa khumbelo ndi zwa ndingelo nahone zwi nga shanduka.
- 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.
Ndaela ya dzina
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.