COROS's developer-access guidance distinguishes self-service MCP development from the Partner API path for multi-user integrations. The COROS Training discussion should name which model is intended.
Confirm authorization and onboarding requirements before promising account synchronization. Test revocation and missing activity data without interpreting an absent record as evidence about a person's training or health.