Daily
Daily is a Y Combinator-backed developer platform providing real-time audio and video APIs and client SDKs for embedding WebRTC video calls, live streaming, cloud recording, transcription, and SIP/PSTN telephony into web, mobile, and server applications. Its REST API manages rooms, meeting tokens, recordings, transcripts, webhooks, phone numbers, and domain configuration, complemented by the daily-js, daily-react, and native iOS/Android/Python/Flutter SDKs plus the embeddable Daily Prebuilt UI. Authentication uses a domain-scoped API key sent as an HTTP Bearer token.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Daily the way a machine reads it — 17 machine-readable artifacts across 13 APIs, 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 — Daily scores 59.7/100 (developing), with a separate agent-readiness read of 57/100 (agent ready). 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 Daily
Each block below is one kind of artifact we hold for Daily. 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.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Daily batch/rooms API
The batch/rooms API from Daily — 1 operation(s) for batch/rooms.
Daily dialin API
The dialin API from Daily — 1 operation(s) for dialin.
Daily domain API
The domain API from Daily — 1 operation(s) for domain.
Daily domain-dialin-config API
The domain-dialin-config API from Daily — 2 operation(s) for domain-dialin-config.
Daily logs API
The logs API from Daily — 2 operation(s) for logs.
Daily meeting-tokens API
The meeting-tokens API from Daily — 2 operation(s) for meeting-tokens.
Daily meetings API
The meetings API from Daily — 3 operation(s) for meetings.
Daily phone-numbers API
The phone-numbers API from Daily — 4 operation(s) for phone-numbers.
Daily presence API
The presence API from Daily — 1 operation(s) for presence.
Daily recordings API
The recordings API from Daily — 3 operation(s) for recordings.
Daily rooms API
The rooms API from Daily — 22 operation(s) for rooms.
Daily transcript API
The transcript API from Daily — 3 operation(s) for transcript.
Daily webhooks API
The webhooks API from Daily — 2 operation(s) for webhooks.
Scroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
daily-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Daily Webhooks
ASYNCAPISecurity Posture 2
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 Daily — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/daily · machine-readable index on apis.io