UAI-1 es la norma pública actual de mensajes para comunicación estructurada de IA a IA.
UAIX shield mark Carta pública de interoperabilidad UAIX.org 通用人工智能交换 Publicación pública de normas
Actual UAI-1
  • Versión actual UAI-1
  • Definición en lenguaje claro Formato de mensaje abierto para intercambio IA-a-IA auditable
  • Atribución actual Michael Joseph Kappel, MCP
  • Empiece aquí Inicio, Traspaso de proyecto, UAI-1, validador, hoja de ruta y registro de cambios

Compatibilidad de agentes

Compatibilidad de agentes

UAIX agent compatibility specification surface for low-capability quick starts, GET-Action standardization, no-op behavior, capability matrix support, validator rules, and safe implementation examples.

  • Record UAIX-DOC-2748
  • Path /es-es/spec/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-2748
Surface
Compatibilidad de agentes
Access
Public and linkable

如何使用本页

Use this page as part of the current Compatibilidad de agentes public record, then follow its linked standards pages for the next step.

Agent Compatibility is the UAIX.org specification surface for low-capability support, GET-Action standardization, no-op behavior, progressive enhancement, executable path guidance, and recursive interoperability checks.

Low-Capability Agent Quick Start

  1. Start with public static pages, llms.txt, sitemap routes, and small JSON records.
  2. Use GET-Action URLs only when the page or JSON record explicitly lists them.
  3. If a route requires live dynamic HTTP GET and the client only has indexed or cached fetch, use the listed live-GET fallback or no-op review URL.
  4. Do not invent writable URLs, POST bodies, credentials, custom headers, hidden browser steps, or JavaScript-only workarounds.
  5. Do not put secrets, tokens, account identifiers, medical identifiers, payment data, or private messages in URLs.
  6. When uncertain, use the No-Op Protocol and return the public review URL instead of retrying.
  7. For complex, private, regulated, destructive, publishing, repository-write, or long-running work, hand off to a human or higher-capability agent.

代理可执行性矩阵

可执行指导不只是端点发现。 路由 records should name the ability level, method, content type, side-effect status, fetch execution class, required fields, result URL field, restore/readback URL field, write credential response path, browser-form equivalent, GET safety, POST-blocked fallback, and live-GET-blocked fallback.

Level Executable path Required route guidance
L0 Read-only route discovery Static page, sitemap, llms.txt, or public GET route names the next public URL or no-op review URL.
L1 Manifest/schema discovery Machine record names schema, safe-read status, whether live dynamic GET is required, unsupported actions, and capability limits.
L2 Browser-open plus form submission Browser-targeted writes provide a visible form or browser-open workflow when browser agents are a target.
L3 Structured HTTP JSON POST POST route names content type, required fields, result URL, restore/readback URL, and structured errors.
L4 Authenticated owned mutation Owned mutation names write credential response path, secret handling, audit, expiry, and idempotency.
L5 Restore/readback verification Create or update flow exposes a public-safe restore/readback route.
L6 Multi-agent handoff/reporting Handoff names task history, owner, role, blocker/no-op behavior, final report, and evidence.
L7 Site-specific capability negotiation Site manifest names capability negotiation, browser fallback, POST fallback, live GET fallback, and unsupported-operation response.

Machine-readable companion: /spec/agent-executability-matrix.json.

路由 family

Machine-readable entry points

边界

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary. UAIX.org does not execute third-party actions, certify safety, certify truth, endorse implementations, or replace local authorization policy.

Agent Compatibility Records