Daylight

Daylight (Daylight Security) is an AI-native Managed Detection and Response (MDR) provider delivering what it calls Managed Agentic Security Services (MASS) — combining agentic AI with elite human analysts to run security operations end-to-end, from real-time threat detection through Tier 1 triage, deep Tier 3 investigations, and full incident response, 24x7x365. The platform ingests signals across endpoints, cloud, and networks, learns each customer's business context (identity platforms, HR systems, even Slack), and connects into the customer stack (AWS, Google Cloud, Microsoft 365, Snowflake, Slack, Microsoft Teams). Daylight exposes a partner API at api.daylight.ai (OAuth2 / OIDC, Bearer) plus an OAuth-protected Model Context Protocol (MCP) server so security teams can connect investigations to AI assistants such as Claude and Cursor. Daylight is SOC 2 Type II certified and ISO 27001 compliant. Founded in 2024 by Hagai Shapira and Eldad Rudich; backed by Craft Ventures, Bain Capital Ventures, and Maple VC ($40M raised). Added to the API Evangelist network from VC-portfolio discovery.

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.

How we profile Daylight

Each block below is one kind of artifact we hold for Daylight. 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 1

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.

Daylight API

Daylight's partner/product API surface at api.daylight.ai, protected by OAuth2 / OpenID Connect (Bearer token, authorization server at auth.app.daylight.ai). Access is authentic...

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.

daylight-mcp.yml

MCP SERVER

Security 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.

Daylight Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Daylight Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Daylight Scopes

2 scopes · authorizationCode/clientCredentials/refreshToken

2 scopes

SCOPES

Resources

Every other property we hold for Daylight — 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.

← All providers · Data indexed from github.com/api-evangelist/daylight · machine-readable index on apis.io