AICL — Kouch Lisans Konteni AI
Lisans Konteni AI / Kouch Lisans Konteni AI
Transform drwa deklare an lisans exekitab: devi, peye, verifye, odit, anile.
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 · Objektif
- Konverti deklarasion drwa an enn marse lisans ki marse, olie enn web biner ouver/ferme.
- Standardiz sikwi masinn-a-masinn: dekouver politik → demann devi → lisans → servi → verifye.
- Gard peman agent limite: bidze, limit apruvasion, token atache-a-demand, rejis odit konplet.
- Donn founiser konteni enn chemin ver konpansasion san ferm zot sit ar AI.
03 · Etandi
Katalog lisans — nivo pake drwa avek pri ek kondision
Endpoint devi / peye / verifye / anile
Token lisans siyen, atache ar demander, etandi, ek letan
Rejis lizaz ek pis odit
Enteroperabilite HTTP 402 «Peman Bizin»
Regleman sekirite: AI pa manipile done bri kart, limit apruvasion imin
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 · Exanp lizib-pou-masinn
Prop lisans sa sit-la — /.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
- Sa sit-la pa opere enn pòrtay peman; lisans komersyal base lor kontakte-nou dan v0.1.
- AICL se enn proposision protokol — li pa garanti ki bann lantropriz AI pou peye.
- Konformite peman, tax, ek regilasion finansyer andeor letandi sa brouyon-la.
- Format token ek sinifikasion endpoint experimantal ek kapav sanze.
- 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.
Not lor apelasion
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.