AICL — Legora la Laesense ya Diteng tša AI
Laesense ya Diteng tša AI / Legora la Laesense ya Diteng tša AI
E fetoša ditokelo tše di phatlaladitšwego go ba laesense ye e phethagatšwago: tekanyo, tefo, go netefatša, tlhahlobo, go phumola.
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 · Morero
- Fetoša diphatlalatšo tša ditokelo go ba mmaraka wa laesense wo o šomago go e na le inthanete ya ee/aowa ya go bulega/go tswalwa.
- Beakanya tshepedišo ya metšhene-go-metšhene: go hwetša pholisi → go kgopela tekanyo → laesense → tirišo → tlhahlobo.
- Boloka ditefo tša baemedi di beetšwe mellwane: ditekanyetšo, mellwane ya tumelelo, di-token tše di golegilwego kgopelong, dipego tša tlhahlobo tše di feletšego.
- Nea bafani ba diteng tsela ya moputso ntle le go tswalela mafelo a bona go AI.
03 · Tekanyo
Katalogo ya laesense — maemo a diphuthelwana tša ditokelo ka ditheko le maemo
Di-endpoint tša tekanyo / tefo / go netefatša / go phumola
Di-token tša laesense tše di golegilwego go mokgopedi, tekanyo, le nako
Dipego tša tirišo le mekgokolodi ya tlhahlobo
Go sepelisana ga HTTP 402 "Tefo e a Nyakega"
Melawana ya polokego: AI ga e swanela go swara tshedimošo ya karata e tala, mellwane ya tumelelo ya batho
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 balwago ke metšhene
Dilaesense tša lefelo le ka bolena — /.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 · Mellwane
- Lefelo le ga le šome sepheo sa tefo; dilaesense tša kgwebo di theilwe godimo ga kgokagano ka fase ga v0.1.
- AICL ke tšhišinyo ya phrothokholo — ga e netefatše gore dikhamphani tša AI di tla lefa.
- Go latela melao ya tefo, motshelo, le taolo ya ditšhelete ga di akaretšwe morolong wo.
- Mebopego ya token le moko wa endpoint ke tša teko gomme di ka fetoga.
- 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.
Ntlha ya leina
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.