Boulder Care
Boulder Care is a Portland, Oregon telehealth provider founded in 2017 by Stephanie Strong that delivers evidence-based outpatient treatment for opioid and alcohol use disorder entirely through a mobile app. Participants connect to a collaborative care team — addiction medicine clinicians, peer recovery specialists and care coordinators — over secure video and messaging, and are prescribed medications for addiction treatment including buprenorphine/naloxone (Suboxone), naltrexone (Revia, Vivitrol) and acamprosate (Campral). The company focuses on Medicaid beneficiaries and other historically underserved populations, contracts with health plans, health systems, employers and correctional and jail-based referral partners, and has served more than 12,000 participants across states including Oregon, Washington, Colorado, North Carolina, New Mexico, Ohio and Michigan. Boulder Care raised a $35M Series C in 2024 led by Advance Venture Partners. It ships software only as an end-user patient product: there is no developer portal, no published API documentation, no SDK and no machine-readable specification anywhere on its public surface.
Boulder Care is profiled on the APIs.io network. Tagged areas include Company, Healthcare, Telehealth, Behavioral Health, and Addiction Treatment.
Boulder Care’s developer surface includes engineering blog, support, FAQ, signup flow, pricing, legal docs, and 16 more developer resources.
Kin Score
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 4
Properties that don't map to a standard resource type