Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Freed website screenshot

Freed

Freed is a San Francisco-based AI medical scribe and clinician assistant designed to reduce the documentation burden on healthcare providers. The product listens to patient visits and generates SOAP-style clinical notes, visit summaries, patient instructions, referral letters, and ICD-10 / CPT coding suggestions, then transfers the finalized note into the clinician's EHR via a browser-resident agent. Freed was founded in 2023 by former Facebook engineers Erez Druk (CEO) and Andrey Bannikov (CTO) after Druk's wife, a practicing family physician, experienced the daily toll of manual charting. The company is consumer self-serve: clinicians sign up for a 7-day free trial and then a monthly Starter, Core, Premier, or custom Groups plan with no enterprise sales required. As of 2025 Freed reported more than 20,000 paying clinician users and raised a $30M Series A led by Sequoia Capital, bringing total funding to $34M. The platform is HIPAA-compliant, SOC 2 Type II certified, and HITECH-ready; patient recordings are not stored. Rather than ship a traditional public REST API, Freed pursues an "anti-integration" model in which a Chrome-extension AI agent navigates any web-based EHR (Athena, Tebra, PracticeFusion, TherapyNotes, SimplePractice, Elation, AdvancedMD, Cerbo, and others) to place the finished note in the correct fields. There is no public developer API, SDK, or open-source release.

human only

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.

Kin Score

API Evangelist profiles Freed the way a machine reads it — 2 machine-readable artifacts, 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 — Freed scores 13.1/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 13.1/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 3.7 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Freed

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

Freed Ai Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Freed Ai Trust Center

SOC 2, HIPAA

SECURITY

Resources

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

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 3

Properties that don't map to a standard resource type

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