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

Capability-Adaptive Web Interaction

UAIX L0-L6 client capability ladder, profile IDs, required fields, fallback behavior, consent boundaries, validator rules, and evidence expectations for browsers and agents.

  • Record UAIX-DOC-2670
  • Path /en-us/guides/capability-adaptive-web-interaction/
  • Use Canonical public record

Document status

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

How to use this page

Use this guide to choose the correct L0-L6 browser or agent capability profile, fallback, consent boundary, and evidence packet before claiming support.

Capability-Adaptive Web Interaction lets one site speak safely to very different readers: limited crawlers, structured fetchers, browser-assisted agents, tool callers, workflow agents, multi-agent runtimes, and audited systems.

The point is not to make UAIX execute work. The point is to publish the exact capability boundary, fallback behavior, consent requirement, and evidence packet a receiver can validate before acting.

Client capability ladder

Level Client Can do Must not imply
L0 Limited Browser / Static Fetch Read static text, static HTML, Markdown, sitemap, llms.txt, and JSON. JavaScript execution, UI operation, posting, auth, tools, memory, or coordination.
L1 Structured Fetch Resolve predictable low-token JSON, schemas, registry entries, examples, and route manifests. JavaScript execution or write-capable behavior.
L2 Browser-Assisted Agent Inspect rendered UI and compare it with static or structured parity evidence. Autonomous auth, posting, tool calls, or long-running work.
L3 Tool-Calling Agent Call tools, authenticate, or post only with explicit consent, idempotency, fallback, and evidence. Long workflow control, durable memory writes, or multi-agent coordination.
L4 Workflow Agent Run long tasks in an external runtime with correlation, task status, timeout, fallback, and final reports. Memory promotion or agent coordination without additional review.
L5 Multi-Agent Runtime Coordinate agents in an external runtime while UAIX carries reviewed records and handoffs. UAIX-hosted runtime execution.
L6 Audited Agent System Attach provenance, audit logs, validator output, consent records, memory review, and final reports. Certification, endorsement, or proof that missing evidence is acceptable.

Published profile IDs

The release publishes these profile IDs: uai.capability.profile.v1, uai.capability.negotiation.v1, uai.client.limited-browser.v1, uai.client.structured-fetch.v1, uai.client.browser-assisted.v1, uai.client.tool-agent.v1, uai.client.workflow-agent.v1, uai.client.multi-agent-runtime.v1, and uai.client.audited-agent-system.v1.

Required capability profile fields

Every capability profile body carries: client_level, client_name, can_fetch_static, can_fetch_json, can_execute_javascript, can_use_browser_ui, can_post_data, can_authenticate, can_call_tools, can_run_long_tasks, can_store_memory, can_coordinate_agents, requires_human_consent_for, declared_or_required_uaix_profiles, fallback_behavior, known_limits, evidence_requirements, and safe_default_response.

Minimum safe packet

Code example
{
  "profile": "uai.client.structured-fetch.v1",
  "body": {
    "client_level": "L1",
    "client_name": "Structured Fetch",
    "can_fetch_static": true,
    "can_fetch_json": true,
    "can_execute_javascript": false,
    "can_post_data": false,
    "requires_human_consent_for": [],
    "fallback_behavior": "Use JSON, sitemap, llms.txt, and static HTML before requiring JavaScript.",
    "safe_default_response": "Name the exact static or JSON route and stop before write-capable action."
  }
}
Transfer formatOptimized (Keyless) JSON
Code example
[
    null,
    "uai.client.structured-fetch.v1",
    null,
    null,
    null,
    null,
    null,
    null,
    [
        "L1",
        "Structured Fetch",
        true,
        true,
        false,
        null,
        false,
        null,
        null,
        null,
        null,
        null,
        [],
        null,
        "Use JSON, sitemap, llms.txt, and static HTML before requiring JavaScript.",
        null,
        null,
        "Name the exact static or JSON route and stop before write-capable action."
    ]
]

Field order follows the keyed JSON example, the published schema order, and the public field registry.

Validator rules

  • L0 and L1 records fail when they claim JavaScript or depend on JavaScript-only content without a static or JSON fallback.
  • Write-capable, authentication-capable, memory-capable, coordination-capable, and high-assurance records require human consent boundaries.
  • POST-like actions require idempotency; workflows require correlation and expiration; high-assurance records require provenance, audit, validator, consent, and final-report evidence.
  • Memory writes require uai.agent.memory-proposal.v1 and review before durable promotion.
  • UAIX runtime execution claims, unsafe credentials, and ambiguous UAIX/Carcinus/LocalEndPoint boundaries fail validation.

Machine surfaces

Boundary

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary. 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 is an external consumer boundary, not a UAIX runtime feature.

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.