How agent-ready is Anthropic?

Anthropic's public website scored 25/100 on its homepage and 26/100 on pricing pages, indicating limited agentability for autonomous AI systems attempting to parse and interact with these surfaces. Documentation fared better at 48/100, though still below the threshold for smooth agent operation. These scores reflect significant gaps in how the site exposes structure, state, and control mechanisms that agents rely on.

The audit identified three principles with zero scores—status reporting, clean handoffs, and transparency—meaning the site provides no machine-readable feedback on system state, minimal structured error context, and no audit trails or confidence metadata. Control mechanisms scored 19/100, lacking explicit confirmation patterns and cancel affordances for destructive or long-running actions. Machine readability (65/100) and defaults (59/100) were relative strengths, while chunking (41/100) and shadow UI avoidance (15/100) fell into the middle range.

For a company building agent-capable AI models, these scores suggest that Anthropic's own digital properties have not yet been optimized for the autonomous agent workflows its products enable. Addressing the transparency, control, and error-handling gaps would materially improve agent integration outcomes.

Anthropic can improve agentability by implementing the following changes:

• Return structured error context in both UI and API responses, including specific failure reasons, error codes, and the fields or inputs that triggered the problem, rather than generic messages like 'Something went wrong'.
• Add an activity log or audit trail that records system actions in machine-readable format (such as a JSON event feed), and surface a user-facing version to explain results and decisions made by the platform.
• Gate destructive actions—such as deletions or irreversible changes—behind explicit, visually distinct confirmation steps, and provide undo or override capabilities for completed actions where feasible.
• Include confidence or certainty indicators on key outputs in API responses and UI, such as 'verified' versus 'best-guess' labels, to help agents assess reliability.
• Provide labeled pause, cancel, or stop controls for long-running operations with accessible names (e.g., 'Cancel upload'), not icon-only buttons.
• Attach source references, input citations, or identifiers to generated outputs, and offer expandable drill-downs on important results—a summary line with optional detail view.