RPC API
Action-based (JSON-RPC 2.0)
Why it exists
- Explicit intent (method name instead of HTTP verb + path)
- Less ceremony than REST for internal services
Tradeoffs
- Not resource-oriented; caching is less natural
POST /api/rpc — body: { "jsonrpc": "2.0", "method": "...", "params": {}, "id": 1 }