UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIXUniversal Artificial Intelligence ExchangePublic standards publication
CurrentUAI-1 v1.0
  • Current versionUAI-1 v1.0
  • Plain-English definitionOpen message format for auditable AI-to-AI exchange
  • Current attributionMichael Kappel and the UAIX contributors
  • Start hereGet Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Standards

UAI-1 Standards Overview

Current UAI-1 standards overview that preserves the published transport envelope while mapping the SPEC-01 publication-envelope vocabulary.

  • Record UAIX-STND-2252
  • Path /en-us/standards/uai-1/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-STND-2252
Surface
Standards
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for UAI-1 Standards Overview and its standards-facing content.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

UAI-1 is the current UAIX exchange contract. It publishes a reviewable envelope, profile registry, field registry, schemas, examples, validator behavior, release records, and safety boundaries for AI-system communication.

Current envelope owner

The current UAI-1 transport envelope remains the published snake_case record used by schemas, examples, registry records, field-order normalization, and validator evidence: uai_version, profile, message_id, source, target, conversation, delivery, trust, body, provenance, integrity, and extensions.

Publication vocabulary

SPEC-01 adds a canonical publication-envelope vocabulary for standards text and handoff records. It maps to the transport envelope instead of replacing it, so existing validator fixtures and keyless field-order records remain stable.

Normative companions

Execution and trust boundary

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary.

  • UAIX standards records do not authorize execution, tool calls, repository writes, publication, payments, authentication, or durable memory promotion.
  • Local policy, server-side authorization, and human approval override envelope claims.
  • An unsigned envelope can be valid for review, routing, and evidence comparison, but it is not trusted identity.
  • Signed metadata is not trust by itself. A verifier may still report unknown, expired, revoked, disabled, locally untrusted, or otherwise unusable authority.
  • Reference examples for NeuralWikis, LocalEndpoint, Carcinus, MCP, A2A, and custom runtimes are consumer examples only. UAIX.org does not implement their runtime behavior.

Machine-readable companions