SteadyMD sells the part of a telehealth program you cannot see. The part you can see is the part you build.
SteadyMD's homepage headline is "We power your telehealth services in all 50 states". What it powers is the clinician bench and the operations behind it. That makes it the fourth shape on this track. Healthie is the chart. MD Integrations is the medicine with a checkout attached. OpenLoop is the whole clinic with your logo on it. SteadyMD is the workforce and the workflow engine, and it hands you the screen.
Its documentation is public, at docs.steadymd.com, with an `llms.txt` index and every page available as Markdown. The marketing site puts the same material behind a "Request API Documentation" form, which you do not need. Every claim below is read out of SteadyMD's own pages and linked so you can check it. Nothing here is medical or legal advice.
What does SteadyMD own?
The clinicians, and everything it costs to keep them. The homepage describes "Hundreds of active board-certified doctors and nurse practitioners in all 50 states." The clinical operations page lists what sits behind them: recruiting, hiring and training, forecasting and capacity planning, scheduling, "a 24/7 supervising physician" for nurse practitioners, licensing and credentialing, and "malpractice insurance for all our clinicians." The routing is theirs too: the Digital Clinic page says visits go to clinicians who are "Trained and assigned on your program", "Licensed in the state where the patient is located" and "Available at the time needed".
The protocols. The clinical operations page offers three doors: "We review your clinical protocols, work with you to enhance those protocols, or develop protocols from scratch." Whichever door you take, the protocol is what the intake has to satisfy and what the clinician follows.
The workflow. The docs introduction says it plainly: "The SteadyMD Platform is a workflow system." Each program is configured with consult types, and "Partners cannot create consults for Consult Types not supported by the program." Business hours, response time SLAs, the booking buffer and the 15 day scheduling window are set with SteadyMD, not in your code.
The decision to see the patient. A consult can come back rejected for an administrative reason or referred out for a clinical one, each with a reason slug your system has to handle. The published reject reasons include an age ineligible for the condition, a failed identity check, a duplicate visit, an incomplete intake and an unsupported state. Pediatrics is off unless you ask: "By default, patients under the age of 18 are not eligible for care through SteadyMD."
The lab menu. For direct to consumer labs, "SteadyMD will manage the exact tests and laboratories are available for ordering."
The company. SteadyMD, Inc. has been owned by DocGo since October 20, 2025. DocGo's 8-K reports "an aggregate purchase price of up to $25 million, consisting of $12.5 million in cash payable at the closing" and up to $12.5 million as an earn-out.
What stays yours?
Find every sentence in the documentation that offers you a choice, because that is a thing you now own. SteadyMD's docs are unusually generous with them.
The patient interface. This is the one that sets the build. The modalities page: "Messaging requires partners to design and build the patient interface to interact with our APIs." If your program runs on asynchronous messaging, the screen the patient types into is yours to build, host and maintain. Video and scheduling are a choice: "Use our video element" or "Use your own video platform", and the scheduling element or raw availability from the API. SteadyMD also runs a white label patient experience behind single sign-on, which is the door that hands the most back.
The intake. The intake guide says the questionnaire "should include all of the clinically necessary information regarding a patient for the care being requested as agreed in the clinical protocol." The urgent care guide is firmer: the clinical intake questionnaire "must include hard stop for red listed conditions that cannot be treated virtually", and "should support branching question logic, pharmacy selection, and image upload". The form that decides who gets stopped is yours to build to their specification. So is the patient's location, which the key terms say "should be validated each time the patient requests a virtual visit."
The pharmacy, with a condition. The preferred pharmacy guide: "Partners may have a partnership pharmacy, however the patient must be able to opt for their pharmacy of choice." You collect that choice during intake and send it on the episode of care, and the guide says a partnered pharmacy must be set up in Surescripts' staging environment before an end to end test. The prescription record that comes back carries a written date and an effective date, and "Patients cannot fill prescriptions until the effective date." SteadyMD never touches the drug. Your pharmacy integration and cold chain are your contract with the pharmacy, not with SteadyMD.
The money. On the API path the checkout is yours end to end. On the white label, the Stripe guide says it "can plug into a partner's Stripe account", that "SteadyMD configures what price the patient pays per program visit type", and that "Operational processes are required to manage refunds when appropriate as determined by Customer Support." The SSO guide adds a refund you do not choose: a patient outside the agreed age range "will be automatically rejected and the patient will be refunded." The scheduling guide adds a fee you will have to explain: visits "rescheduled or canceled within 24 hours of the appointment time will generally incur fees." The card runs through your account. The rules that charge or refund it are negotiated.
The notifications. SteadyMD can text or email the patient directly at the important steps of a visit, from "Visit scheduled" to "Visit starting now", or stay silent while you send them. Either way the platform events arrive at your endpoint over AWS SNS and your system decides what the patient hears.
Identity. External, where the partner attests it verified the patient: "External verifications require agreement between legal teams before this option can be used." Or internal, where a clinician checks an ID and selfie on intake or asks to see the ID on video.
The clinician roster, kept current by you. Both lightweight integration guides end on the same instruction: "Partners should use Clinician Profiles to pull the most accurate licensing information from SteadyMD at minimum, monthly." The licences on your site go stale on your schedule.
The attribution. The SSO guide says "SteadyMD can track which UTM source, medium, and campaign patients come from" for white label and SSO patients. That is the feed your ad attribution runs on.
Whose medical practice is it?
We could not find out from the public pages. The Terms of Use, last updated October 2023, say the website is "owned and operated by SteadyMD, Inc." and that "Use of the Services does not create a physician/patient or provider/patient relationship with SteadyMD." They point patients to "the SteadyMD New Patient Agreements" presented at sign-up, which are not published, and the SSO guide lists "NPA" as the first step of the white label. So the professional entity your patients are told they are seeing, and whose name goes on the consent and the chart, is in a document your patients will see at sign-up. Ask for it before then. That is the corporate practice of medicine question, and your website has to tell the truth about it.
Does their compliance cover you?
LegitScript. None of the SteadyMD pages we read displays a LegitScript seal, an NCQA badge or any other certification mark, in text or as an image. We looked for one because a footer badge is a claim too. There is nothing to transfer, and certification would not transfer anyway: it is granted to an applicant for the websites it controls, so your storefront is its own application.
Compounding. The word does not appear on any SteadyMD page or doc we read. The weight management page says its clinicians can "order and evaluate lab tests, prescribe GLP-1 medications" and goes no further. Compounded drugs are not FDA approved, and whether a compounded product is inside your program's protocol is a question for the clinical lead and the contract, not something the website answers. Our 503A and 503B explainer covers what your own page can and cannot say about it.
State coverage. "All 50 states" is a workforce claim. The consult API returns a 400 error if you create a consult "in US state where the program is not supported". Your program's map is a configuration, not the homepage.
Where do their own pages disagree?
How many clinicians. The homepage says "Hundreds". The 2023 Amazon Clinic release says "thousands of board-certified clinicians". DocGo's October 2025 press release says "over 600 clinicians". DocGo's December 2025 blog says "over 500 clinicians". Four figures across four of their own documents.
What the shallow integration is called. The Telehealth APIs page calls it "Limited API Integration: Quick Start". The documentation has a Limited Integrations page and a Light Integration page with near identical steps, and the pediatric guide refers to "Limited Integration" and "Complete Integration". Three labels for the same two paths.
Who you are contracting with. The Terms of Use predate the acquisition and still describe SteadyMD, Inc. under Missouri law, with references to "the SteadyMD Privacy Policy". The privacy link on the same site now redirects to DocGo's policy, and every footer reads "SteadyMD, a DocGo company, is governed by the DocGo Privacy Policy." The old patient app at the SteadyMD domain redirects to a Lemonaid Health login, left over from the 2022 shift "from servicing consumers directly to enabling healthcare organizations". None of this is wrong. The version that counts is the one in your contract.
What to settle before you sign
- Whether you are building the patient interface, using the white label behind SSO, or mixing SteadyMD's video and scheduling elements into your own screens. Each is a different build.
- The consult types, business hours, SLAs and booking buffer for your program, in writing, since your code cannot change them.
- The name of the professional entity your patients will be told they are seeing, and where the New Patient Agreements live.
- Which pharmacy your partner relationship routes to, how the patient's right to choose another is presented in your intake, and whether anything compounded is in protocol.
- Whose Stripe account takes the charge, who sets the per visit price, and who handles the refund, the late cancellation fee and the FSA receipt when a patient asks.
SteadyMD is the platform on this track that leaves you the most to build and the most to own. For a brand with a product team and a point of view about its patient experience, that is the right trade. For one that wanted a clinic in a box, it is the wrong one, and the modalities guide says so in its first bullet.
If you want that build mapped against your program before you commit, that is what a telehealth program fit review is for, and it is the same work behind our telehealth and GLP-1 website builds.
Common questions
Does SteadyMD provide the clinicians, or do I bring my own?
SteadyMD provides them. Its homepage describes hundreds of active board-certified doctors and nurse practitioners in all 50 states and says it handles their recruiting, hiring and training, and its clinical operations page adds scheduling, a 24/7 supervising physician for nurse practitioners and malpractice insurance for all of its clinicians. The documentation routes each visit to a clinician who is trained and assigned on your program, licensed in the state where the patient is located and available at the time needed. The partner's job is to keep its own records current: the integration guides say partners should pull clinician profiles from SteadyMD at minimum monthly for the most accurate licensing information. SteadyMD has been owned by DocGo since October 20, 2025, when DocGo's 8-K reported the acquisition for up to 25 million dollars.
Do I have to build the patient-facing experience myself?
For messaging, yes. SteadyMD's modalities page says secured messaging requires partners to design and build the patient interface to interact with its APIs. For video and scheduling you have a choice: use SteadyMD's video element and scheduling element, or use your own video platform and retrieve availability through the API. SteadyMD also offers a white label patient experience reached through single sign-on, and can send SMS and email notifications to patients directly if you use them. The intake questionnaire is yours to build as well, and it has to carry whatever the clinical protocol agreed with SteadyMD requires, including hard stops for conditions that cannot be treated virtually.
Does SteadyMD handle pharmacy fulfilment for a GLP-1 program?
No. SteadyMD's clinicians prescribe, and the prescription goes to a pharmacy the patient chose. The preferred pharmacy guide says partners may have a partnership pharmacy, however the patient must be able to opt for their pharmacy of choice, and that choice is collected during intake and sent on the episode of care. Electronic scripts reach a partnered pharmacy over the Surescripts network, and the guide says the pharmacy has to be set up in Surescripts' staging environment before anything can be tested end to end. Nothing on SteadyMD's public pages or in its documentation mentions compounded drugs; the weight management page says its clinicians prescribe GLP-1 medications and stops there. Compounded drugs are not FDA approved, and whether a compounded product is in scope for your program is a question for the contract, not the website.
Who takes the payment and handles refunds on a SteadyMD program?
On an API integration, you do, in your own checkout. On SteadyMD's white label, its Stripe guide says the white label can plug into a partner's Stripe account, that SteadyMD configures what price the patient pays per program visit type, and that operational processes are required to manage refunds when appropriate as determined by Customer Support, plus receipts for FSA and HSA reimbursement if automatic receipts are not enabled. The scheduling guide adds that visits rescheduled or cancelled within 24 hours of the appointment time will generally incur fees, and the SSO guide says a patient outside the agreed age range is automatically rejected and refunded. The money moves through your account; the policies that trigger a charge or a refund are set between you and SteadyMD.
Can I use SteadyMD with my own EMR?
Yes, and SteadyMD gives it two names. The Telehealth APIs page calls it Limited API Integration: your EMR hosts patient data and clinician workflow, you create visits in SteadyMD's system that link to your EMR, and SteadyMD's clinicians pick them up but the work happens in your system. The documentation calls the same path Limited Integrations on one page and Light Integration on another. It requires you to set up single sign-on for SteadyMD clinicians into your EMR, to deep link each consult to the visit in your EMR, to flag pediatric patients, and to tell SteadyMD when the visit is completed or cancelled. The Digital Clinic page lists AthenaHealth, EPIC, Cerner and Dr. Chrono as supported external EMRs.
Is SteadyMD LegitScript certified, and does that cover my storefront?
We found no claim either way. None of the SteadyMD pages we read on October 31, 2026 displays a LegitScript seal, an NCQA badge or any other certification mark, in text or as an image, and LegitScript's public lookup sits behind a CAPTCHA that we do not bypass. It would not transfer in any case. LegitScript certification is granted to an applicant for the websites it controls, so a brand's storefront is its own application, with its own disclosures and its own review. SteadyMD's documentation does put one compliance task on you: the identity verification guide says external verification, where the partner attests it has verified the patient, requires agreement between legal teams before it can be used. Nothing here is legal advice.
Sources
- SteadyMD homepage, with the 50 states claim, the hundreds of clinicians figure, the 200k+ visits a month figure and the DocGo footer line checked 2026-11-04
- SteadyMD, About Us, on the 2016 founding, the two launch states and 50 state coverage by 2018 checked 2026-11-04
- SteadyMD, Clinical Operations, on protocols, NP supervision, patient operational support and malpractice coverage checked 2026-11-04
- SteadyMD, Telehealth APIs, with the Limited and Complete API Integration descriptions and the Request API Documentation form checked 2026-11-04
- SteadyMD, Digital Clinic, on clinician routing and supported external EMRs checked 2026-11-04
- SteadyMD, Weight Management Companies, with the GLP-1 prescribing line checked 2026-11-04
- SteadyMD, AI-Powered Care, with the clinician in the loop flow and the Quest line checked 2026-11-04
- SteadyMD Terms of Use, last updated October 2023, on SteadyMD, Inc., Missouri law and the New Patient Agreements checked 2026-11-04
- SteadyMD blog, March 1, 2022, on the shift from serving consumers directly and the Lemonaid Primary Care Complete offering checked 2026-11-04
- SteadyMD blog, August 29, 2023, on Amazon Clinic, with the thousands of clinicians figure checked 2026-11-04
- SteadyMD documentation index, llms.txt checked 2026-11-04
- SteadyMD docs, Introduction, describing the platform as a workflow system checked 2026-11-04
- SteadyMD docs, Key Terms, on consult types, patient location and the EMR and consult endpoints checked 2026-11-04
- SteadyMD docs, Modalities, on messaging, phone and the two video options checked 2026-11-04
- SteadyMD docs, Limited Integrations checked 2026-11-04
- SteadyMD docs, Light Integration checked 2026-11-04
- SteadyMD docs, Direct to Patient Notifications, SMS and Email checked 2026-11-04
- SteadyMD docs, Intake Questionnaires checked 2026-11-04
- SteadyMD docs, Urgent Care, on the clinical intake questionnaire and hard stops checked 2026-11-04
- SteadyMD docs, Preferred Pharmacy, on the patient's pharmacy of choice and Surescripts checked 2026-11-04
- SteadyMD docs, Episode of Care, on treatment plans and prescription effective dates checked 2026-11-04
- SteadyMD docs, ID Verification, on external and internal verification checked 2026-11-04
- SteadyMD docs, Pediatric Requirements checked 2026-11-04
- SteadyMD docs, Scheduled Video, on the 15 day window, business hours, fees and missed visits checked 2026-11-04
- SteadyMD docs, SSO, on the white label, refunds for ineligible patients and UTM tracking checked 2026-11-04
- SteadyMD docs, Stripe Account Integration checked 2026-11-04
- SteadyMD docs, Labs, on who decides which tests and laboratories are available checked 2026-11-04
- SteadyMD docs, Consult Statuses, including rejected and referred out checked 2026-11-04
- SteadyMD docs, Consult Status Reasons checked 2026-11-04
- SteadyMD docs, Visit Status Updates / SNS Topics, on platform events sent to partners over AWS SNS checked 2026-11-04
- SteadyMD API reference, Create Consult, with the 400 error for a consult in a US state the program does not support checked 2026-11-04
- DocGo, Form 8-K filed October 20, 2025, Item 1.01, on the acquisition of SteadyMD, Inc. and the purchase price checked 2026-11-04
- DocGo, press release dated October 20, 2025, Exhibit 99.1, with the over 600 clinicians and 3 million patients figures checked 2026-11-04
- DocGo blog, December 10, 2025, with the over 500 clinicians figure checked 2026-11-04
Want this costed for your build?
Tell us what you already have and what is not working, and we will come back with the shape of the work and what drives the number.