AICL — Sosona Fanomezan-dalana Votoaty AI
Lisansa Votoaty AI / Sosona Fanomezan-dalana Votoaty AI
Mamadika ny zo nambara ho fanomezan-dalana azo ampiharina: tondro vidiny, fandoavana, fanamarinana, fanaraha-maso, fanafoanana.
01 · Famaritana
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 · Tanjona
- Mamadika ny fanambaran-jo ho tsena fanomezan-dalana azo ampiharina, fa tsy web roa lafiny (misokatra/mihidy) fotsiny.
- Manara-penitra ny fizotra eo amin'ny milina sy milina: mahita ny paikady → mangataka tondro vidiny → mahazo lisansa → mampiasa → manamarina.
- Ahazona voafetra ny fandoavam-bola ataon'ny agenta: teti-bola, fetran'ny fanekena, token mifamatotra amin'ny fangatahana, ary rakitry ny fanamarinana feno.
- Manome lalana mankany amin'ny valisoa ho an'ny mpanome votoaty, tsy manidy ny tranonkalany amin'ny AI.
03 · Velarana
Katalaogin-dalisa — ambaratongan'ny fitambaran-jo miaraka amin'ny vidiny sy ny fepetra
Endpoint fangatahana tondro vidiny / fandoavana / fanamarinana / fanafoanana
Token lisansa voasonia mifamatotra amin'ny mpangataka, ny velarana, ary ny fotoana
Rakitry ny fampiasana sy rakitry ny fanamarinana
Fifandraisan'ny HTTP 402 "Ilaina ny Fandoavam-bola"
Fitsipiky ny fiarovana: tsy mikarakara angon-tsora amin'ny karatra mihitsy ny AI, fetran'ny fanekena ataon'olombelona
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 · Ohatra azon'ny milina vakiana
Ny lisansa manokan'ity tranonkala ity — /.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 · Fetra
- Tsy mampiasa vavahady fandoavam-bola ity tranonkala ity; ny lisansa ara-barotra dia mifototra amin'ny fifandraisana amin'ny v0.1.
- Tolo-kevitra protokoly ny AICL — tsy miantoka fa handoa ny orinasa AI izany.
- Ivelan'ny velaran'ity volavolan-kevitra ity ny fanarahan-dalàna momba ny fandoavam-bola, ny hetra, ary ny fitsipiky ara-bola.
- Andrana ny endriky ny token sy ny hevi-dalan'ny endpoint ary mety hiova.
- 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.
Fanamarihana momba ny anarana
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.