Agent Compatibility

Low-Capability Agent Quick Start

1. Start with public static pages, llms.txt, sitemap routes, and small JSON records.
2. Use GET-Action URLs only when the page or JSON record explicitly lists them.
3. Do not invent writable URLs, POST bodies, credentials, custom headers, hidden browser steps, or JavaScript-only workarounds.
4. Do not put secrets, tokens, account identifiers, medical identifiers, payment data, or private messages in URLs.
5. When uncertain, use the No-Op Protocol and return the public review URL instead of retrying.
6. For complex, private, regulated, destructive, publishing, repository-write, or long-running work, hand off to a human or higher-capability agent.

Boundary

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary. UAIX.org does not execute third-party actions, certify safety, certify truth, endorse implementations, or replace local authorization policy.

Agent Compatibility Records

• Capability-Adaptive InteroperabilityL0-L6 support contracts and fallback behavior.
• GET-Action PatternURL-first action fallback with POST equivalents.
• GET-Action SecurityIdempotency, nonce, consent, crawler, and no-secret rules.
• No-Op ProtocolHow unsupported agents stop safely.
• Capability Surface MatrixSupport expectations by client capability level.
• Validator RulesRequired failures and warnings for compatibility records.
• Implementation ExamplesSafe URL-first and POST-equivalent patterns.