Eike content-pe voi
AGIRight.org

AICL — IA Contenido Licenciamiento Ñuãha

IA Contenido Licencia / IA Contenido Licenciamiento Ñuãha

Omoambue derécho declaráva licenciamiento ejecutable-pe: oferta, ñemyengovia, mbojoja, auditoría, jejora.

Draft v0.1.1 Esquema ↓

01 · Definición

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 · Propósito

  • Emoambue derécho declaración-kuéra mercado licenciamiento ikatúva omba'apo-pe, web binário ijurujáva/oñembotýva rangue.
  • Estandariza rape máquina-máquina apytépe: ejuhu política → ejerure oferta → licencia → jeporu → auditoría.
  • Emoĩ ñemyengovia agente-gua mbojoyke: presupuesto, límite jeroviapy, token pyendaguáva pedido-pe, auditoría registro opavavete.
  • Eme'ẽ contenido me'ẽhare-kuérape peteĩ tape ñemyengovia-rã, ombotypy'ỹre itenda IA-pe g̃uarã.

03 · Alcance

00

Licencia catálogo — nivel derécho paquete hepy ha condición reheve

01

Endpoint oferta / ñemyengovia / mbojoja / jejora-gua

02

Licencia token firmado, pyendaguáva ojerurévape, alcance ha aravo ndive

03

Registro jeporu ha auditoría rape

04

HTTP 402 «Ñemyengovia Oipotáva» interoperabilidad

05

Rembiapoukapy seguridad-gua: IA ndoiporukái tarjeta data cruda, límite jeroviapy yvypóra-gua

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 · Techapyrã oñemoñe'ẽkuaáva máquina rupive

Ko tenda licencia ijupegua — /.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 · Límite-kuéra

  • Ko tenda ndoiporukái pasarela ñemyengovia-gua; licencia comercial-kuéra oñembopyenda contacto-pe v0.1-pe.
  • AICL ha'e peteĩ protokolo propuesta — ndoguerekói jerovia empresa IA-gua ohepyme'ẽtaha.
  • Cumplimiento ñemyengovia-gua, impuesto, ha regulación financiero ndoikéi alcance ko borrador-pe g̃uarã.
  • Token formato ha endpoint significado ha'e experimental ha ikatu oñemoambue.
  • 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.

Téra rehegua jehaipy

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.