Biobeat
Biobeat Technologies is an Israeli med-tech company whose remote patient monitoring (RPM) health-AI platform pairs a disposable short-term chest-monitor and a reusable long-term wrist-monitor - both using a photoplethysmography (PPG) sensor - to continuously track up to 13 vital signs, including FDA-cleared cuffless blood pressure, pulse rate, respiratory rate, blood oxygen saturation, temperature, stroke volume, cardiac output, and one-lead ECG (chest-monitor). Readings stream to Biobeat's HIPAA- and GDPR-compliant, cloud-based patient management platform, where clinicians view real-time data, trends, and configurable alerts. Biobeat offers programmatic data access and EMR/EHR integration as a paid add-on for hospitals, health systems, and research partners; there is no publicly documented self-serve developer API.
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 Biobeat the way a machine reads it — 6 machine-readable artifacts across 4 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 — Biobeat scores 16.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.
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.
How we profile Biobeat
Each block below is one kind of artifact we hold for Biobeat. 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 4
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.
Biobeat Patients API
Modeled resource for enrolling and managing monitored patients on the Biobeat patient management platform - create, list, and update patient records, assign devices, and set per...
Biobeat Devices API
Modeled resource for provisioning and managing Biobeat wearable devices - the disposable chest-monitor and the reusable wrist-monitor - including registration, assignment to a p...
Biobeat Vital Signs Measurements API
Modeled resource for retrieving continuous vital-sign readings collected by Biobeat wearables - cuffless blood pressure, pulse rate, respiratory rate, blood oxygen saturation, t...
Biobeat Alerts API
Modeled resource for the alerts Biobeat raises when a patient's readings cross configured alarm limits or its health-AI flags early deterioration. Covers listing active alerts a...
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
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.
Resources
Every other property we hold for Biobeat — 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
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/biobeat · machine-readable index on apis.io