# Agent Readiness

**Canonical:** https://apis.io/providers/agent-readiness/  
**APIs profiled:** 15

A topic index covering the operational practices, signals, and patterns that make an API surface safely usable by autonomous AI agents rather than only by humans. Catalogs the specifications, identity layers, agent skill formats, and edge-layer signals that combine into a coherent agent-readiness posture, with a dimension model, JSON Schema, JSON-LD context, vocabulary, and example signal records for representative providers.

## Kin Score — 25.7 / 100 (emerging)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 25.7).

| Facet | Score |
|---|---|
| Discoverability | 74.1 |
| Contract Quality | 52.1 |
| Governance | 25.0 |
| Contract Governance | 25.0 |
| Operational Transparency | 2.6 |
| Developer Ergonomics | 9.5 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 15.4 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## APIs (15)

- **Model Context Protocol (MCP)** — An open JSON-RPC protocol that lets AI agents talk to tools, resources, and prompts through a uniform server surface. MCP is the most direct expression of "an API designed for a...
- **OpenAPI Specification** — The dominant machine-readable contract for HTTP APIs. Presence of a public OpenAPI document — with examples, error schemas, security schemes, and rate-limit headers — is the sin...
- **AsyncAPI Specification** — Machine-readable contract for event-driven APIs (webhooks, message brokers, streaming). Agent-readiness for event surfaces depends on whether the provider ships an AsyncAPI docu...
- **JSON Schema** — The vocabulary that lets an agent validate request and response bodies against typed contracts. Published JSON Schemas (independent of, or embedded in, an OpenAPI) are a strong ...
- **Agent Skills** — A community schema for publishing operational instructions an agent should follow when using a site or API. A provider that ships a `/skills/` directory with a skill index is si...
- **/.well-known/api-catalog (RFC 9727)** — RFC 9727 defines `/.well-known/api-catalog` as the canonical machine entrypoint for discovering an organization's APIs, formatted as an RFC 9264 linkset. Presence of a catalog a...
- **HTTP Message Signatures (RFC 9421)** — A cryptographic signature scheme for HTTP messages, used by the emerging web-bot-auth profile to let agents authenticate themselves to origins. Provider support for verifying or...
- **Web Bot Auth (draft)** — IETF draft layering an "identified bot" profile on top of RFC 9421. A provider that publishes a directory of verified agent identities — or surfaces Web Bot Auth verdicts in its...
- **Content-Usage / AIPREF (IETF AIPREF WG)** — The IETF AIPREF working group's effort to standardise machine-readable AI usage preferences (e.g. `Content-Usage: ai-input=y, ai-train=n`). A provider that publishes explicit AI...
- **Cloudflare Content Signals** — Cloudflare's `Content-Signal` robots.txt directive, complementing the AIPREF drafts. Together they let an origin separate "crawl for search" from "use for AI input" from "use fo...
- **APIs.json** — The APIs.json format describes a provider's API portfolio in one machine-readable document. Publishing `/apis.json` (or `/apis.yml`) at the site root is the agent-readiness equi...
- **OpenID Connect** — Identity layer on top of OAuth 2.0. Agent-readiness for authenticated APIs depends on clear, discoverable OIDC metadata (`/.well-known/openid-configuration`) so agents can negot...
- **Stripe API (reference provider)** — Reference provider for the agent-readiness signal set. Stripe publishes its full OpenAPI, ships idempotency keys, surfaces rate-limit headers, has a consistent error envelope, a...
- **GitHub REST + GraphQL API (reference provider)** — Reference provider with arguably the most extensively-tooled developer surface on the web. Public OpenAPI, GraphQL schema, webhooks, conditional requests, explicit `X-RateLimit-...
- **Twilio API (reference provider)** — Reference provider with strong agent-readiness signals on the messaging side — published OpenAPI, idempotency on resource creation, structured error codes, signed webhooks, stat...

## Security (2)

- **Agent Readiness Domain Security** — TLSv1.3 · HSTS · DMARC
- **Agent Readiness Vulnerability Disclosure** — security.txt · contact published

## Use cases (5)

- **Provider Self-Assessment** — A team auditing their own API surface against a checklist of agent-readiness dimensions
- **Consumer Pre-Integration Review** — An engineering team evaluating whether a third-party API can be driven by an autonomous agent before committing to integration
- **Procurement and RFP Scoring** — A buyer scoring vendor APIs on a normalized agent-readiness rubric during procurement
- **Aggregator Indexes** — A directory or marketplace ranking listed APIs by agent-readiness score to help agent developers pick safe surfaces
- **Standards Coverage Map** — Mapping where each standard (OpenAPI, AsyncAPI, MCP, AIPREF, RFC 9727, RFC 9421) contributes to which dimension

## Tags

Agent Readiness, AI Agents, API Discovery, API Governance, Machine-Readable APIs, MCP, OpenAPI, AsyncAPI

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/agent-readiness/). Scores are computed from the provider's own public artifacts under a published rubric.