AICL — Xiphandzo xo Nyika Tilayisense ta Kontenti ya AI
Layisense ya Kontenti ya AI / Xiphandzo xo Nyika Tilayisense ta Kontenti ya AI
Hundzula mfanelo leyi voxiweke yi va tilayisense leti tirhaka: xiavo, nkhokhelo, ku kambela, audit, ku susa.
01 · Nhlamuselo
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 · Xikongomelo
- Hundzula swiboxo swa mfanelo swi va makete yo tirha ya tilayisense, ematshan'weni ya wepu leyi nga ni "pfulekile kumbe pfarilwe" ntsena.
- Endla xilaveko xo fambisana exikarhi ka matšhini na matšhini: ku kuma pholisi → ku kombela xiavo → layisense → ku tirhisa → audit.
- Hlayisa tinkhokhelo ta agent ti pimiwile: mibuxo, minkoma ya mpfumelelo, tokheni leti bohiweke eka xikombelo, na rhekhodo ra audit ra ku helela.
- Nyika vahumesi va kontenti ndlela ya ku hakheriwa handle ko pfarela masayiti ya vona eka AI.
03 · Nkoma
Nxaxamelo wa Tilayisense — swiyenge swa maphaka ya mfanelo swi na tinani na swiyimo
Tindhawu ta Xiavo / Nkhokhelo / Ku Kambela / Ku Susa
Tokheni ta layisense leti sayiniweke leti bohiweke eka muteki, nkoma, na nkarhi
Rhekhodo ra ku tirhisiwa na rhekhodo ra audit
Ku fambelana ni HTTP 402 "Payment Required"
Milawu ya ku sirheleka: ku hava AI leyi tirhisaka vuxokoxoko byo tiya bya khadi, minkoma ya mpfumelelo wa vanhu
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 · Xikombiso lexi Hlayekaka hi Matšhini
Tilayisense ta sayiti leyi hi yoxe — /.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 · Minkoka
- Sayiti leyi a yi tirhisi xitirhisiwa xa nkhokhelo; tilayisense ta mabindzu ti fambisiwa hi vulavurisano eka v0.1.
- AICL i xiboxo xa protocol — a yi tiyisisi leswaku tikhamphani ta AI ti ta hakela.
- Ku landzeleriwa ka nawu wa nkhokhelo, tibelo, na nawu wa timali a swi katsiwi eka drafiti leyi.
- Mafomati ya token na tinhlamuselo ta ndhawu i swa xikombiso naswona swi nga cinca.
- 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.
Xitsundzuxo xa Vito
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.