Ruka hadi kwenye maudhui
AGIRight.org

AICL — Tabaka la Utoaji Leseni wa Maudhui ya AI

Leseni ya Maudhui ya AI / Tabaka la Utoaji Leseni wa Maudhui ya AI

Inabadilisha haki zilizotamkwa kuwa utoaji leseni unaotekelezeka: bei-elekezi, lipa, thibitisha, kagua, batilisha.

Draft v0.1.1 Schema ↓

01 · Fasili

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 leseni linaloweza kufanya kazi badala ya mtandao wa jozi wa wazi/uliofungwa.
  • Sanifisha mtiririko wa mashine-kwa-mashine: gundua sera → omba bei-elekezi → pata leseni → tumia → kagua.
  • Weka malipo ya kiwakala na mipaka: bajeti, viwango vya idhini, tokeni zilizofungwa kwa ombi, kumbukumbu kamili za ukaguzi.
  • Wape watoa maudhui njia ya kupata fidia bila kufunga tovuti zao kwa AI.

03 · Upeo

00

Katalogi ya leseni — ngazi za vifurushi vya haki zenye bei na masharti

01

Sehemu za huduma za bei-elekezi / kulipa / kuthibitisha / kubatilisha

02

Tokeni za leseni zilizosainiwa, zilizofungwa kwa mwombaji, upeo, na muda

03

Kumbukumbu za matumizi na mifuatano ya ukaguzi

04

Uoanifu na HTTP 402 "Payment Required"

05

Kanuni za usalama: AI haishughulikii data ghafi za kadi, viwango vya 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 unaosomeka na mashine

Leseni 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 · Mapungufu

  • Tovuti hii haiendeshi lango la malipo; leseni za kibiashara zinategemea mawasiliano katika v0.1.
  • AICL ni pendekezo la itifaki — halihakikishi kuwa makampuni ya AI yatalipa.
  • Uzingatiaji wa malipo, kodi, na udhibiti wa kifedha viko nje ya wigo wa rasimu hii.
  • Miundo ya tokeni na maana za sehemu za huduma ni za kijaribio 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.

Maelezo kuhusu jina

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.