# Coolso

**Canonical:** https://apis.io/providers/coolso/  
**Website:** https://coolsotech.com  
**APIs profiled:** 0

Coolso develops wearable gesture-recognition technology. Using patented sensing that detects muscle-vibration signals processed through its own AI model, Coolso recognizes individual finger movements and strength levels with low-latency response, from a wrist-worn device or an ordinary smartwatch's accelerometer and gyroscope without dedicated hardware. Founded by Sheng-Kuei Hsu, Wei-Lin Lee, and Jack Wu and based in Cambridge, Massachusetts, the seed-stage company is backed by 500 Global and Alchemist Accelerator and targets AR/VR interaction, with potential expansion into medical rehabilitation and sports equipment. Coolso publishes no public API, SDK, or developer portal at this time.

## Kin Score — 5.7 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 5.7).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 3.6 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (1)

- **Coolso Domain Security** — no transport/DNS hardening detected

## Tags

Company, Wearables, Gesture Recognition, Artificial Intelligence, Sensors, Augmented Reality, Virtual Reality, Hardware

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/coolso/). Scores are computed from the provider's own public artifacts under a published rubric.
