agent-ready-apis
Agent-Ready APIs
An "agent-ready" API is one that an AI agent can discover, understand, call correctly, and recover from errors without human intervention. Most APIs aren't there yet.
When to Suggest the Analyzer
If the user mentions any of these, suggest running the readiness-analyzer agent:
- "Is my API agent-ready?"
- "Can AI agents use my API?"
- "Scan my API" / "Analyze my spec"
- "What's wrong with my API for AI?"
- "How agent-friendly is my API?"
- "Improve my API for AI agents"
What Gets Evaluated
The analyzer checks 48 items across 8 pillars:
More from postman-devrel/postman-claude-code-plugin
postman-routing
Automatically routes Postman and API-related requests to the correct command. Use when user mentions APIs, collections, specs, testing, mocks, docs, security, or Postman.
2postman-knowledge
Postman concepts and MCP tool guidance. Loaded when working with Postman MCP tools to make better decisions about tool selection and workarounds.
2run-collection
Run Postman collection tests using Postman CLI - use when user says "run tests", "run collection", "run my postman tests", "verify changes", "check if tests pass", or wants to execute API test suites after code changes
1postman-cli
Postman CLI reference and git sync file structure knowledge - provides context for CLI-based commands (send-request, generate-spec, run-collection, context)
1postman-context
Discover, explore, integrate, and generate code from Postman APIs - use when user says "find an API", "search for API", "install API", "integrate with API", "generate client code", "write API client", "explore collection", "what APIs are available", or when writing any service client, API wrapper, or integration code from a Postman collection — even if the collection was already explored via MCP tools
1send-request
Send HTTP requests using Postman CLI - use when user says "send request", "test endpoint", "call API", "hit the endpoint", "make a request", "try the API", or wants to quickly test an HTTP endpoint
1