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.

20.0/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
0 APIs
CompanyHealthcareTelehealthBehavioral HealthAddiction TreatmentSubstance Use DisorderDigital HealthMedicaidVirtual CareMobile Health

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 20.0/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 1.1 / 17
Commercial Clarity 7.6 / 17
Operational Transparency 0.6 / 11
Governance 1.3 / 10
Discoverability 5.8 / 9
Regulatory Posture 3.6 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
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
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/boulder-care: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Boulder Care Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

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

Source (apis.yml)

apis.yml Raw ↑
aid: boulder-care
name: Boulder Care
description: '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.'
image: https://cdn.prod.website-files.com/61a529f90d9568244b6f6716/621d5fdca5956ee9ec3de8c2_logo_primary_light.svg
url: https://raw.githubusercontent.com/api-evangelist/boulder-care/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-08'
modified: '2026-08-08'
tags:
- Company
- Healthcare
- Telehealth
- Behavioral Health
- Addiction Treatment
- Substance Use Disorder
- Digital Health
- Medicaid
- Virtual Care
- Mobile Health
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/boulder-care-domain-security.yml
- type: Conformance
  url: conformance/boulder-care-conformance.yml
- type: Website
  url: https://www.boulder.care/
- type: About
  url: https://www.boulder.care/about
- type: Blog
  url: https://www.boulder.care/blog
- type: Support
  url: https://www.boulder.care/support
- type: Contact
  url: https://www.boulder.care/contact
- type: FAQ
  url: https://www.boulder.care/faqs
- type: SignUp
  url: https://www.boulder.care/get-started
- type: Pricing
  url: https://www.boulder.care/self-pay
- type: TermsOfService
  url: https://www.boulder.care/legal/terms
- type: PrivacyPolicy
  url: https://www.boulder.care/legal/platform-privacy-policy
- type: Legal
  url: https://www.boulder.care/legal
- type: GitHubOrganization
  url: https://github.com/bouldercare
- type: Partners
  url: https://www.boulder.care/partners
- type: Careers
  url: https://www.boulder.care/careers
- type: KnowledgeBase
  url: https://www.boulder.care/services
- type: LinkedIn
  url: https://www.linkedin.com/company/boulder
- type: MobileApp
  url: https://apps.apple.com/us/app/boulder-care/id1437606990
- type: MobileApp
  url: https://play.google.com/store/apps/details?id=bouldercare.patient
- type: SecondaryMarket
  url: https://forgeglobal.com/boulder-care_stock/
- type: LLMsTxt
  url: llms/boulder-care-llms.txt
x-enrichment:
  date: '2026-08-08'
  status: minimal
  artifacts_added: 4
  pass: local-v1
x-coverage:
  state: none
  reason: no-developer-program
  detail: Boulder Care ships software only as an end-user patient app — its 156-URL sitemap contains no developer, docs, API
    or integration page, and the only machine API on any host is an undocumented Apollo GraphQL endpoint at the root of api.boulder.care
    that serves the mobile app and refuses introspection with INTROSPECTION_DISABLED.
  evidence:
  - url: https://www.boulder.care/developers
    status: 404
  - url: https://www.boulder.care/openapi.json
    status: 404
  - url: https://www.boulder.care/llms.txt
    status: 404
  - url: https://www.boulder.care/.well-known/security.txt
    status: 404
  - url: https://api.boulder.care/
    status: 400
  - url: https://api.boulder.care/health
    status: 200
  checked: '2026-08-08'