Incandor
Incandor is a San Francisco based Y Combinator (Spring 2026) startup building behavioral intelligence infrastructure for fraud and abuse detection. Rather than relying on identity verification at account creation, Incandor constructs a behavioral map of every user on a platform from how they physically interact with an app or website — mouse dynamics, keystroke timing, scroll patterns, and on mobile how a device is held. It requires no fraud labels and no enrollment period, working from the first session. At the individual level it identifies account takeovers with greater than 99 percent accuracy; at the population level it separates out coordinated fraud rings, mule operators, shared operators, bots and agents, and coerced or duress sessions. Incandor is delivered as a programmable API and a client-side telemetry SDK rather than a black-box risk score, letting fraud teams combine behavioral signals with their own transaction history, customer records, and business rules. It collects only behavioral signals — not what users type, read, or view — keeping user data private by design. The company was founded by Matthew Yekell (CEO) and Luc Rosenzweig (CTO), both Stanford CS graduates. This profile is maintained by the API Evangelist network; the developer platform is currently early access.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Incandor the way a machine reads it — 1 machine-readable artifact, 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 — Incandor scores 8.3/100 (minimal), with a separate agent-readiness read of 0/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 Incandor
Each block below is one kind of artifact we hold for Incandor. 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 1
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 Incandor — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/incandor · machine-readable index on apis.io