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

Guides

Limited Browser Support

Static and structured fallback guidance for limited browsers, crawlers, and fetch clients that cannot execute JavaScript or perform write-capable actions.

  • Record UAIX-DOC-2671
  • Path /en-us/guides/limited-browser-support/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-2671
Surface
Guides
Access
Public and linkable

How to use this page

Use this guide to publish static and structured fallbacks for clients that cannot execute JavaScript, authenticate, post, call tools, store memory, or coordinate agents.

Limited-browser support is the L0/L1 promise: a client can still read useful public records when it cannot run JavaScript, click UI controls, authenticate, post data, call tools, store memory, or coordinate agents.

What to publish

  • Static HTML or text summaries for important pages.
  • JSON records for schemas, registry entries, examples, discovery, conformance levels, and error codes.
  • llms.txt, llms-full.txt, sitemap routes, and stable canonical links.
  • A fallback note when a feature needs browser rendering, tools, authentication, or human consent.

L0 and L1 validation

L0 and L1 profiles fail when they claim JavaScript execution or make JavaScript-only content the only path. Their safe default is to cite the static or JSON route and state what higher capability level is needed next.

Useful records

Minimal Access Tier for URL-only chatbots

Limited-browser support now names a stricter Minimal Access Tier for clients that can only issue a public GET request with no body, no auth, no custom headers, and no JavaScript. That tier returns only a code and a public url; it never mutates state.

Agent Communication Operating Model

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

Use Agent Communication Operating Model when a human operator, coding agent, AI agent, or runtime implementer needs portable identity, intent, context, acknowledgement, status, blocker, memory proposal, validation evidence, correction, final report, or handoff records. The matching machine-readable assets are published through Schemas, Registry, Examples, and the Validator.

  • UAIX does not provide automatic sync, hosted messaging, runtime orchestration, official adapters, repository write execution, certification authority, or hosted import mechanisms.
  • Carcinus.org is a separate runtime/orchestrator example that may consume UAIX records. UAIX.org does not implement Carcinus runtime behavior and does not execute Carcinus workflows.
  • LocalEndPoint and other runtimes may consume the published UAIX records as external consumers; UAIX.org does not implement their project-specific runtime features.
  • Durable memory proposals stay separate from task execution records. Do not promote temporary endpoint statuses, session tokens, write tokens, beta platform instructions, local error traces, private keys, or API credentials.