Curai

Curai Health is a virtual-first primary care company offering 24/7 text-based telemedicine to patients across all 50 U.S. states, connecting them with board-certified clinicians for urgent care, chronic disease management, wellness, and preventive screenings, with orders for labs and prescriptions and referrals to specialists. For organizations, health systems, TPAs, and benefits administrators, Curai exposes a Partner API and an embeddable Web SDK (curai-js) that let partners register patients and drop the Curai patient experience into their own web and mobile apps, plus integration via standards-based APIs, Health Information Exchanges (HIE), and webhooks. The Partner API is a small, key-authenticated surface used to onboard patients and obtain session access tokens for the embedded experience.

Curai publishes 1 API contract indexed on the APIs.io network: Partner API. Tagged areas include Company, Health, Healthcare, Telehealth, and Primary Care.

Curai’s developer surface includes engineering blog, documentation, getting-started guide, authentication, sandbox, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.3/100 thin ▬ flat Agent 26/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 published contract 1 Agent Skills

Company Health Healthcare Telehealth Primary Care Digital Health Patient Engagement Partner API SDK

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Patient Access Management

BC-2800

Partner

POST /register-patient

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 35.3/100 · thin

Contract Quality 9.4 / 21

Developer Ergonomics 11.6 / 17

Access Clarity 1.8 / 17

Operational Transparency 0.6 / 11

Contract Governance 0.5 / 10

Discoverability 5.6 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

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.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/curai/"><img src="https://apis.io/badge/curai/card.svg" alt="Curai on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 10.5 — up to +17.9 composite points
Contract Quality scores 44.1 — up to +14.0 composite points
Operational Transparency scores 5.3 — up to +12.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/curai/apis.yml: open an issue on github.com/api-evangelist/curai to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Curai Partner API

The Partner API from Curai — 2 operation(s) for partner.

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Curai Partner API

OPEN COLLECTION

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Register a Curai patient and launch the embedded experience

AGENT SKILL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Curai Partner Overlay

3 actions · update · curai-partner-openapi.json

DERIVED

Security Posture 2

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

Curai Authentication

apiKey · 1 scheme

SECURITY

Curai Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Curai Agentic Access

2 operations · 2 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

LLMsTxt

AgentSkill

AgenticAccess

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Components

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Commercial 1

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: curai
name: Curai
description: Curai Health is a virtual-first primary care company offering 24/7 text-based telemedicine to patients across
  all 50 U.S. states, connecting them with board-certified clinicians for urgent care, chronic disease management, wellness,
  and preventive screenings, with orders for labs and prescriptions and referrals to specialists. For organizations, health
  systems, TPAs, and benefits administrators, Curai exposes a Partner API and an embeddable Web SDK (curai-js) that let partners
  register patients and drop the Curai patient experience into their own web and mobile apps, plus integration via standards-based
  APIs, Health Information Exchanges (HIE), and webhooks. The Partner API is a small, key-authenticated surface used to onboard
  patients and obtain session access tokens for the embedded experience.
url: https://raw.githubusercontent.com/api-evangelist/curai/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://cdn.prod.website-files.com/619acca858666ac6759d6e31/61d79c66ae46600b755a13be_logo_webclip.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- general-catalyst
- khosla-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Health
- Healthcare
- Telehealth
- Primary Care
- Digital Health
- Patient Engagement
- Partner API
- SDK
tags_raw:
- Company
- Health
- Healthcare
- Telemedicine
- Telehealth
- Primary Care
- Digital Health
- Patient Engagement
- Partner API
- SDK
apis:
- aid: curai:curai-partner-api
  name: Curai Partner API
  description: The Partner API from Curai — 2 operation(s) for partner.
  humanURL: https://gateway.curaihealth.com/partner/docs
  baseURL: https://gateway.curaihealth.com/partner
  tags:
  - Partners
  tags_raw:
  - Partner
  properties:
  - type: OpenAPI
    url: openapi/curai-partner-api-openapi.yml
  - type: APIReference
    url: https://gateway.curaihealth.com/partner/docs
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.curaihealth.com/blogs
  type: Blog
- type: CapabilityMap
  url: capabilities/curai-capability-edges.yml
  name: Curai Business Capability Map
- type: Overlay
  url: overlays/curai-partner-overlay.yaml
- type: Website
  url: https://www.curaihealth.com/
- type: DeveloperPortal
  url: https://gateway.curaihealth.com/partner/docs
- type: Documentation
  url: https://www.curaihealth.com/sdk-quickstart-guide
- type: GettingStarted
  url: https://www.curaihealth.com/sdk-quickstart-guide
- type: GitHubOrganization
  url: https://github.com/curai
- type: TermsOfService
  url: https://www.curaihealth.com/terms-of-use
- type: Packages
  url: packages/curai-packages.yml
- type: SDKs
  url: packages/curai-packages.yml
- type: Components
  url: components/curai-components.yml
- type: WellKnown
  url: well-known/curai-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/curai-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/curai-llms.txt
- type: Conformance
  url: conformance/curai-conformance.yml
- type: ErrorCatalog
  url: errors/curai-problem-types.yml
- type: Lifecycle
  url: lifecycle/curai-lifecycle.yml
- type: Authentication
  url: authentication/curai-authentication.yml
- type: DomainSecurity
  url: security/curai-domain-security.yml
- type: Sandbox
  url: sandbox/curai-sandbox.yml
- type: Conventions
  url: conventions/curai-conventions.yml
- type: DataModel
  url: data-model/curai-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/curai-agentic-access.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Curai API — frequently asked questions

Does Curai have an API?

Yes. APIs.io lists 1 API from Curai, including Curai Partner API.

Is there an OpenAPI specification for the Curai API?

Yes. APIs.io indexes 1 OpenAPI specification for Curai, each linked for download from this page.

How do I authenticate with the Curai API?

Curai uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Curai Authentication.

Is the Curai API ready for AI agents?

Curai has a Kin Score of 35.3 out of 100 (thin) and an Agent Readiness score of 25.5 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/curai"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/curai/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/curai/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.