AICL — Lera la Dilaesense tsa Diteng tsa AI
Laesense ya Diteng tsa AI / Lera la Dilaesense tsa Diteng tsa AI
E fetola litokelo tse boletsweng hore e be dilaesense tse sebetsang: theko, tefo, netefatso, tlhahlobo, ho hlakola.
01 · Tlhaloso
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 · Sepheo
- Fetola diboitsebiso tsa litokelo hore e be mmaraka wa dilaesense o sebetsang, ho e-na le Web e le nngwe kapa tjhe e bulehileng kapa e koetsweng.
- Etsa hore metsamao ya mochini-ho-mochini e be ya kamehla: fumana leano → kopa theko → laesense → sebedisa → hlahlobo.
- Boloka ditefo tsa di-agent di meetswe: ditekanyetso, meedi ya tumello, di-token tse tlamanang le kopo, direkoto tse felletseng tsa tlhahlobo.
- Fa bafani ba diteng tsela ya ho fumana moputso ntle le ho koala disebaka tsa bona ho AI.
03 · Bophara
Katalogo ya Dilaesense — mekgahlelo ya diphutheloana tsa litokelo tse nang le ditheko le dipehelo
Li-endpoint tsa Theko / Tefo / Netefatso / Ho Hlakola
Di-token tsa Laesense tse Saenilweng tse Tlamanang le Mokopi, Bophara, le Nako
Direkoto tsa Tshebediso le Ditsela tsa Tlhahlobo
Kopano ya HTTP 402 ‘Payment Required’
Melawana ya Polokeho: AI ha e sebedise data ya karete e sa sireletsehang, meedi ya tumello ya motho
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 · Mohlala o balehang ke mochini
Dilaesense tsa Sebaka sena — /.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 · Meeli
- Sebaka sena ha se sebedise kgoro ya tefo; dilaesense tsa kgwebo li itshetlehile ho ho ikopanngwa ho v0.1.
- AICL ke tlhahiso ya protokolo — ha e netefatse hore difeme tsa AI di tla lefa.
- Ho latela melawana ya tefo, lekgetho, le taolo ya ditjhelete ho ka ntle ho bophara ba moralo ona.
- Mefuta ya token le moelelo wa endpoint ke tsa teko mme di ka fetoha.
- 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.
Tlhaloso ya Lebitso
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.