EK
Good distinction. We haven’t run into that response-shape mismatch in our Social Data workflows so far. Each action has a stable BeatAPI ID and input contract, and REST and MCP share the same catalog and response envelope. The data inside is still action-specific, though, so I wouldn’t claim an existing Skill written for any search API will work unchanged.