# Reken

**Canonical:** https://apis.io/providers/reken/  
**Website:** https://reken.ai  
**APIs profiled:** 0

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.

## Kin Score — 11.8 / 100 (emerging)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 11.8).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| Commercial Clarity | 34.2 |
| Access Clarity | 34.2 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (1)

- **Reken Domain Security** — TLSv1.3 · HSTS · DMARC

## Tags

Company, Artificial Intelligence, Security, Cybersecurity, Fraud Detection, Anti-Phishing, Deepfakes, Trust and Safety, On-Device AI

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/reken/). Scores are computed from the provider's own public artifacts under a published rubric.