Langkau ke kandungan
AGIRight.org

AICL — Lapisan Pelesenan Kandungan AI

Lesen Kandungan AI / Lapisan Pelesenan Kandungan AI

Menukarkan hak yang diisytiharkan menjadi pelesenan boleh laksana: sebut harga, bayar, sahkan, audit, batal.

Draft v0.1.1 Skema ↓

01 · Definisi

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

  • Tukarkan deklarasi hak menjadi pasaran pelesenan yang berfungsi dan bukannya web binari terbuka/tertutup.
  • Piawaikan aliran mesin-ke-mesin: temui dasar → minta sebut harga → lesen → guna → audit.
  • Kekalkan pembayaran agentik dalam had: bajet, ambang kelulusan, token terikat permintaan, log audit yang lengkap.
  • Berikan penyedia kandungan laluan kepada pampasan tanpa perlu menutup laman mereka daripada AI.

03 · Skop

00

Katalog lesen — peringkat pakej hak dengan harga dan syarat

01

Titik akhir sebut harga / bayar / sah / batal

02

Token lesen bertandatangan yang terikat kepada pemohon, skop, dan masa

03

Log penggunaan dan jejak audit

04

Kesalinghubungan HTTP 402 "Payment Required"

05

Peraturan keselamatan: AI tidak mengendalikan data kad mentah, ambang kelulusan manusia

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 · Contoh boleh baca mesin

Lesen laman ini sendiri — /.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 · Batasan

  • Laman ini tidak mengendalikan get pembayaran; lesen komersial berasaskan hubungan terus dalam v0.1.
  • AICL ialah cadangan protokol — ia tidak menjamin bahawa syarikat AI akan membayar.
  • Pematuhan pembayaran, cukai, dan peraturan kewangan berada di luar skop draf ini.
  • Format token dan semantik titik akhir adalah eksperimen dan boleh berubah.
  • 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 penamaan

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.