Build with the work already logged.
Connect an AI client to your own record with Agent Access, or use the separate read-only TRENBot integration. Each has its own authentication and permissions; choose the guide for the connection you are building.
Using your own AI? Start with Agent Access.
Pro members can connect a compatible AI client to their own Paggered record through OAuth. Choose read access, optionally allow proposed changes, and approve each batch in Paggered. This is a separate contract from the TRENBot pilot below.
Read the Agent Access guideTRENBot: the shortest path to data
Keep the token on your server, send it as a bearer credential with the verified Discord channel context, and request one of the six documented routes. Every successful response uses snake-case JSON and carries a request ID.
curl --request GET \
--url https://paggered.app/api/v1/stats \
--header "Authorization: Bearer $PAGGERED_API_TOKEN" \
--header "X-Paggered-Platform: discord" \
--header "X-Paggered-Platform-User-Id: $DISCORD_USER_ID" \
--header "X-Paggered-Guild-Id: $DISCORD_GUILD_ID" \
--header "X-Paggered-Channel-Id: $DISCORD_CHANNEL_ID" \
--header "Accept: application/json"What the pilot can read
/api/v1/meDisplay name, unit preference, and timezone.
/api/v1/statsThis week, rolling 30 local days, and consecutive active weeks.
/api/v1/workoutsCompleted workout summaries in stable newest-first order.
/api/v1/workouts/{id}Exercises, completed set performance, and historical PR indicators for one owned workout.
/api/v1/saved-workoutsSaved workout titles and exercise counts.
/api/v1/saved-workouts/{id}Ordered exercises, sets, reps, and rest for one saved workout.
What is deliberately outside it
This contract is useful because its boundary is narrow. It does not expose free-text coaching context or let a caller search for another Paggered account.
- descriptions and notes
- feedback and RPE
- recovery data
- chat context and goals
- nutrition and body metrics
- billing and social graph
- schedule identifiers
- internal user IDs
There is no self-service key creation, public developer OAuth, browser CORS, username lookup, public write access, or webhook in this pilot. Account owners connect through Paggered's interactive Discord consent flow; developers do not receive user tokens.