Klarify
Klarify is a San Francisco and Canada based mental-health technology company building an AI assistant, "Klara", for licensed therapists. The product handles the administrative and operational work around therapy rather than the therapy itself: an AI scribe that turns recorded sessions into structured clinical notes across 20+ note formats, treatment-plan generation, clinical letters and assessment reports, insurance claim filing and form completion, session preparation, between-session client resources and worksheets, supervision prep, and visual session mindmaps, with support for many languages. Klarify also operates a public directory of licensed therapists and clinics across Canada and the US, where profiles, FAQs, and long-form articles are authored and verified by the clinicians themselves. The company states HIPAA, PIPEDA, PHIPA, and UK GDPR compliance, stores permanent records in Canada, deletes session audio after 14 days, and does not train models on customer session data. Founded in 2024 by Moody Abdul (CEO, previously co-founder of Circleback.ai) and Alexander Bergholm (CTO, formerly LLM infrastructure at Workday), Klarify is part of Y Combinator's Spring 2026 batch. Klarify publishes no public developer API: its llms.txt explicitly marks paths under /api/ as internal infrastructure.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Klarify 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 — Klarify scores 25.1/100 (emerging), 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 Klarify
Each block below is one kind of artifact we hold for Klarify. 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 Klarify — 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 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/klarify · machine-readable index on apis.io