Spring na inhoud
AGIRight.org

AICL — Laag vir KI-inhoudlisensiëring

KI-inhoudlisensie / Laag vir KI-inhoudlisensiëring

Skakel verklaarde regte om in uitvoerbare lisensiëring: kwotasie, betaal, verifieer, oudit, herroep.

Draft v0.1.1 Skema ↓

01 · Definisie

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 · Doel

  • Skakel regteverklarings om in 'n werkbare lisensiëringsmark, in plaas van 'n binêre oop/geslote web.
  • Standaardiseer die masjien-na-masjien-vloei: ontdek beleid → versoek kwotasie → lisensieer → gebruik → oudit.
  • Hou agentiese betalings begrens: begrotings, goedkeuringsdrempels, versoek-gebonde tokens, volledige ouditstate.
  • Gee inhoudverskaffers 'n pad na vergoeding sonder om hul werwe vir KI te sluit.

03 · Omvang

00

Lisensiekatalogus — vlakke van regtebundels met pryse en voorwaardes

01

Eindpunte vir kwotasie / betaal / verifieer / herroep

02

Ondertekende lisensietokens gebonde aan versoeker, omvang, en tyd

03

Gebruikstate en ouditspore

04

HTTP 402 „Payment Required”-interoperabiliteit

05

Veiligheidsreëls: geen hantering van rou kaartdata deur KI nie, drempels vir menslike goedkeuring

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 · Masjienleesbare voorbeeld

Hierdie werf se eie lisensies — /.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 · Beperkings

  • Hierdie werf bedryf nie 'n betalingspoort nie; kommersiële lisensies is in v0.1 kontak-gebaseer.
  • AICL is 'n protokolvoorstel — dit waarborg nie dat KI-maatskappye sal betaal nie.
  • Betalingsnakoming, belasting, en finansiële regulering val buite die bestek van hierdie konsep.
  • Tokenformate en eindpunt-semantiek is eksperimenteel en kan verander.
  • 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.

Nota oor naamgewing

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.