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
DexCare website screenshot

DexCare

DexCare is a healthcare navigation and care-orchestration platform, launched from within Providence Health, that connects patients to available care across fragmented health systems while helping providers fill capacity and reduce wait times. Its products span Search & Schedule, Virtual On Demand, Provider Data Management (PDM+), Optimize AI, and Acquire. DexCare publishes six OpenAPI definitions on its own developer portal covering 27 operations across the Visit Service, Visit Booking, Care Options, Slots Availability, Omni Search and Provider Data Management services, alongside prose references for the Patient and Reporting APIs and native iOS, Android and JavaScript SDKs. There is no shared base URL: every health system is provisioned its own UAT and production hosts, and the published specifications use templated or per-tenant servers. Public directory, availability and search endpoints are open, while PHI/PII endpoints require an OAuth 2.0-issued JWT bearer token and server-to-server services require a DexCare-issued x-api-key. DexCare operates as a HIPAA business associate. This profile was enriched from DexCare's public developer surface as part of the API Evangelist network (originally surfaced as an ICONIQ Capital portfolio lead).

agent aware

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles DexCare the way a machine reads it — 24 machine-readable artifacts across 12 APIs, 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 — DexCare scores 50.2/100 (developing), with a separate agent-readiness read of 27/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
DexCare Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from DexCare'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/dexcare/"
   title="DexCare on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/dexcare.svg"
       alt="DexCare 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 DexCare

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

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.

DexCare REST API

RESTful service for accessing business information and performing actions against DexCare-managed healthcare environments. The umbrella reference covering the Patient and Report...

DexCare Assignmentqualifiers API

The assignmentqualifiers API from DexCare — 1 operation(s) for assignmentqualifiers.

DexCare External API

The external API from DexCare — 2 operation(s) for external.

DexCare Modalities API

The modalities API from DexCare — 1 operation(s) for modalities.

DexCare Omni Analytics API

The OmniAnalytics API from DexCare — 1 operation(s) for omnianalytics.

DexCare Omni Data API

The OmniData API from DexCare — 1 operation(s) for omnidata.

DexCare Omni Search API

The OmniSearch API from DexCare — 1 operation(s) for omnisearch.

DexCare Omni Search Analytics API

The OmniSearchAnalytics API from DexCare — 1 operation(s) for omnisearchanalytics.

DexCare Omni Search Facets API

The OmniSearchFacets API from DexCare — 1 operation(s) for omnisearchfacets.

DexCare Omni Sitemap API

The OmniSitemap API from DexCare — 1 operation(s) for omnisitemap.

DexCare Omni Slugs API

The OmniSlugs API from DexCare — 1 operation(s) for omnislugs.

DexCare Omni Synonyms API

The OmniSynonyms API from DexCare — 1 operation(s) for omnisynonyms.

DexCare Pdm API

The Pdm API from DexCare — 2 operation(s) for pdm.

DexCare Providers API

The Providers API from DexCare — 1 operation(s) for providers.

DexCare Queued Guest Visit API

The queued-guest-visit API from DexCare — 1 operation(s) for queued-guest-visit.

DexCare Slots API

The Slots API from DexCare — 3 operation(s) for slots.

DexCare Tokbox API

The tokbox API from DexCare — 1 operation(s) for tokbox.

DexCare Virtual Visits API

The virtual-visits API from DexCare — 1 operation(s) for virtual-visits.

DexCare Visits API

The visits API from DexCare — 3 operation(s) for visits.

DexCare Waittimes API

The waittimes API from DexCare — 2 operation(s) for waittimes.

Scroll within the panel for all 20 ·

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Dexcare Plans Pricing

0 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Dexcare Rate Limits

0 limits

RATE LIMITS

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.

Dexcare Authentication

oauth2/http/apiKey/none · 7 schemes

SECURITY

Dexcare Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for DexCare — 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 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

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/dexcare · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of DexCare, 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.