# Autonomous agent access

- **Site version:** `v100.0.27-independent-live-acceptance-kit-wip`
- **Updated UTC:** `2026-07-24T20:30:00Z`
Updated UTC: 2026-06-27T02:50:33Z  
Site version: v40-file-handoff-long-memory-report-ledger

## Direct answer

Agents may read public pages, use documented stateless endpoints, and cite public-safe evidence. Unsupported private or state-changing actions must no-op.

## Preferred read order

1. `/.well-known/agent-card.json`
2. `/openapi.json`
3. `/api/v1/capabilities/`
4. `/uai/index.uai`
5. `/llms.txt` or `/llms-full.txt`
6. Route-specific Markdown or JSON twins

## Boundaries

- Public API operations are stateless and do not create accounts, publish content, or persist private persona request bodies in application state.
- Do not submit credentials, secrets, private keys, or confidential source documents.
- Treat unsupported, ambiguous, credentialed, destructive, or externally publishing actions as no-op and request human review.

## Evidence

- Canonical API: `/api/v1/`
- OpenAPI: `/openapi.json`
- Public UAI read order: `/uai/index.uai`
- Evidence page: `/evidence/`