Skip to content
Get Started Free

Progressive Agent Access

Progressive Agent Access lets one user intent move from static discovery to richer agent workflows only when the client proves capability and permission.

Same action across tiers

  1. Minimal Access: return a public URL and a code only. No state changes.
  2. GET-Action fallback: allow a bounded idempotent URL action only when consent, rate limits, audit logging, and no-secret query rules hold.
  3. POST JSON: prefer structured POST for L2+ clients, rich validation, authentication, and normal API behavior.
  4. Advanced manifests: expose schemas, examples, discovery manifests, conformance records, and evidence packets.
  5. Memory or handoff: move durable claims through Project Handoff, Agent File Handoff, review receipts, and final-report evidence.

Failure behavior

  • If the client cannot prove capability, return the lower-capability public URL.
  • If the action needs consent, return a human-review URL or blocker record.
  • If the request carries secrets or private identifiers in a query string, reject it and require a safer POST or human-mediated path.

Route family

Boundary

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

  • Minimal Access is read-only, public-safe, GET-only, URL-only, and must not mutate state.
  • GET-Action is a separate bounded fallback for bounded actions and must not be treated as a replacement for POST JSON APIs.
  • UAIX does not certify runtime safety, truth, consciousness, authorization, medical suitability, or production readiness.

Machine-readable companions

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.