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

Low-Capability Agents

Static, Markdown, sitemap, llms, and small-JSON fallback guidance for L0 and L1 clients.

  • Record UAIX-STND-2706
  • Path /en-us/standards/low-capability-agents/
  • Use Canonical public record

Document status

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

How to use this page

Use this page for static, Markdown, sitemap, llms, and compact JSON fallbacks for L0 and L1 clients.

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.

Low-capability agents need boring, durable fallbacks. UAIX should remain useful to clients that can read links, text, Markdown, sitemap entries, llms files, and compact JSON but cannot execute JavaScript or operate UI controls.

Publish for L0 and L1 first

  • Readable HTML pages with headings, tables, and direct links.
  • llms.txt and llms-full.txt with canonical reading order and safety boundaries.
  • Sitemap entries for the page family.
  • REST catalog, schemas, registry, examples, and well-known manifests.
  • Small JSON examples with UTC timestamps, manifest metadata, checksums, and no secrets.

Human-mediated handoff

If a client cannot post, authenticate, call tools, or validate complex payloads, the safe path is to produce a packet for a human or higher-capability agent to review. That packet can cite AI Memory Package Wizard output, but the browser-generated ZIP is still review material, not automatic execution.

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