BodyTrace

BodyTrace makes cellular-connected remote patient monitoring (RPM) devices - blood pressure monitors, body-weight scales, and pulse oximeters - that transmit readings directly over the cellular network with no phone, app, Wi-Fi, or Bluetooth pairing required. Each device encrypts measurements end-to-end and sends them to the BodyTrace platform, which exposes the data to healthcare organizations, EHRs, and RPM programs over a simple HTTP API using HTTP Basic authentication. Consumers can pull device readings (data values) on a polling loop or receive them pushed to a configured HTTP endpoint. BodyTrace sells to organizations, not individuals; API and device provisioning are arranged through BodyTrace sales.

BodyTrace publishes 5 API contracts indexed on the APIs.io network, including Alerts API, Data Messages API, Devices API, and 2 more. Tagged areas include Remote Patient Monitoring, RPM, Cellular, Medical Devices, and Digital Health.

The BodyTrace catalog on APIs.io includes 1 Spectral governance ruleset.

BodyTrace’s developer surface includes authentication, documentation, and 7 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.1/100 thin ▬ flat Agent 21/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

1 published contract

Remote Patient Monitoring RPM Cellular Medical Devices Digital Health Blood Pressure Connected Devices IoT

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 28.1/100 · thin

Contract Quality 9.4 / 19

Developer Ergonomics 3.4 / 15

Access Clarity 0.6 / 15

Operational Transparency 0.7 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 0.7 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 21/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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 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

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

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/bodytrace/"><img src="https://apis.io/badge/bodytrace/card.svg" alt="BodyTrace 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 Ask about this →
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) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

9 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 4.3 — up to +19.1 composite points Ask about this →
Developer Ergonomics scores 22.6 — up to +15.5 composite points Ask about this →
Contract Quality scores 50.2 — up to +12.5 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/bodytrace/apis.yml: open an issue on github.com/api-evangelist/bodytrace 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Canada Medical Device Licensing (Health Canada MDALL licence holders, incl. SaMD)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

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

BodyTrace Alerts API

Modeled threshold and connectivity alerts.

BodyTrace Data Messages API

Modeled surface for raw per-transmission device messages.

BodyTrace Devices API

Modeled device listing and status keyed by IMEI.

BodyTrace Observations API

Confirmed pull surface for device readings (data values).

BodyTrace Provisioning API

Modeled device enrollment and delivery configuration.

Open Collections 6

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

BodyTrace RPM Data Alerts API

OPEN COLLECTION

BodyTrace RPM Data Alerts Data Messages API

OPEN COLLECTION

BodyTrace RPM Data Alerts Devices API

OPEN COLLECTION

BodyTrace RPM Data Alerts Observations API

OPEN COLLECTION

BodyTrace RPM Data Alerts Provisioning API

OPEN COLLECTION

BodyTrace RPM Data API

OPEN COLLECTION

BodyTrace API pricing

Not yet checked against BodyTrace's own pricing page. Compiled by API Evangelist on 2026-07-05 from www.bodytrace.com; confirm before you rely on a figure.

Plan	Price
Per-Device Subscription subscription	—
Enterprise / Volume enterprise	—

Plan details, limits and sources →

Rate limits

Data Values Pull Requests: not published requests
Device Transmission Frequency: a few readings + heartbeats per day messages
Push Delivery: event-driven messages

Compiled by API Evangelist, not yet checked against BodyTrace's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

BodyTrace Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

BodyTrace Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

BodyTrace Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

BodyTrace API Rules

69 rules · 67 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

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

BodyTrace Authentication

http · 1 scheme

SECURITY

BodyTrace Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

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

BodyTrace Agentic Access

6 operations · 1 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

LinkedIn

Website

Website

Source (apis.yml)

aid: bodytrace
url: https://raw.githubusercontent.com/api-evangelist/bodytrace/refs/heads/main/apis.yml
name: BodyTrace
kind: company
description: BodyTrace makes cellular-connected remote patient monitoring (RPM) devices - blood pressure monitors, body-weight
  scales, and pulse oximeters - that transmit readings directly over the cellular network with no phone, app, Wi-Fi, or Bluetooth
  pairing required. Each device encrypts measurements end-to-end and sends them to the BodyTrace platform, which exposes the
  data to healthcare organizations, EHRs, and RPM programs over a simple HTTP API using HTTP Basic authentication. Consumers
  can pull device readings (data values) on a polling loop or receive them pushed to a configured HTTP endpoint. BodyTrace
  sells to organizations, not individuals; API and device provisioning are arranged through BodyTrace sales.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/bodytrace.png
tags:
- Remote Patient Monitoring
- RPM
- Cellular
- Medical Devices
- Digital Health
- Blood Pressure
- Connected Devices
- IoT
created: '2026-07-05'
modified: '2026-07-05'
specificationVersion: '0.23'
apis:
- aid: bodytrace:bodytrace-alerts-api
  name: BodyTrace Alerts API
  description: Modeled threshold and connectivity alerts.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Alerts
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-alerts-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-data-messages-api
  name: BodyTrace Data Messages API
  description: Modeled surface for raw per-transmission device messages.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Data Messages
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-data-messages-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-devices-api
  name: BodyTrace Devices API
  description: Modeled device listing and status keyed by IMEI.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Devices
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-devices-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-observations-api
  name: BodyTrace Observations API
  description: Confirmed pull surface for device readings (data values).
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Observations
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-observations-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
- aid: bodytrace:bodytrace-provisioning-api
  name: BodyTrace Provisioning API
  description: Modeled device enrollment and delivery configuration.
  humanURL: https://www.bodytrace.com/medical/
  baseURL: https://us.data.bodytrace.com/1
  tags:
  - Provisioning
  properties:
  - type: OpenAPI
    url: openapi/bodytrace-provisioning-api-openapi.yml
  - type: Documentation
    url: https://www.bodytrace.com/medical/
  - type: PostmanCollection
    url: collections/bodytrace.postman_collection.json
  - type: OpenCollection
    url: collections/bodytrace.opencollection.json
common:
- type: AgenticAccess
  url: agentic-access/bodytrace-agentic-access.yml
- type: DomainSecurity
  url: security/bodytrace-domain-security.yml
- type: Authentication
  url: authentication/bodytrace-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/bodytrace
- type: Website
  url: https://www.bodytrace.com
- type: Documentation
  url: https://www.bodytrace.com/medical/
- type: Plans
  url: plans/bodytrace-plans-pricing.yml
- type: RateLimits
  url: rate-limits/bodytrace-rate-limits.yml
- type: FinOps
  url: finops/bodytrace-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

BodyTrace API — frequently asked questions

Does BodyTrace have an API?

Yes. APIs.io lists 5 APIs from BodyTrace, including BodyTrace Alerts API, BodyTrace Data Messages API and BodyTrace Devices API, and 2 more.

Is there an OpenAPI specification for the BodyTrace API?

Yes. APIs.io indexes 5 OpenAPI specifications for BodyTrace, each linked for download from this page.

How do I authenticate with the BodyTrace API?

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

How much does the BodyTrace API cost?

APIs.io lists 2 pricing plans for BodyTrace, with each plan's price, limits and inclusions under Pricing on this page.

Is the BodyTrace API ready for AI agents?

BodyTrace has a Kin Score of 28.1 out of 100 (thin) and an Agent Readiness score of 20.7 (agent-aware), scored by API Evangelist on 2026-11-13.

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/bodytrace"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.