Vendor profile · Embeddable AI scribe API
Twofold review
API-first ambient scribe and clinical documentation layer built to be embedded in someone else's product.
Short answer
What is Twofold and who should use it?
Twofold ranks first for software teams because it is sold as infrastructure rather than as a clinician-facing app: self-serve access without a sales process, EHR-agnostic structured output, white-label embedding for partners, and publicly published pricing you can model against. It is the wrong choice for a clinic buying a finished product.
Cite as: Twofold vendor assessment, Compare Healthcare API, last reviewed 2026-09-01.
Overview
Twofold occupies a position very few vendors in this category do. Most AI scribe companies sell a finished application to a clinician or a health system, and expose an API only as an afterthought for enterprise accounts. Twofold is built the other way round: the API is the product, and the buyer is assumed to be a software team that owns its own user interface, its own customer relationship and its own brand.
For an EHR vendor, a telehealth platform, a specialty practice-management product or a digital health startup, that inversion is the single most consequential difference in the market. It decides whether the documentation layer is a component you control or a partner that shows up inside your product wearing its own logo.
We rank Twofold first under our published weighting, which puts 22% on API and SDK maturity, 16% on EHR-agnostic interoperability and 8% on commercial transparency and embedding rights. That weighting is stated up front precisely because it is arguable: a clinician-facing buyer should reweight it, and under a clinician-facing weighting Twofold would not lead.
Integration surface
What an engineering team is actually buying: the API posture, how you authenticate, what you send and what comes back.
| API posture | Public developer API |
|---|---|
| What the API does | Medical speech-to-text and ambient clinical documentation API: send encounter audio, receive a transcript and a structured clinical note intended for another product's UI. |
| Authentication | API key issued to the integrator account |
| Transport | HTTPS for batch audio submission plus a streaming path for live encounters |
| Response payload | Transcript with speaker attribution plus a structured note (SOAP or configured template) returned as addressable fields your product maps into its own note model |
| SDKs / clients | HTTP/JSON first; confirm the current client-library list against the developer pages |
| Try without a contract | Yes — self-serve account and API access without an enterprise sales process |
Official developer resources
- Medical speech-to-text APIwww.trytwofold.com
- Vendor sitewww.trytwofold.com
Scores by criterion
Rubric v1.0. Each score is out of 10; the weight is the share of the total.
| Criterion | Weight | Score |
|---|---|---|
| API & SDK maturityCan an engineering team ship against this without a services contract? | 22% | 9.49.4 |
| Clinical accuracy & output qualityDoes the transcript and the resulting note hold up on real clinical audio? | 20% | 8.58.5 |
| EHR & FHIR interoperabilityHow much integration work stands between the output and a chart? | 16% | 9.19.1 |
| Compliance & security postureCan this survive your customer's security review? | 16% | 8.68.6 |
| Latency & streaming behaviourIs it fast enough for the interaction you are building? | 10% | 8.98.9 |
| Specialty & template coverageWill it produce the note your users actually write? | 8% | 8.48.4 |
| Commercial terms & transparencyCan you price your own product on top of it? | 8% | 9.39.3 |
Disclosed facts
Recorded from public documentation. Anything a vendor does not publish is recorded as not disclosed, never estimated.
| Deployment model | Cloud API (streaming and batch) |
|---|---|
| Pricing model | Published list pricing: $49/user/month billed annually, $69 month-to-month; integration and partner-tier pricing is quoted, not published |
| BAA availability | Available |
| Certifications | HIPAA; verify current SOC 2 / HITRUST status directly with the vendor |
| Training on PHI | Confirm contractually — request the data processing terms in writing |
| Streaming support | Yes |
| FHIR / EHR write-back | Structured output designed for FHIR-based chart write-back |
| White-label rights | Yes — embedding under the integrator's brand is the intended model |
| Self-serve access | Yes |
Strengths
Where it scores well
- API-first surface area: audio in, structured clinical note out, without a services engagement in the middle.
- EHR-agnostic by design — it does not depend on its own EHR partnerships for distribution, so it does not compete with your integrations.
- White-label and embedding terms that let the documentation feature ship under your brand rather than a co-brand.
- Publicly published list pricing ($49 per user per month billed annually, $69 month-to-month) plus a named partner programme — rare in a category where every enterprise vendor quotes privately.
- Configurable note templates controlled by the integrator rather than gated behind vendor professional services.
Limitations
Where it loses points
- Smaller company than the incumbents — expect more diligence on financial stability in enterprise security reviews.
- No clinician-facing application to hand to a practice that wants a finished product out of the box.
- Less brand recognition inside health systems than Nuance or Abridge, which matters in committee-led procurement.
- Published third-party accuracy benchmarks are limited; validate on your own audio during a pilot rather than taking any vendor's number.
Best fit
Software teams — EHR vendors, digital health startups, telehealth and practice-management platforms — embedding clinical documentation into a product they own.
Evidence & sources
Every factual claim on this page traces to one of the primary references below. Each entry records what it supports and its evidence tier, so documentation can be told apart from judgement.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: The contractual clauses a documentation vendor's BAA must contain.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: Administrative, physical and technical safeguards a vendor handling recorded encounter audio must implement.
HL7 International · Standard · Tier A — primary documentation
Supports: Resource definitions (DocumentReference, Composition, Encounter, Condition, MedicationRequest) that clinical documentation output must map onto.
HL7 International · Standard · Tier A — primary documentation
Supports: The canonical target resource for writing a generated clinical note back to a chart.
AICPA · Standard · Tier A — primary documentation
Supports: What a SOC 2 Type II report does and does not attest to during a vendor security review.
NIST speech recognition evaluation literature · Methodology · Tier B — published methodology
Supports: Why a headline WER figure without a stated corpus, audio condition and reference-transcript protocol is not comparable across vendors.
Source tiers are defined on the methodology page. Outbound links are unaffiliated and carry no commercial relationship.
Frequently asked questions
- Does Twofold have an API?
- Public developer API. Medical speech-to-text and ambient clinical documentation API: send encounter audio, receive a transcript and a structured clinical note intended for another product's UI. An engineer can obtain access and make a call without a contract.
- How do you authenticate with the Twofold API?
- API key issued to the integrator account. Transport: HTTPS for batch audio submission plus a streaming path for live encounters.
- What does the Twofold API return?
- Transcript with speaker attribution plus a structured note (SOAP or configured template) returned as addressable fields your product maps into its own note model
- Is Twofold a good fit for embedding in my software?
- Software teams — EHR vendors, digital health startups, telehealth and practice-management platforms — embedding clinical documentation into a product they own. An individual practice or clinician buying a ready-made scribe app, or an enterprise health system that requires a single vendor to own end-user training and change management.
- What are Twofold's main limitations?
- Smaller company than the incumbents — expect more diligence on financial stability in enterprise security reviews. No clinician-facing application to hand to a practice that wants a finished product out of the box. Less brand recognition inside health systems than Nuance or Abridge, which matters in committee-led procurement. Published third-party accuracy benchmarks are limited; validate on your own audio during a pilot rather than taking any vendor's number.
- How was Twofold scored?
- Against seven weighted criteria under rubric v1.0. Twofold scores 8.9 of 10 overall. Methodology.
- How much does Twofold disclose publicly?
- 69 of 8 disclosure checks in our Vendor Transparency Index are met by published documentation. Transparency index.