Build personalized health products with one API for every wearable. Access wearable data, open health scoring algorithms, and structured context your AI can reason with. Self-hosted, open-source, MIT licensed.
Mine says 68 today. Green zone apparently. But 68 out of what? Compared to what baseline? Why 68 and not 71? Should I train hard or take it easy? The app doesn't say. It just shows me the number and a vague color.
Most wearables give you a score with zero explanation of how they got there. Black box. Proprietary algorithm, tuned for some average user that probably isn't you. You either trust it or you don't, but you have no way to verify it either way.
I wear a WHOOP. I've coached people on movement and sleep for many years and I still can't answer that question for myself. The algorithm is locked. You get a number, you trust it, you stop there.
When we built Open Wearables, we decided the scoring layer should work differently. Sleep Score and Resilience Score shipped in v0.5 - every coefficient, every threshold, every weighting is in the repo and you can fork them, tune for endurance athletes or elder care or clinical populations. Moreover, you run them on your own infrastructure and the same algorithms feed the MCP layer so AI coaching can cite the actual data behind a recommendation instead of approximating.
Imagine this: Both devices on the same wrist, same night of sleep, same morning. One shows green, one shows red. And neither will tell you how it decided. That's not a hardware problem. It's an algorithm problem. Different weightings, different baseline calculations, different thresholds - all proprietary, all invisible. You're left choosing which black box feels more right today. The reason we open-sourced the scoring algorithms in Open Wearables wasn't just philosophical. It's because conflicting scores are meaningless without context, and context requires transparency. When you can see exactly how a Resilience Score weights HRV versus sleep duration versus resting heart rate, you can actually reason about the discrepancy. Has anyone else hit this? Curious whether people trust one device more than others and why.
I was recently reflecting on the open-source projects that bring massive daily value versus those that are just cool, experimental concepts. I'd love to hear what your tech stack looks like.
We launched Open Wearables on Product Hunt today. For teams building AI agents, coaches, or copilots in health, OW turns raw wearable streams into the structured, scored, time-series context an LLM can actually reason over.
Something we kept running into across projects: wearable integration eats months and adds zero product value.
Every provider does things differently. Garmin sends XML. Whoop sends JSON but paginates differently than Oura. Apple Health needs on-device processing. Samsung has its own SDK. Different auth flows, different rate limits, different webhook formats.
