REST APIs
REST APIs in A²D represent HTTP API contracts that you design, mock, and test alongside MCP Servers and Agent Cards.
What are REST APIs in A²D?
While MCP Servers use the Model Context Protocol (JSON-RPC) and Agent Cards use the A2A protocol, REST APIs represent traditional HTTP APIs with endpoints, methods, paths, and request/response schemas. A²D treats them as first-class agentic assets alongside MCP Servers and Agent Cards.
Key Differences from MCP Servers
| Aspect | MCP Server | REST API |
|---|---|---|
| Protocol | JSON-RPC 2.0 (MCP) | HTTP REST |
| Entities | Tools, Resources, Prompts | Endpoints |
| Request Format | tools/call with arguments | HTTP method + path + body |
| Response Format | MCP content array | Direct JSON response |
| Test Validation Paths | content.0.text.asJson.field | field (direct access) |
When to Use REST APIs
Use REST APIs when you need to:
- Design and mock HTTP API contracts before implementation.
- Test REST endpoints with automated validations.
- Include REST API testing in exploratory sessions alongside MCP and A2A assets.
- Import/export API specifications as part of your design workflow.
How REST APIs Work in A²D
- Define — Create an API with endpoints (method, path, parameters, schemas).
- Mock — Configure mock scenarios with conditional responses.
- Test — Use the Playground, create automated A2TF tests, or run exploratory sessions.
- Publish — Export or publish to Anypoint Exchange.
Next Steps
- REST APIs Feature Guide — Full feature documentation.
- Testing REST API Endpoints — Hands-on testing guide.
- MCP Protocol — Compare with MCP approach.
REST APIs complement MCP Servers and Agent Cards as testable agentic assets in A²D.