BEKHealth
BEKhealth is a clinical research technology company whose BEKplatform applies a BERT-based deep-learning model to structured and unstructured electronic health record data — physician notes, pathology reports, clinical endpoints — to power trial feasibility, patient matching and research-grade real-world data for sponsors, CROs and research site networks. The company markets 25+ proprietary EHR adapters reaching roughly 80% of the EHR market (Epic, Cerner, athenahealth, NextGen, eClinicalWorks, Veradigm, Greenway, ModMed, DrChrono, Elation, AdvancedMD, Flatiron, OpenEMR and others), a longitudinal patient graph mapped to an ontology of more than 24 million clinical terms, and the BEKnetwork of 200+ research sites covering 30M+ patient records. Delivery is enterprise SaaS — sold direct and through AWS Marketplace, and embedded in partner platforms such as CRIO eSource/CTMS. BEKhealth operates a documentation portal at docs.bekhealth.com and an Auth0 OpenID Connect issuer at auth.bekhealth.com, but publishes no public developer portal, API reference or machine-readable specification; the documented route to the platform is a demo request and a contracted onboarding with BAAs and DUAs.
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.
API Evangelist profiles BEKHealth the way a machine reads it — 3 machine-readable artifacts, 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 — BEKHealth scores 26.9/100 (emerging), with a separate agent-readiness read of 9/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.
Why this profile is thin
BEKhealth runs a real documentation portal at docs.bekhealth.com, but every path on it — the root, /openapi.json, /llms.txt, even /.well-known/agent-card.json — returns a 302 into the company's Auth0 tenant at auth.bekhealth.com, so the contract is readable only by an existing customer with a signed BAA/DUA; nothing on the public marketing site names an API at all.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is BEKHealth's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://docs.bekhealth.com/→ HTTP 302https://docs.bekhealth.com/openapi.json→ HTTP 302https://api.bekhealth.com/openapi.json→ HTTP 404https://www.bekhealth.com/.well-known/agent-card.json→ HTTP 404https://www.bekhealth.com/llms.txt→ HTTP 200https://auth.bekhealth.com/.well-known/openid-configuration→ HTTP 200
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
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from BEKHealth'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/bekhealth/"
title="BEKHealth on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bekhealth.svg"
alt="BEKHealth Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/bekhealth/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bekhealth/"
title="BEKHealth on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bekhealth/card.svg"
alt="BEKHealth Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile BEKHealth
Each block below is one kind of artifact we hold for BEKHealth. 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 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for BEKHealth — 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 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bekhealth · machine-readable index on apis.io
This is an independent, third-party profile of BEKHealth, 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.