Cape
Cape is a privacy-first U.S. mobile carrier (mobile virtual network operator) that leases physical tower capacity from major operators but builds and runs its own mobile core and SIMs, enabling privacy-enhancing controls that traditional carriers cannot offer. Features include daily identifier rotation (changing SIM ID numbers to disrupt persistent tracking), minimal data collection, disappearing call logs, secondary phone numbers, SIM-swap protection, network lock, and secure global roaming. Founded in 2022 by John Doyle and Nicholas Espinoza and headquartered in Arlington, Cape serves privacy-conscious consumers, enterprises, and U.S. government agencies, and has raised roughly $190M from investors including Andreessen Horowitz, Bain Capital Ventures, IVP, and Costanoa Ventures. Cape publishes no public developer API; this profile is an API Evangelist network company record enriched from Cape's public web surface.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Cape the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cape scores 19.4/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Cape
Each block below is one kind of artifact we hold for Cape. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Cape — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cape · machine-readable index on apis.io