AICL — AI ᑎᑎᖅᖃᑦ License-ᖃᕐᓂᕐᒧᑦ ᐃᓚᖔ
AI ᑎᑎᖅᖃᑦ License / AI ᑎᑎᖅᖃᑦ License-ᖃᕐᓂᕐᒧᑦ ᐃᓚᖏᑦ
ᓇᓗᓇᐃᖅᓯᒪᔪᓂᒃ ᐱᔪᓐᓇᐅᑎᓂᒃ ᐊᓪᓚᖑᖅᑎᑦᑐᖅ ᐊᑐᖅᑕᐅᔪᓐᓇᖅᑐᒧᑦ license-ᖃᕐᓂᕐᒧᑦ: quote, ᐊᑭᓕᖅ, ᐅᖃᖅ, audit, revoke.
01 · ᑐᑭᓯᐅᒪᓂᖓ
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 · ᑐᕌᖓᔭᖃᕐᓂᖓ
- ᐱᔪᓐᓇᐅᑎᑦ ᓇᓗᓇᐃᖅᓯᒪᓂᖏᑦ ᐊᓪᓚᖑᖅᑎᒍᒃ ᐊᑐᖅᑕᐅᔪᓐᓇᖅᑐᒥᒃ license-ᖃᕐᓂᕐᒧᑦ ᓂᐅᖅᕿᓂᖃᕐᓂᕐᒧᑦ, ᒪᕐᕉᖏᑦᑐᒥᒃ ᐊᒻᒪᖅᑐᖅ/ᒪᑐᓯᒪᔪᖅ web-ᒥᒃ ᑕᓃᓐᓇᐅᙱᑦᑭᐊᖅ.
- Standardize-ᑎᒍᒃ ᖃᕆᐊᓴᒥᑦ-ᖃᕆᐊᓴᒧᑦ ᐊᖅᖁᖅᑖᖓ: ᒪᓕᒐᖅ ᓇᓂᓴᒍᒃ → quote ᐊᐱᖅᓱᒃ → license → ᐊᑐᖅᑎᒍᒃ → audit.
- Agent-ᒃᑯᑦ ᐊᑭᓕᖅᑎᑦᓯᓃᑦ ᑭᓪᓕᖃᖅᑎᑕᐅᒋᑦ: ᑮᓇᐅᔾᔭᖁᑏᑦ, ᐊᖏᖅᑕᐅᓂᖅ ᑭᓪᓕᖏᑦ, request-ᒧᑦ ᐊᑦᑕᕕᒋᔭᐅᔪᑦ token-ᒃᑯᑦ, ᑕᒪᐃᑕ audit log-ᒃᑯᑦ.
- ᑎᑎᖅᖃᑦ ᓴᖅᕿᔭᐃᔨᓄᑦ ᐊᖅᖁᖅᑕᐅᔪᒥᒃ ᐊᑭᓕᖅᑎᑕᐅᓯᒪᓂᐊᓄᑦ ᑐᓂᒋᑦ, ᓇᒻᒥᓂᒃ site-ᒥᓂᒃ AI-ᒧᑦ ᒪᑐᔪᖏᑦᑭᐊᖅ.
03 · Scope
License ᑲᑕᓗᒑ — ᐱᔪᓐᓇᐅᑎᑦ tier-ᒃᑯᑦ ᑲᑎᑎᑕᐅᔪᑦ ᐊᑭᑐᔮᖏᓐᓂᒃ ᓈᓚᐅᑎᒋᔭᐅᔪᖃᕐᓂᐊᖏᓐᓂᓪᓗ
Quote / ᐊᑭᓕᖅ / ᐅᖃᖅ / Revoke Endpoint-ᒃᑯᑦ
ᐊᑎᓕᐅᖅᑕᐅᓯᒪᔪᑦ License Token-ᒃᑯᑦ ᐊᐱᖅᓱᖅᑎᒧᑦ, Scope-ᒧᑦ, ᐊᒻᒪᓗ ᐅᓪᓗᓕᒫᖓᓄᑦ ᐊᑦᑕᕕᒋᔭᐅᔪᑦ
ᐊᑐᖅᑕᐅᓯᒪᓃᓪᓗ Log-ᒃᑯᑦ ᐊᒻᒪᓗ Audit Trail-ᒃᑯᑦ
HTTP 402 "Payment Required" ᐃᓚᖃᑦᑖᕐᓂᖅ
ᐊᑐᕈᓐᓇᕐᓂᖅ ᒪᓕᒐᕐᔪᐃᑦ: AI raw card ᑎᑎᖅᖃᓂᒃ ᐱᓕᕆᖃᙱᓐᓇᒥᒃ, ᐃᓄᐃᑦ ᐊᖏᖅᑕᐅᓂᕆᑦ ᑭᓪᓕᖏᑦ
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 · ᖃᕆᐊᓴᒃᑯᑦ ᐊᑐᖅᑕᐅᔪᓐᓇᖅᑐᖅ ᐊᔅᓯᓕᐊᖓ
ᐅᓇ Site-ᐅᑉ ᓇᒻᒥᓂᖅ License-ᒃᑯᑦ — /.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 · ᑭᓪᓕᖏᑦ
- ᐅᓇ site ᐊᑭᓕᖅᑎᑦᓯᓂᖅ gateway-ᒥᒃ ᐱᓕᕆᖃᙱᑦᑐᖅ; ᓂᐅᕕᕈᑎᒋᓗᒍ license-ᒃᑯᑦ ᐊᑦᑕᕕᒋᔭᐅᔪᓂᒃᑯᑦ v0.1-ᒥ.
- AICL protocol-ᒥᒃ ᐃᓱᒪᒋᔭᐅᔪᖅ — ᓇᓗᓇᐃᖅᓯᙱᑦᑐᖅ AI ᑲᒥᓯᐊᓇᖅᑐᐃᑦ ᐊᑭᓕᖅᑎᙱᓐᓇᒥᒃ.
- ᐊᑭᓕᖅᑎᑦᓯᓂᖅ ᓈᓚᙱᓐᓇᒥᖓᓂᒃ, tax-ᒃᑯᑦ, ᐊᒻᒪᓗ ᑮᓇᐅᔭᖅᑎᒍᑦ regulation ᐅᓇ draft-ᒥ scope-ᒥ ᐃᓚᐅᙱᑦᑐᑦ.
- Token format-ᒃᑯᑦ endpoint ᑐᑭᓯᖁᑎᖏᓪᓗ experimental-ᑐᑦ ᐊᓪᓚᖑᖅᑕᐅᓐᓇᖅᑐᓪᓗ.
- 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.
ᐊᑎᓕᐅᕈᑎᓄᑦ ᐅᖃᕐᓂᖅ
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.