Kālọk ñan Kontent
AGIRight.org

AICL — Layer in Laisin Kontent an AI

Laisin Kontent an AI / Layer in Laisin Kontent an AI

Ukot maroñ ko kar kwaḷọk ñan laisin emaroñ execute: quote, kōḷḷā, verify, audit, revoke.

Draft v0.1.1 Schema ↓

01 · Meḷeḷe

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 · Kōttōpar

  • Ukot kwaḷọk maroñ ko ñan juon market in laisin emaroñ jerbal, jab juon wēb binary in open/closed.
  • Standardize flow eo machine-to-machine: lo policy → kajjitōk quote → laisin → kōjerbal → audit.
  • Kōjparok kōḷḷā an agent ro bwe ren bound wōt: budget ko, threshold in kaṃool, token ko lukkuun ekkar ñan request, audit log ko weeppān.
  • Lewōj ñan ri-lewōj kontent juon iaḷ ñan compensation ejjeḷọk aer aikuj kilōk site ko aer ñan AI.

03 · Scope

00

Catalog in laisin — tier ko in maroñ bundle kōn oṇāān im condition

01

Endpoint ko ñan quote / kōḷḷā / verify / revoke

02

License token ko kar sain, lukkuun ekkar ñan requester, scope, im iien

03

Usage log ko im audit trail ko

04

Interoperability an HTTP 402 “Payment Required”

05

Kien safety: ejjeḷọk AI ej uwe kōn card data e ṃool, ewor threshold in kaṃool jān armej

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 · Waanjoñak machine-readable

License ko an site in make — /.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 · Kōṃad ko

  • Site in e jab operate juon payment gateway; commercial license ko rej contact-based ilo v0.1.
  • AICL ej juon protocol proposal — e jab kaṃool bwe AI company ko renaaj kōḷḷā.
  • Payment compliance, tax, im financial regulation rej ilikin scope an draft in.
  • Token format ko im endpoint semantics rej experimental im remaroñ oktak.
  • 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.

Kōjjeḷā kōn etan

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.