openGym

What it provides

Connect an existing HTTPS deployment, with a scoped token where the service requires one. Heavy jobs stay on that service instead of using bot memory. Requires your own HTTPS openGym deployment and a paired non-admin profile token. The token allows profile writes too; the examples only read data. Sessions expire after 90 days by default and require manual credential replacement. The bot receives a client; openGym is not hosted or installed for you.

Connection requirements

Run openGym outside the bot and enter its HTTPS origin without an /api suffix. Sign in to a regular, non-admin profile, then open Settings → Pair the mobile app. Redeem the one-use code within five minutes with POST /api/pair/redeem and a JSON body {"code":"YOUR_CODE"}; copy the returned token privately, keep Bearer selected, and paste it below. This is a profile session credential, not a read-only API key: it also permits writes to that profile. The examples only read your synced workout, routine, and body-weight data. Sessions last SESSION_DAYS (90 days by default). The connector does not automatically save renewed tokens from /api/me; re-pair and replace the credential when it expires or is revoked. Data stays on your openGym host until the bot requests it. Its local stdio MCP server is separate and is not used by this REST connection.

Protocol

REST / OpenAPI

Endpoint

https://opengym.example.com

Authentication

bearer

Where to add it

Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.

Related Analytics & research