AICL — I Kapan Lisensian AI Kontenido
Lisensia AI Kontenido / I Kapan Lisensian AI Kontenido
Ha kombietti i diritchu siha ni ma deklåra para lisensiasion ni siña ma ripela: kotasion, apas, beripika, awdit, rebokasion.
01 · Definision
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 · Propósito
- Kombietti i deklarasion siha put diritchu para un maketan lisensia ni fuma'chocho', ti ha' un web binaria put mababa/ma tåpa'.
- Estandardisa i flujo måkina-para-måkina: fuma'sodda' polisi → fuma'gagao kotasion → lisensia → fina'usa → awdit.
- Fuma'sigi i apas siha put ehente gaige límite: badyet, límiten aprobasion, token siha ni ma amåtta gi finaisen, yan fulwan na rehistron awdit.
- Nå'e i providot siha put kontenido un chalan para konpensasion, sin fuma'tåpa' i sitioñiha kontra AI.
03 · Alkånse
Katalogon lisensia — nibet siha put pakete diritchu yan presiu yan kondision
Endpoint siha put kotasion / apas / beripika / rebokasion
Token siha put lisensia ni ma firma, ma amåtta gi i taotao fuma'gagao, i alkånse, yan i tiempo
Rehistron fina'usa yan rehistron awdit
Fina'chocho'-tugeta yan HTTP 402 "Nesesita Apas"
Lai siha put seguridåt: taya' AI fuma'aksehon detåyen kaddu, límiten aprobasion ni taotao
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 · Ehemplo ni matatataitai ni måkina
I mismo lisensia siha blong este na sitio — /.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 · Limitasion siha
- Este na sitio ti ha operera un gateway put apas; i lisensia siha komersiåt, basao gi kontåktu gi v0.1.
- AICL un propuesta put protokolo — ti ha garantisa na i kompaniña AI siha, bai u man apåse.
- I kumplimento put apas, taks, yan regulasion finansiåt, gaige gi sanhiyong i alkånse blong este na boradot.
- I fotma siha put token yan i sinifikasion blong endpoint, esperimentåt yan siña ma kambia.
- 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.
Nota put i na'an
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.