Hopp til innhold
AGIRight.org

AICL — AI-innholdslisensieringslag

AI Content License / AI-innholdslisensieringslag

Gjør deklarerte rettigheter om til eksekverbar lisensiering: tilby, betal, verifiser, revider, tilbakekall.

Draft v0.1.1 Skjema ↓

01 · Definisjon

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 · Formål

  • Gjør rettighetsdeklarasjoner om til et fungerende lisensieringsmarked i stedet for et binært åpent/lukket nett.
  • Standardiser maskin-til-maskin-flyten: oppdag policy → be om tilbud → lisensier → bruk → revider.
  • Hold agentiske betalinger avgrenset: budsjetter, godkjenningsterskler, forespørselsbundne tokener, fullstendige revisjonslogger.
  • Gi innholdsleverandører en vei til kompensasjon uten å stenge nettstedene sine for AI.

03 · Omfang

00

Lisenskatalog — nivåer av rettighetspakker med priser og vilkår

01

Endepunkter for tilbud / betaling / verifisering / tilbakekalling

02

Signerte lisenstokener bundet til forespørrer, omfang og tid

03

Brukslogger og revisjonsspor

04

Interoperabilitet med HTTP 402 «Payment Required»

05

Sikkerhetsregler: ingen AI-håndtering av rå kortdata, menneskelige godkjenningsterskler

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 · Maskinlesbart eksempel

Dette nettstedets egne lisenser — /.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 · Begrensninger

  • Dette nettstedet driver ingen betalingsportal; kommersielle lisenser er kontaktbaserte i v0.1.
  • AICL er et protokollforslag — det garanterer ikke at AI-selskaper vil betale.
  • Betalingsregelverk, skatt og finansiell regulering faller utenfor omfanget av dette utkastet.
  • Tokenformater og endepunktsemantikk er eksperimentelle og kan endres.
  • 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.

Merknad om navngiving

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.