# Kyte

**Canonical:** https://apis.io/providers/kyte/  
**APIs profiled:** 0

Kyte was a full-stack technology-operations company that delivered rental cars on demand to the customer's door, positioning itself for any trip longer than a rideshare — a car for a day, a few days, or longer — with no rental counters, no lines and no paperwork. Headquartered in San Francisco, the company combined a consumer mobile and web booking experience with its own fleet and delivery operations ("bits and atoms"), and at its peak operated in 14 US markets delivering tens of thousands of trips per month. It was a growth-stage portfolio company of Anthemis under that firm's Data, Tech and Infrastructure thesis. Kyte was a consumer-facing operator and never published a public developer program, API, SDK or developer portal, and as of this enrichment pass its web properties no longer serve the company.

## Kin Score — 5.0 / 100 (minimal)

Scored 2026-08-20 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, Mobility, Transportation, Car Rental, Vehicle Delivery, Consumer; Marketplace, Logistics, Travel, Defunct, No Public API

---

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