AICL — Tikina ni Laiseni ni iYaya AI
Laiseni ni iYaya AI / Tikina ni Laiseni ni iYaya AI
Vakasautaka na dodonu e vakatakilai me laiseni e rawa ni cakacaka taki: taro isau, saumi, vakadeitaki, dikevi, vakawaqavi.
01 · iVakamacala
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 · Inaki
- Vakasamataka na ivakatakila ni dodonu me maketi ni laiseni e cakacaka, ka sega ni dua ga na web dola/sogo.
- Vakadodonutaka na sala mai masini ki masini: kunea na policy → taro na isau → laiseni → vakayagataki → dikevi.
- Maroroya na saumi vakaagent me vakayalataki: ilavo e vauci, iyalayala ni ivakadonui, token e vauci ki na taro, kei na ivakarau ni dikevi taucoko.
- Solia vei ira era vakarautaka na iyaya e dua na sala ki na isau, ka sega ni sogo na nodra vasite ki na AI.
03 · Yalava
Katalog ni Laiseni — tikina ni dodonu vakaikoya kei na isau kei na veiyalayalataki
Endpoint ni Taro Isau / Saumi / Vakadeitaki / Vakawaqavi
Token ni Laiseni e Sainitaki, Vauci ki na Dauvakatoro, Yalava, kei na Gauna
Ivakarau ni Vakayagataki kei na Sala ni Dikevi
Kena Cakacaka Vata na HTTP 402 “e Gadreva na Saumi”
Lawa ni Taqomaki: e sega ni rawa ni cakava na AI na itukutuku dina ni kata, iyalayala ni ivakadonui vakaitamata
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 · Ivakaraitaki e Rawa ni Wilikitaki ena Masini
Na Laiseni Dodonu ni Vasite Oqo — /.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 · iYalayala
- Na vasite oqo e sega ni cakava e dua na gateway ni saumi; na laiseni vakabisinisi era yavutaki ena veitaratara ena v0.1.
- Na AICL e dua na ivakarau ni protocol — e sega ni vakadeitaka ni na saumi na kamipani AI.
- Na veiyalayalataki ni saumi, takisi, kei na lawa vakailavo e sega ni loma ni yalava ni draft oqo.
- Na ivakarau ni token kei na ibalebale ni endpoint e vakatovolei tiko ka rawa ni veisautaki.
- 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.
iVakasala ni Yaca
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.