Known
Known is a voice-first, swipeless dating application founded in 2025 by Celeste Amadon and Asher Allen and headquartered in San Francisco, California. Instead of profiles, feeds, queues, and swiping, Known onboards users through a voice-AI interview and then sends one curated introduction at a time, with a 24-hour acceptance window on both sides. When both people accept, Known helps pick a restaurant that fits both sets of preferences and checks calendar availability, then collects a short post-date check-in to refine future matches. The company optimizes for in-person dates rather than engagement, and has raised $9.7M from Forerunner Ventures, NFX, and other investors. The product is iOS-only in the United States today, with waitlists for Android and for Apple users outside the US. Known publishes no public developer program, API, or SDKs; it does publish a first-party llms.txt describing the product for AI agents.
Known is profiled on the APIs.io network. Tagged areas include Company, Consumer, Dating, Mobile, and Voice AI.
Known’s developer surface includes support, signup flow, legal docs, and 13 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Apple Accessory & Device Ecosystem (MFi, Matter, Apple partners) | undeclared | - | - | - |
| Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.