Mazmuna geç
AGIRight.org

AICL — Emeli Intellekt Mazmun Ygtyýarnamalandyryş Gatlagy

Emeli Intellekt Mazmun Ygtyýarnamasy / Emeli Intellekt Mazmun Ygtyýarnamalandyryş Gatlagy

Deklarirlenen hukuklary ýerine ýetirilip bilinjek ygtyýarnamalandyrma öwürýär: baha, töleg, tassyklama, barlag, ýatyrma.

Draft v0.1.1 Shema ↓

01 · Kesgitleme

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

  • Hukuk deklarasiýalaryny ikilik açyk/ýapyk webiň ýerine işleýän ygtyýarnamalandyryş bazaryna öwürmek.
  • Maşyndan-maşyna akymy standartlaşdyrmak: syýasaty açmak → baha soramak → ygtyýarnamalandyrmak → ulanmak → barlamak.
  • Agent tölegleri çäklendirilen görnüşde saklaň: býudjetler, tassyklama bosagalary, sorag bilen baglanyşykly tokenler, doly audit ýazgylary.
  • Mazmun üpjün edijilere sahypalaryny emeli intellekte ýapmazdan öwez almak üçin ýol bermek.

03 · Gerim

00

Ygtyýarnama katalogy — bahalary we şertleri bolan hukuk toplumlarynyň derejeleri

01

Baha / töleg / tassyklama / ýatyrma soňky nokatlary

02

Sorag ediji, gerim we wagt bilen baglanyşykly gol çekilen ygtyýarnama tokenleri

03

Ulanyş ýazgylary we audit yzlary

04

HTTP 402 „Töleg Zerur” özara işlemekligi

05

Howpsuzlyk kadalary: emeli intellekt çig kart maglumatlaryny işlemeýär, ynsan tassyklama bosagalary

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 · Maşyn tarapyndan okalýan mysal

Bu sahypanyň öz ygtyýarnamalary — /.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 · Çäklendirmeler

  • Bu sahypa töleg derwezesini işletmeýär; täjirçilik ygtyýarnamalary v0.1-de habarlaşma esaslydyr.
  • AICL bir protokol teklibidir — ol emeli intellekt kompaniýalarynyň hakykatdan hem töleg etjekdigine kepillik bermeýär.
  • Töleg laýyklygy, salgyt we maliýe düzgünleşdirmesi bu taslamanyň gerimden daşarda.
  • Token formatlary we soňky nokat manylary eksperimentaldyr we üýtgäp biler.
  • 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.

Atlandyrma barada bellik

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.