UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Standards

Standards

First-class UAIX standards index for UAI-1, SPEC-01 through SPEC-04, the capability ladder, low-capability readers, advanced agents, schemas, examples, and safety boundaries.

  • Record UAIX-STND-2699
  • Path /en-us/standards/
  • Use Canonical public record

Document status

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

How to use this page

Use this page as the first-class index for current UAIX standards, schemas, examples, capability levels, and safety boundaries.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into Conformance Pack, implementation track, changelog, or Project Handoff evidence.

UAIX Standards is the first-class route family for UAI-1, Project Handoff, AGENTS.md, File Handoff, the capability ladder, low-capability readers, advanced agents, schemas, examples, and safety boundaries.

The older Specification pages remain valid. This route family makes the current standards contracts easier for humans and agents to discover without changing existing public URLs.

Safety summary

  • Use schemas, examples, registry records, validator output, and release notes together before making support claims.
  • Use the lowest viable capability level, and downgrade to static/JSON fallback when capability is unknown.
  • Do not treat a standards envelope as runtime authorization, trust proof, certification, endorsement, or permission to expose secrets.

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