AICL — Lapisan Lisensi Kontén AI
Lisensi Kontén AI / Lapisan Lisensi Kontén AI
Ngarobih hak anu didéklarasikeun janten lisensi anu tiasa dilaksanakeun: panawaran, pambayaran, verifikasi, audit, pambatalan.
01 · Definisi
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 · Tujuan
- Ngarobih déklarasi hak janten pasar lisensi anu tiasa jalan, tinimbang wéb binér muka/tutup.
- Standarisasi alur mesin-ka-mesin: manggihan kabijakan → nyuhunkeun panawaran → lisensi → pamakéan → audit.
- Jaga pambayaran agéntik tetep diwatesan: anggaran, ambang persetujuan, token anu kaiket kana paménta, log audit anu lengkep.
- Masihan panyadia kontén jalan kana kompénsasi tanpa kedah nutup situsna ti AI.
03 · Ruang lingkup
Katalog lisensi — tingkat pakét hak kalayan harga sareng syarat
Titik ahir panawaran / mayar / mariksa / mambatalkeun
Token lisensi anu ditandatanganan sareng kaiket kana anu nyuhunkeun, ruang lingkup, sareng waktos
Log pamakéan sareng jejak audit
Interoperabilitas kalayan HTTP 402 “Payment Required”
Aturan kaamanan: AI teu kénging nyekel data kartu mentah, aya ambang persetujuan manusa
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 · Conto anu tiasa dibaca ku mesin
Lisensi situs ieu sorangan — /.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 · Watesan
- Situs ieu teu ngoperasikeun gerbang pambayaran; lisensi komérsial dina v0.1 dumasar kontak.
- AICL mangrupa usulan protokol — teu ngajamin yén pausahaan AI bakal mayar.
- Kapatuhan pambayaran, pajeg, sareng régulasi kauangan saluareun ruang lingkup draf ieu.
- Format token sareng makna titik ahir mangrupa ékspérimén sareng tiasa robih.
- 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.
Catetan ngaran
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.