Mo er a content
AGIRight.org

AICL — A AI Content Licensing Layer

A Klisiich er a AI Content / AI Content Licensing Layer

Mengedecheduch a declared rights el mo executable licensing: quote, pay, verify, audit, revoke.

Draft v0.1.1 Schema ↓

01 · A belkul

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 · A ngerechelel

  • Mengedecheduch a rights declarations el mo er a licensing market el sebechel a ureor, diak el di ua a binary open/closed web.
  • Standardize a machine-to-machine flow: ochotii a policy → oker a quote → license → ousbech → audit.
  • Ngeso a agentic payments el telbilel: budgets, approval thresholds, request-bound tokens, meklou el audit logs.
  • Ngeso a content providers a rael el mo er a compensation diak el kldibel a beluu er tir el kirel a AI.

03 · A rebetok

00

License catalog — tiers er a rights bundles loba prices me a llechul

01

A Quote / Pay / Verify / Revoke Endpoints

02

Signed license tokens el bound er a requester, scope, me a taem

03

Usage logs me a audit trails

04

HTTP 402 “Payment Required” interoperability

05

Safety rules: diak a AI el mo mengai a card data el meral, human approval thresholds

06

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 · A klausbech el machine-readable

A licenses er tia el beluu — /.well-known/aicl.json

/.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 · A telbilel

  • Tia el beluu a diak el meruul a payment gateway; a commercial licenses a contact-based er a v0.1.
  • A AICL a protocol proposal — diak el kmeed el kmo a AI companies a mo mengedecheduch.
  • Payment compliance, tax, me a financial regulation a diak chelsel a scope er tia el draft.
  • A token formats me a endpoint semantics a experimental e sebechel el mengedecheduch.
  • 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.

A subeded er a ngklel

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.