Cape website screenshot

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.

Cape is profiled on the APIs.io network. Tagged areas include Company, Privacy, Mobile, Telecommunications, and Carrier.

Cape’s developer surface includes support, engineering blog, signup flow, and 14 more developer resources.

🌐 Visit website 📡 Source on GitHub
19.4/100 emerging ▬ flat Agent 7/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
0 APIs
CompanyPrivacyMobileTelecommunicationsCarrierMVNOSecurityConsumer

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 19.4/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 7/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/cape: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Cape Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Cape Vulnerability Disclosure

security.txt · contact published

SECURITY

Cape Trust Center

SOC 2 Type 1

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp
SignUp

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown
WellKnown
 LLMsTxt
LLMsTxt

Access & Security 7

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 Compliance
Compliance
 Security
Security
 VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 TrustCenter
TrustCenter
 SecurityTxt
SecurityTxt

Scroll for all 7

Operate 2

Status, limits, changes, and where to get help

Support
Support
 HelpCenter
HelpCenter

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 3

The organization behind the API

Website
Website
 Blog
Blog
 BlogRSS
BlogRSS

Source (apis.yml)

apis.yml Raw ↑ 
aid: cape
name: Cape
description: 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.
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://cdn.sanity.io/images/9u514z6s/development/608e15873d6f442b9a990c5839a4d37940cbd047-1600x900.png
url: https://raw.githubusercontent.com/api-evangelist/cape/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- bain-capital-ventures
- costanoa-ventures
- ivp
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Privacy
- Mobile
- Telecommunications
- Carrier
- MVNO
- Security
- Consumer
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.cape.co/
- type: Support
  url: https://support.cape.co
- type: HelpCenter
  url: https://support.cape.co
- type: Blog
  url: https://www.cape.co/blog
- type: BlogRSS
  url: https://www.cape.co/blog/rss.xml
- type: SignUp
  url: https://www.cape.co/get-cape
- type: TermsOfService
  url: https://www.cape.co/terms-of-service
- type: PrivacyPolicy
  url: https://www.cape.co/privacy-summary
- type: TrustCenter
  url: https://trust.cape.co/
- type: Compliance
  url: https://trust.cape.co/
- type: Security
  url: https://cape.co/vulnerability-disclosure
- type: VulnerabilityDisclosure
  url: security/cape-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/cape-domain-security.yml
- type: TrustCenter
  name: Cape Trust Center artifact
  url: security/cape-trust-center.yml
- type: SecurityTxt
  url: well-known/cape-security.txt
- type: WellKnown
  url: well-known/cape-well-known.yml
- type: LLMsTxt
  url: llms/cape-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence