AICL — Haen Drwyddedu Cynnwys AI
Trwydded Cynnwys AI / Haen Drwyddedu Cynnwys AI
Yn troi hawliau datganedig yn drwyddedu gweithredadwy: dyfynbris, talu, gwirio, archwilio, dirymu.
01 · Diffiniad
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 · Diben
- Trosi datganiadau hawliau'n farchnad drwyddedu weithredadwy yn lle gwe agored/caeedig ddeuaidd.
- Safoni'r llif peiriant-i-beiriant: darganfod polisi → gofyn am ddyfynbris → trwyddedu → defnyddio → archwilio.
- Cadw taliadau asiantaidd wedi'u ffinio: cyllidebau, trothwyon cymeradwyo, tocynnau sy'n gaeth i'r cais, cofnodion archwilio llawn.
- Rhoi llwybr i ddarparwyr cynnwys tuag at ddigolledu heb gau eu safleoedd i AI.
03 · Cwmpas
Catalog trwyddedau — haenau bwndeli hawliau â phrisiau ac amodau
Pwyntiau terfyn dyfynbris / talu / gwirio / dirymu
Tocynnau trwydded wedi'u llofnodi, yn gaeth i'r ceisiwr, y cwmpas, a'r amser
Cofnodion defnydd a llwybrau archwilio
Rhyngweithrededd HTTP 402 “Payment Required”
Rheolau diogelwch: ni chaiff AI drin data cerdyn crai, trothwyon cymeradwyo dynol
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 · Enghraifft ddarllenadwy gan beiriannau
Trwyddedau'r safle hwn ei hun — /.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 · Cyfyngiadau
- Nid yw'r safle hwn yn gweithredu porth talu; mae trwyddedau masnachol yn seiliedig ar gyswllt yn v0.1.
- Cynnig protocol yw AICL — nid yw'n gwarantu y bydd cwmnïau AI yn talu.
- Mae cydymffurfiaeth talu, treth, a rheoleiddio ariannol y tu allan i gwmpas y drafft hwn.
- Mae fformatau token a semanteg pwynt terfyn yn arbrofol ac yn gallu newid.
- 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.
Nodyn enwi
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.