Reken
Reken is an AI security company building a trust layer for the Internet to combat generative-AI-enabled fraud, phishing, scams, deepfakes, and automated social engineering. Co-founded by Shuman Ghosemajumder (who founded Google's Trust & Safety group) and Rich Griffiths, both formerly of Shape Security, Reken centers on the on-device Reken Private Core: the Reken Model Zero detection ensemble, the Reken Trust Sensor for verifying human activity, and an embedded Reken API that lets applications connect to the core while keeping data on-device with local AI models and zero AI token cost. Protected applications form the Reken Network, a self-assembling zero-trust mesh. The company is pre-launch, offering an Early Access Program; it does not yet publish a public developer API, SDKs, or documentation.
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 Reken 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 — Reken scores 13.6/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 Reken
Each block below is one kind of artifact we hold for Reken. 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 Reken — 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 1
Portal, sign-up, and the first successful call
Access & Security 1
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/reken · machine-readable index on apis.io