# Hydrow

> Hydrow (legally True Rowing, Inc.) is a Boston-based connected-fitness hardware company
> selling the Hydrow indoor rowing machine and the LYQUID strength-training platform, together
> with a subscription to live and on-demand athlete-led workouts filmed on open water.

**Hydrow does not publish a public API.** This file is GENERATED by API Evangelist from an
independent third-party profile of Hydrow's public surface. It is not published by Hydrow and
does not live on a Hydrow host — Hydrow serves no /llms.txt of its own. It exists so that an
agent asking "can I integrate with Hydrow?" gets an accurate, sourced answer instead of
guessing, and so that it does not waste calls probing endpoints that are not there.

## What an agent can actually do with Hydrow

Nothing programmatic, without a partnership. As of 2026-08-22 there is:

- no developer portal, and no documentation of any kind
- no OpenAPI, Swagger, GraphQL SDL, AsyncAPI, Protobuf or WSDL contract
- no first-party SDK in npm, PyPI or RubyGems
- no MCP server, no A2A agent card, no webhooks, no /.well-known/ document
- no API pricing, no API rate limits, no sign-up for API access

Hydrow's own developer-shaped hostnames (api.hydrow.com, developer.hydrow.com,
docs.hydrow.com) resolve only because hydrow.com uses a wildcard DNS record pointing at
Vercel; none of them completes a TLS handshake, so none of them is a service.

## What is real and machine-readable

- Status page (Atlassian Statuspage, fully anonymous JSON API):
  https://status.hydrow.com/api/v2/summary.json
  Also: /api/v2/status.json, /api/v2/components.json, /api/v2/incidents.json,
  /api/v2/scheduled-maintenances.json, /history.rss, /history.atom
  Tracked components are consumer properties — "Hydrow Service", "hydrow.com website",
  "shop.hydrow.com", "Support.hydrow.com". No API component, because there is no API.

## Human surfaces

- Website: https://hydrow.com/ — answers HTTP 429 to non-browser clients on every path.
  The site is up; it simply refuses agents and crawlers. Do not read a 429 here as an outage.
- Help center: https://support.hydrow.com/s/ — a Salesforce Experience Cloud community.
  Article routing is real (a valid article returns 200, an invalid one 404) but every
  response is the same client-rendered shell, so the content is not readable without a
  browser.
- Membership pricing: https://support.hydrow.com/s/article/Hydrow-membership-pricing-1651497389211
- GitHub organization: https://github.com/TrueRowing — 38 public repositories, 34 of them
  forks of third-party libraries pinned for Hydrow's own mobile build. No client library.

## Private backends (do not attempt to use these)

Hydrow runs real production backends for its own iOS/Android apps at
v1.api.prod.hydrow-external.net (AWS API Gateway, blanket 401) and
v2.api.prod.hydrow-external.net (NestJS). They are recorded in this profile only because
contract discovery reached them and found nothing published. They are undocumented, carry no
public terms permitting third-party use, and require member credentials. They are not an
integration path, and an agent must not treat them as one.

## Integration direction

Hydrow's integrations run OUTBOUND: the Hydrow mobile app acts as an OAuth client of Strava
and writes to Apple Health, pushing a member's own workout summaries out to those services.
The integration surface belongs to Strava and Apple, not to Hydrow. If you need Hydrow
workout data, the supported route is a member connecting Hydrow to Strava and you reading
Strava's API.

## Correcting this

If Hydrow publishes an API, or if anything above is wrong, open an issue at
https://github.com/api-evangelist/hydrow or email info@apievangelist.com. Corrections and
re-scores are free and require no relationship.

Generated: 2026-08-22 | method: generated | source: this repository's probed artifacts