Liigu sisu juurde
AGIRight.org

AICL — AI-sisu litsentsimise kiht

AI sisulitsents / AI sisu litsentsimise kiht

Muudab deklareeritud õigused täidetavaks litsentsimiseks: hinnapakkumine, maksmine, kontrollimine, auditeerimine, tühistamine.

Draft v0.1.1 Skeem ↓

01 · Definitsioon

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 · Eesmärk

  • Muuta õiguste deklaratsioonid toimivaks litsentsituruks binaarse avatud/suletud veebi asemel.
  • Standardida masinatevaheline voog: poliitika avastamine → hinnapakkumise küsimine → litsentsimine → kasutamine → auditeerimine.
  • Hoida agentide maksed piiratuna: eelarved, kinnitamise lävendid, päringuga seotud tokenid, täielikud auditilogid.
  • Anda sisupakkujatele tee hüvitiseni, ilma et nad peaksid oma saidid AI-le sulgema.

03 · Ulatus

00

Litsentsikataloog — õiguste paketiastmed koos hindade ja tingimustega

01

Hinnapakkumise / maksmise / kontrollimise / tühistamise lõpp-punktid

02

Allkirjastatud litsentsitokenid, mis on seotud päringu esitaja, ulatuse ja ajaga

03

Kasutuslogid ja auditijäljed

04

HTTP 402 „Payment Required” koostalitlusvõime

05

Ohutusreeglid: AI ei tohi käidelda töötlemata kaardiandmeid, inimese kinnituse lävendid

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 · Masinloetav näide

Selle saidi enda litsentsid — /.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 · Piirangud

  • See sait ei halda maksevärava; kommertslitsentsid põhinevad versioonis v0.1 kontaktil.
  • AICL on protokolliettepanek — see ei taga, et AI-ettevõtted maksavad.
  • Maksete vastavus, maksustamine ja finantsregulatsioon jäävad selle eelnõu käsitlusalast välja.
  • Tokenite vormingud ja lõpp-punktide semantika on eksperimentaalsed ning võivad muutuda.
  • 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.

Nimetamise märkus

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.