ຂ້າມໄປຫາເນື້ອຫາ
AGIRight.org

AICL — ຊັ້ນການອອກໃບອະນຸຍາດເນື້ອຫາ AI

ໃບອະນຸຍາດເນື້ອຫາ AI / ຊັ້ນການອອກໃບອະນຸຍາດເນື້ອຫາ AI

ປ່ຽນສິດທີ່ປະກາດໄວ້ໃຫ້ກາຍເປັນການອອກໃບອະນຸຍາດທີ່ໃຊ້ງານໄດ້ຈິງ: ໃບສະເໜີລາຄາ, ຈ່າຍເງິນ, ກວດສອບ, ກວດສອບຕິດຕາມ, ເພິກຖອນ.

Draft v0.1.1 Schema ↓

01 · ນິຍາມ

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 · ຈຸດປະສົງ

  • ປ່ຽນຄຳປະກາດສິດໃຫ້ກາຍເປັນຕະຫຼາດການອອກໃບອະນຸຍາດທີ່ໃຊ້ງານໄດ້ຈິງ ແທນທີ່ຈະເປັນເວັບແບບເປີດ/ປິດແບບໄບນາຣີ.
  • ສ້າງມາດຕະຖານໃຫ້ຂັ້ນຕອນລະຫວ່າງເຄື່ອງຈັກກັບເຄື່ອງຈັກ: ຄົ້ນຫານະໂຍບາຍ → ຮ້ອງຂໍໃບສະເໜີລາຄາ → ອອກໃບອະນຸຍາດ → ໃຊ້ງານ → ກວດສອບ.
  • ຮັກສາການຈ່າຍເງິນແບບ agentic ໃຫ້ຢູ່ໃນຂອບເຂດ: ງົບປະມານ, ຂອບເຂດການອະນຸມັດ, token ທີ່ຜູກກັບ request, ບັນທຶກກວດສອບແບບຄົບຖ້ວນ.
  • ໃຫ້ຜູ້ໃຫ້ບໍລິການເນື້ອຫາມີເສັ້ນທາງໄປສູ່ຄ່າຕອບແທນ ໂດຍບໍ່ຕ້ອງປິດເວັບໄຊທ໌ຂອງຕົນຈາກ AI.

03 · ຂອບເຂດ

00

ຄາຕາລອກໃບອະນຸຍາດ — ຊັ້ນຂອງຊຸດສິດພ້ອມລາຄາ ແລະ ເງື່ອນໄຂ

01

endpoint ສຳລັບໃບສະເໜີລາຄາ / ຈ່າຍເງິນ / ກວດສອບ / ເພິກຖອນ

02

Token ໃບອະນຸຍາດແບບມີລາຍເຊັນ ຜູກກັບຜູ້ຮ້ອງຂໍ, ຂອບເຂດ, ແລະ ເວລາ

03

ບັນທຶກການໃຊ້ງານ ແລະ ຮ່ອງຮອຍການກວດສອບ

04

ຄວາມສາມາດເຮັດວຽກຮ່ວມກັນຂອງ HTTP 402 "Payment Required"

05

ກົດລະບຽບຄວາມປອດໄພ: AI ຫ້າມຈັດການຂໍ້ມູນບັດດິບ, ຂອບເຂດການອະນຸມັດຂອງມະນຸດ

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 · ຕົວຢ່າງທີ່ອ່ານໄດ້ດ້ວຍເຄື່ອງຈັກ

ໃບອະນຸຍາດຂອງເວັບໄຊທ໌ນີ້ເອງ — /.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 · ຂໍ້ຈຳກັດ

  • ເວັບໄຊທ໌ນີ້ບໍ່ໄດ້ດຳເນີນການ payment gateway; ໃບອະນຸຍາດເຊິງການຄ້າໃນ v0.1 ອີງໃສ່ການຕິດຕໍ່.
  • AICL ເປັນຂໍ້ສະເໜີໂປໂຕຄອນ — ມັນບໍ່ໄດ້ຮັບປະກັນວ່າບໍລິສັດ AI ຈະຈ່າຍເງິນ.
  • ການປະຕິບັດຕາມກົດລະບຽບການຈ່າຍເງິນ, ພາສີ, ແລະ ກົດລະບຽບການເງິນ ຢູ່ນອກຂອບເຂດຂອງຮ່າງນີ້.
  • ຮູບແບບ token ແລະ ຄວາມໝາຍຂອງ endpoint ຍັງຢູ່ໃນຂັ້ນທົດລອງ ແລະ ອາດປ່ຽນແປງໄດ້.
  • 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.

ໝາຍເຫດການຕັ້ງຊື່

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.