Ruka hadi kwenye contenu
AGIRight.org

AICL — Safu ya Lisansi ya Contenu ya IA

Lisansi ya Contenu ya IA / Safu ya Lisansi ya Contenu ya IA

Inabadilisha haki zilizotamkwa kuwa lisansi inayotekelezeka: bei, malipo, uhakiki, ukaguzi, ubatilishaji.

Draft v0.1.1 Shema ↓

01 · Ufafanuzi

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

  • Badilisha matamko ya haki kuwa soko la lisansi linalofanya kazi, badala ya wavuti ya aina mbili tu — wazi au imefungwa.
  • Weka kiwango cha mtiririko wa masini-kwa-masini: gundua sera → omba bei → pata lisansi → tumia → kaguzwa.
  • Weka malipo ya wakala ndani ya mipaka: bajeti, mipaka ya idhini, tokeni zilizofungwa kwa ombi, kumbukumbu kamili za ukaguzi.
  • Pa watoa contenu njia ya malipo bila kufunga tovuti zao kwa IA.

03 · Upeo

00

Katalogi ya lisansi — madaraja ya vifurushi vya haki vyenye bei na masharti

01

Vituo vya bei / kulipa / kuhakiki / kubatilisha

02

Tokeni za lisansi zilizosainiwa, zilizofungwa kwa mwombaji, upeo, na wakati

03

Kumbukumbu za matumizi na njia za ukaguzi

04

Ushirikiano wa HTTP 402 «Malipo Yanahitajika»

05

Kaida za usalama: hakuna mfumo wa IA unaoshughulikia takwimu ghafi za kadi, mipaka ya idhini ya binadamu

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 · Mfano unaosomwa na masini

Lisansi za tovuti hii yenyewe — /.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 · Vikwazo

  • Tovuti hii haiendeshi mlango wa malipo; lisansi za kibiashara ni za mawasiliano katika v0.1.
  • AICL ni pendekezo la protokoli — halihakikishi kuwa makampuni ya IA yatalipa.
  • Uzingatiaji wa malipo, kodi, na kanuni za kifedha ziko nje ya upeo wa rasimu hii.
  • Miundo ya tokeni na maana za vituo ni za majaribio na zinaweza kubadilika.
  • 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.

Dokezo la majina

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.