Therabody
Therabody is a Los Angeles-based wellness technology company founded in 2016 by Dr. Jason Wersland, best known for inventing the Theragun percussive therapy device. Its product ecosystem spans percussive therapy (Theragun), pneumatic compression (RecoveryAir), electrical stimulation (PowerDot), vibration therapy (Wave) and the Therabody companion app. Therabody publishes no traditional developer program, but its direct-to-consumer storefront at therabody.com runs on Shopify and exposes a substantial machine-readable commerce surface: an open Storefront GraphQL API, a Universal Commerce Protocol (UCP) MCP server for agent-driven catalog search, cart and checkout, a customer-account MCP server for order status and returns, OAuth 2.0 / OpenID Connect discovery, and published agent instructions at /llms.txt and /agents.md.
Therabody publishes 3 APIs on the APIs.io network. Tagged areas include Company, Wellness, Health, Consumer Products, and E-Commerce.
Therabody’s developer surface includes engineering blog, support, signup flow, authentication, and 16 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Therabody UCP Commerce MCP
Therabody's agent-facing commerce server, implementing the Universal Commerce Protocol (UCP) shopping service over MCP on the Therabody storefront host. Anonymous tools/list ret...
Therabody Storefront GraphQL API
The Shopify Storefront GraphQL API served from the Therabody US storefront host. Anonymous introspection is open and returns 416 types across 35 query root fields covering produ...
Therabody Customer Account MCP
Therabody's customer-account MCP server on account.therabody.com, exposing four post-purchase tools: most-recent order status, order status by order number, store credit balance...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
therabody-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API