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

Registry

Registry

Published UAI-1 profile IDs, schema links, example links, compatibility notes, and the profile map behind the current release.

  • Record UAIX-REGI-0051
  • Path /en-us/registry/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-REGI-0051
Surface
Registry
Access
Public and linkable

How to use this page

Use this page for published profile IDs, schema links, example links, and compatibility notes.

What the registry provides

The UAIX registry publishes the stable identifiers that make UAI-1 readable by both people and automation. It is the profile map that ties the specification, schemas, fixtures, validator expectations, and support claims together.

What belongs here

  • Profile IDs, record codes, titles, and public status.
  • Schema routes, example routes, and expected validation posture.
  • Compatibility cues that explain which message families are meant to pair together.
  • The release-facing identifiers that other records can cite without guessing.

How the current profiles relate

  • uai.intent.request.v1 usually pairs with uai.intent.response.v1, uai.error.v1, or a later uai.task.status.v1 update.
  • uai.intent.response.v1 stays in the same public envelope and can acknowledge accepted async work through task references.
  • uai.capability.statement.v1 advertises supported operations, profile families, endpoints, and security posture for discovery work.
  • uai.error.v1 is designed to remain legible across request, response, capability, task, and validator flows.
  • uai.conformance.result.v1 records validator evidence for the other published profiles.
  • uai.task.status.v1 keeps async progress public when accepted work cannot be closed in a single response.

Extension and field-order governance

Profile registration and field-order governance should move together. If a release changes keyed-to-keyless order or nested body order, the field registry should change beside the profile record instead of drifting into separate implementation notes.

Current published entries

The registry below ties each public profile identifier to its matching schema, example, and validation posture.

Registry

Current UAI-1 profile registry

Each registry entry ties a stable profile identifier to its schema record, compatibility posture, and example fixture so implementers can resolve the public standard surface mechanically. Use the field registry alongside these entries whenever a transport relies on optimized keyless ordering.

Open registry JSON Open field registry JSON

UAI-REGI-0001

UAI Intent Request v1

Request an explicit outcome or async task against a declared subject using the full UAI-1 envelope, trust metadata, and reviewable delivery controls.

Profile
uai.intent.request.v1
Status
ACTIVE
Compatible with
uai.intent.response.v1, uai.task.status.v1, uai.error.v1
Entry JSON Schema Example

UAI-REGI-0002

UAI Intent Response v1

Return a direct result or accepted-task handoff for a declared request while preserving conversation continuity, trust metadata, and release-ready evidence.

Profile
uai.intent.response.v1
Status
ACTIVE
Compatible with
uai.intent.request.v1, uai.task.status.v1, uai.error.v1
Entry JSON Schema Example

UAI-REGI-0003

UAI Capability Statement v1

Publish capability, endpoint, security, async workflow, and extension-support metadata so adjacent systems can resolve what an implementation actually supports.

Profile
uai.capability.statement.v1
Status
ACTIVE
Compatible with
uai.intent.request.v1, uai.intent.response.v1, uai.task.status.v1, uai.error.v1
Entry JSON Schema Example

UAI-REGI-0004

UAI Error v1

Report validation, transport, authorization, or execution failures using a typed problem-details-style envelope with retry and path-level detail.

Profile
uai.error.v1
Status
ACTIVE
Compatible with
uai.intent.request.v1, uai.intent.response.v1, uai.capability.statement.v1, uai.task.status.v1
Entry JSON Schema Example

UAI-REGI-0005

UAI Conformance Result v1

Capture validator output, artifact references, and issue summaries in the same public message family so proof can travel with the release record.

Profile
uai.conformance.result.v1
Status
ACTIVE
Compatible with
uai.intent.request.v1, uai.intent.response.v1, uai.capability.statement.v1, uai.error.v1, uai.task.status.v1
Entry JSON Schema Example

UAI-REGI-0006

UAI Task Status v1

Publish long-running task state, progress, blockers, and result references so async agent work stays auditable instead of disappearing into private workflow state.

Profile
uai.task.status.v1
Status
ACTIVE
Compatible with
uai.intent.request.v1, uai.intent.response.v1, uai.error.v1, uai.conformance.result.v1
Entry JSON Schema Example

How to use this section

  1. Resolve the profile before adding support in code or documentation.
  2. Bind that profile to the matching schema, example, and validator expectation.
  3. Use the registry entry as the stable key when attaching release evidence in Implementations, the Changelog, or References and Contributors.

Next step

Continue to Examples to see how the current identifiers, schema rules, and async workflow records appear in working exchanges.