# Tin Can

**Canonical:** https://apis.io/providers/tin-can/  
**Website:** https://tincan.kids/  
**APIs profiled:** 0

Tin Can is a Seattle-based consumer hardware company behind a screen-free, landline-style Wi-Fi phone for kids — no apps, texting, or games, just voice calls with contacts that parents approve through a companion mobile app, with free unlimited calling between Tin Can devices. Backed by Greylock (which led a $12M round in 2025, bringing total funding to roughly $15.5M). Tin Can publishes no first-party developer API; its agent-facing surface is the Shopify-hosted storefront, which exposes a live MCP server, a UCP merchant profile, an llms.txt, and Shopify Customer Accounts OIDC on the tincan.kids domain.

## Kin Score — 23.7 / 100 (emerging)

Scored 2026-08-19 under rubric 0.12.0. Trend: flat (-3.2 from 26.9).

| Facet | Score |
|---|---|
| Discoverability | 57.4 |
| Contract Quality | 0.0 |
| Governance | 18.2 |
| Contract Governance | 18.2 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 19.0 |
| Commercial Clarity | 38.2 |
| Access Clarity | 38.2 |

Regulatory layer — **Telecommunications**: 58.3 (matched via tags).

## Agent readiness — 18.8 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | verified |
| Auth Clarity | yes |
| 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

Self-serve signup — onboarding: self-serve, pricing: unknown, trial: no (confidence: medium).

## MCP servers (1)

- **tin-can-mcp.yml**

## Security (2)

- **Tin Can Authentication** — oauth2/openIdConnect · 1 scheme
- **Tin Can Domain Security** — TLSv1.3 · HSTS · DMARC

## Tags

Company, Consumer, Hardware, Telecommunications, Voice, Kids, Phones

---

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