Sully AI
Sully AI is a US-based healthcare AI company that ships a portfolio of "AI employees" for clinical and administrative work — including an AI Scribe that turns patient conversations into structured, HIPAA-compliant notes, an AI Receptionist for scheduling and front desk, an AI Triage Nurse for patient engagement, an AI Medical Coder for autonomous ICD-10 coding, an AI Pharmacist, and an AI Consultant for chart prep. The platform integrates with Epic, Cerner, MEDITECH, Athenahealth, Allscripts, Veradigm, and 50+ other EHRs. Beyond the end-user products, Sully exposes a public REST API covering audio transcription (file upload and real-time WebSocket streaming), clinical note generation (SOAP and custom templates), medical coding extraction (ICD-10, CPT, SNOMED), note templates, and a medical consensus alpha feature, with asynchronous results delivered over webhooks. Official Apache-2.0 licensed TypeScript/Node and Python SDKs are published under the sullyai GitHub org, and an Odiggo-maintained sully-api-demo repo showcases end-to-end usage. Sully's revenue model is SaaS subscriptions to healthcare providers, hospitals, and digital health platforms.
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 Sully AI the way a machine reads it — 3 machine-readable artifacts across 1 API, 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 — Sully AI scores 16.0/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 Sully AI
Each block below is one kind of artifact we hold for Sully AI. 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.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sully AI Scribe API
REST API for ambient clinical documentation: upload audio or open a WebSocket stream, generate structured SOAP / custom-template clinical notes, extract medical codes (ICD-10, C...
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.
Resources
Every other property we hold for Sully AI — 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.
Documentation 1
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 5
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/sully-ai · machine-readable index on apis.io