# Nanno

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

Nanno was an on-demand babysitting and childcare marketplace startup, founded in 2016 and based in Denver, Colorado, that connected parents with vetted, background-checked sitters through a consumer mobile app (a "childcare on demand" model). Backed by 500 Global among others, the company paused operations at the end of 2021 amid pandemic-driven labor and childcare-market disruption, and its technology and assets were acquired by household-management startup Call Emmy in May 2022. The Nanno corporate entity persists but no longer operates its platform; nanno.com no longer serves a live site. Nanno was a consumer app and never published a public developer API, SDKs, or developer documentation. This profile is retained as a network stub for historical/lineage purposes and carries no live API surface to enrich.

## Kin Score — 5.0 / 100 (minimal)

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

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| 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).

## Tags

Company, Childcare, Babysitting, Marketplace, Consumer App, On-Demand, Defunct, Acquired

---

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