Hardi · All plans
Your agent. Your workouts. Your planning.
Connect your agent through MCP or CLI to your personal workspace. Authorize the actions you want; they run autonomously within your Free, Plus or Pro plan quotas.
Workouts
Create, edit, duplicate, organize, move to Trash and restore.
Folders
Create, rename and organize your library.
Calendars
Create and use personal calendars. Authorize specific calendars or all your personal calendars, current and future.
Planning
Organize sessions, notes, rest days, cycles and week templates.
Preferences and settings
Adjust programming rules within your plan, units, language and notifications.
Results
Read your activity and record personal results. With separate permission, read participant results on your workouts.
Explicit, revocable access
Choose each permission, accessible calendar and library folder during consent. Select no expiration or 1, 7 or 30 days, and revoke access at any time. Existing connections keep their permissions and duration. Dated changes can be limited to today and future dates. Optional simulation, separate MCP operations, atomic CLI batches, activity history and conditional seven-day undo. Later changes or results can prevent undo. Result entries use a fresh version for corrections and have no undo.
No access to Teams, messages, other users’ personal history, private coach notes, billing, exports or public-link management. Participant results stay within your coach view of authorized workouts. No Hardi Energy is consumed. Calendar edits may appear on existing public calendar links.
Connect your agent
- Use your active, completed and email-verified Hardi account on Free, Plus or Pro.
- Open Settings > AI connection to connect ChatGPT or use the CLI. The ChatGPT directory listing is being prepared.
- Authorize the connection in Hardi and select its permissions.
npm install --global ./hardi-cli-2.1.3.tgz hardi auth login --environment live --name "My agent" hardi context --json hardi actions simulate --file actions.json --json
Requires Node 22.23.4 or later in the Node 22 line. Evaluation archive; no public npm release. System credential store, or explicit file storage for headless hosts. Connecting a verified Hardi account requires no paid plan or invitation.
Agent documentation
Actions and permissions
| Action | Scopes |
|---|---|
| calendar.create | actions:read, planning:read, calendars:create |
| training.performance.create | actions:read, training:read, training:write |
| training.performance.update | actions:read, training:read, training:write |
| training.result.upsert | actions:read, training:read, training:write, workouts:read |
| preferences.update | actions:read, preferences:read, preferences:write |
| settings.update | actions:read, settings:read, settings:write |
| workout.create | actions:read, catalog:read, workouts:read, workouts:create |
| workout.update | actions:read, workouts:read, workouts:update |
| workout.duplicate | actions:read, workouts:read, workouts:create |
| workout.move | actions:read, workouts:read, workouts:update, folders:read |
| workout.trash | actions:read, workouts:read, workouts:delete |
| workout.restore | actions:read, workouts:read, workouts:restore |
| folder.create | actions:read, folders:read, folders:write |
| folder.update | actions:read, folders:read, folders:write |
| folder.reorder | actions:read, folders:read, folders:write |
| folder.trash | actions:read, folders:read, folders:delete |
| folder.restore | actions:read, folders:read, folders:write |
| planning.add | actions:read, planning:read, planning:create, workouts:read |
| planning.update | actions:read, planning:read, planning:update, workouts:read |
| planning.move | actions:read, planning:read, planning:update |
| planning.reorder | actions:read, planning:read, planning:update |
| planning.swap | actions:read, planning:read, planning:update |
| planning.copy | actions:read, planning:read, planning:create, workouts:read |
| planning.shift | actions:read, planning:read, planning:update |
| planning.remove | actions:read, planning:read, planning:delete |
| planning.note | actions:read, planning:read, planning:create |
| planning.edit_note | actions:read, planning:read, planning:update |
| planning.remove_note | actions:read, planning:read, planning:delete |
| planning.rest | actions:read, planning:read, planning:create |
| planning.remove_rest | actions:read, planning:read, planning:delete |
| cycle.create | actions:read, planning:read, cycles:read, cycles:write |
| cycle.update | actions:read, planning:read, cycles:read, cycles:write |
| cycle.delete | actions:read, planning:read, cycles:read, cycles:delete |
| template.create | actions:read, templates:read, templates:write |
| template.update | actions:read, templates:read, templates:write |
| template.add_workout | actions:read, templates:read, templates:write, workouts:read |
| template.move_workout | actions:read, templates:read, templates:write |
| template.remove_workout | actions:read, templates:read, templates:delete |
| template.delete | actions:read, templates:read, templates:delete |
| planning.apply_template | actions:read, planning:read, planning:create, templates:read, workouts:read |
Up to 10 actions, 50 objects and 28 sessions per batch. Technical caps apply alongside plan quotas.
Manage my connections