AICL — Nivel da Licenziaziun da Cuntegn IA
Licenza da Cuntegn IA / Nivel da Licenziaziun da Cuntegn IA
Transferescha dretgs declarads en ina licenziaziun exequibla: offerta, pagament, verificaziun, revisiun, revocaziun.
01 · Definiziun
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 · Intent
- Transfurmar decleraziuns da dretgs en in martgà da licenziaziun funcziunabel, empè d'in web binar avert/serrà.
- Standardisar il flus da maschina a maschina: scuvrir la politica → dumandar in'offerta → licenziar → duvrar → revidar.
- Tegnair ils pagaments agentics limitads: budgets, sgols dad approvaziun, tokens liads a la dumonda, protocols cumplets da revisiun.
- Dar a purschiders da cuntegn ina via envers ina retribuziun senza serrar lur websites a la IA.
03 · Champ d'applicaziun
Catalog da licenzas — categorias da pachets da dretgs cun pretschs e cundiziuns
Endpoints per offerta / pagament / verificaziun / revocaziun
Tokens da licenza suttascrits, liads al dumandader, al champ d'applicaziun ed al temp
Protocols dad utilisaziun e tragects da revisiun
Interoperabilitad cun HTTP 402 «Payment Required»
Reglas da segirezza: nagina elavuraziun da datas grezzas da carta tras la IA, sgols dad approvaziun umana
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 · Exempel leschibel per maschinas
Las atgnas licenzas da quest website — /.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 · Limitaziuns
- Quest website n'exploitescha nagina porta da pagament; licenzas commerzialas sa basan sin contact en la versiun v0.1.
- L'AICL è ina proposta da protocol — ella na garantescha betg che las interpresas da IA paian.
- La conformità da pagament, taglias e regulaziun finanziala n'èn betg en il champ d'applicaziun da quest project.
- Formats da tokens e semantica dad endpoints èn experimentals e pon midar.
- 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.
Remartga davart il num
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.