The Anatomy of a Cassette

Tapes has introduced open-source cassettes, independently deployed microservices that extend its AI-data platform through a shared API namespace and OpenAPI-based discovery. A cassette exposes its own API and OpenAPI specification, including an `x-tapes-cassette` manifest that defines metadata, dependencies, configuration, health checks, proxy paths, and compatibility requirements, allowing Tapes to admit and re-serve its capabilities under `/v1/cassettes/...`. The example prompt cassette retrieves the first captured user prompt from a specified session by querying Tapes trace data, and its functionality becomes automatically discoverable through the Tapes API and `tapesctl` command-line client. Cassettes can be run alongside Tapes and Postgres locally, including through Docker Compose, while remaining independent of Tapes’ implementation language or deployment model. Tapes also supports exposing cassette functions as MCP tools through an `x-tapes-mcp` OpenAPI extension, although the current v1alpha1 standard only converts POST routes into MCP tools, requiring adaptations for operations that would otherwise use GET requests.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.