Directory of machine access sources & AX
Acme Directory is a comprehensive directory index of sources and interfaces for Agent Experience (AX) and machine access.
Why Acme Directory exists
Information about how autonomous agents and software can actually interface with individual systems has been scattered across hundreds of PDF guides, legacy SOAP endpoints, and guarded portals. Acme Directory brings it together.
Acme Directory brings it all together: direct REST APIs, Model Context Protocol (MCP) servers, command-line tools, and browser automation patterns with honest notes on authentication, access requirements, and reliability.
From UX & DX to AX: Agent Experience
Why autonomous software agents need their own interface discipline — and how this directory bridges the gap between digital infrastructure and autonomous AI.
The Evolution of Digital Interfaces
Visual hierarchies, typography, CSS responsive grids, buttons, and animations designed to reduce human cognitive load.
SDKs, CLI ergonomics, typed client libraries, clear REST/GraphQL documentation, and helpful stack traces for builders.
Machine discoverability (llms.txt, MCP), deterministic schemas, unambiguous tool definitions, structured error recovery, and explicit auth boundaries.
The 4 Pillars of AX
1. Machine Discoverability
Agents cannot browse visual app stores. High AX means systems declare their capabilities machine-readably through llms.txt, Model Context Protocol (MCP), and WebMCP browser standards.
2. Semantic & Schema Precision
Ambiguous descriptions trigger hallucinations. AX requires precise function declarations that tell the agent exactly when, why, and how to format parameters.
3. Auth Transparency & Step-up HITL
Agents cannot guess 2FA or bypass step-up identity. This directory clearly delineates public endpoints from enterprise tokens and enforces Human-in-the-Loop (HITL) for sensitive identity.
4. Error Resilience & Recovery
Generic 500 pages cause infinite retry loops. High-AX systems return actionable, structured error payloads that guide the LLM on how to self-correct.
The AX Gap
Many digital services were engineered for human UX or legacy DX. This directory provides the missing AX discovery layer, translating registers and services into agent-ready protocols.
Core Principles
We do not oversell stability. If a system requires human step-up approval or fragile browser automation, we document it clearly.
Actions involving sensitive identity or step-up login require explicit human-in-the-loop oversight.