How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

human only

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.

Kin Score

API Evangelist profiles Boulder Care the way a machine reads it — 1 machine-readable artifact, 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 — Boulder Care scores 20.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.

No API surface

Why this profile is thin

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.

This is an honest zero, not a gap in our research. Boulder Care does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.

What we probed
  • https://www.boulder.care/developersHTTP 404
  • https://www.boulder.care/openapi.jsonHTTP 404
  • https://www.boulder.care/llms.txtHTTP 404
  • https://www.boulder.care/.well-known/security.txtHTTP 404
  • https://api.boulder.care/HTTP 400
  • https://api.boulder.care/healthHTTP 200

Checked 2026-08-08. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 20.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 0.7 / 13
Governance 1.5 / 12
Discoverability 6.9 / 10
Regulatory · Health 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
Boulder Care Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Boulder Care's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/boulder-care/"
   title="Boulder Care on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/boulder-care.svg"
       alt="Boulder Care Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Boulder Care

Each block below is one kind of artifact we hold for Boulder Care. 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.

Security Posture 1

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.

Boulder Care Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Boulder Care — 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.

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

← All providers · Data indexed from github.com/api-evangelist/boulder-care · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Boulder Care, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.