Langsung dhateng isi
AGIRight.org

AICL — Lapisan Lisensi Konten AI

Lisensi Konten AI / Lapisan Lisensi Konten AI

Ngowahi hak ingkang dipundeklarasiaken dados lisensi ingkang saged dipunlampahi: penawaran, bayar, verifikasi, 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 · Ancas

  • Ngowahi deklarasi hak dados pasar lisensi ingkang saged mlampah, tinimbang web binér mbuka/katutup.
  • Menstandarkaken alur mesin-dhateng-mesin: manggihaken kabijakan → nyuwun penawaran → lisensi → panganggé → audit.
  • Njaga pambayaran agentik supados tetep kawatesan: anggaran, ambang persetujuan, token ingkang kaiket kaliyan panyuwunan, log audit lengkap.
  • Maringi panyedhiya konten margi dhateng kompensasi tanpa nutup situsipun dhateng AI.

03 · Cakupan

00

Katalog lisensi — tataran paket hak mawi reregan saha sarat

01

Endpoint penawaran / bayar / verifikasi / batal

02

Token lisensi ingkang dipuntandhatangani, kaiket kaliyan panyuwun, cakupan, saha wekdal

03

Log panganggé saha jejak audit

04

Interoperabilitas kaliyan HTTP 402 “Payment Required”

05

Aturan keamanan: AI mboten kepareng nyekel data kertu mentahan, ambang persetujuan manungsa

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 · Tuladha ingkang Saged Dipunwaos Mesin

Lisensi situs menika piyambak — /.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 · Watesan

  • Situs menika mboten ngoperasikaken gerbang pambayaran; lisensi komersial mawi kontak ing versi v0.1.
  • AICL minangka usulan protokol — mboten njamin bilih perusahaan AI badhé mbayar.
  • Kepatuhan pambayaran, pajeg, saha regulasi finansial ing sanjabaning cakupan rancangan menika.
  • Format token saha makna endpoint taksih eksperimental saha saged owah.
  • 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.

Cathetan Panyebutan

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.