Rook vs Spike: Which Health-Data API Fits Your Build?

Same category, closer than they were#

Neither of these is usually the first aggregator a team shortlists; that is more often Terra or Junction. When Rook and Spike end up head-to-head, the old framing was a mobile-first wearable aggregator against an everything-source one. Their current pages, read on October 17, 2026, blur that line: ROOK now sells medical-device, lab-report and EHR/EMR products alongside its wearable API, and both publish prices. An earlier version of this page said Rook did not reach labs, EMRs or medical IoT, that neither vendor's pricing could be verified, and that Spike's own pages disagreed on its device count. Those claims are corrected below.

ROOK describes itself as "the health data aggregation and intelligence platform for digital health, wellness and insurance products". Its homepage pitch is "Wearables, medical devices, EHR/EMR and labs", priced by plan and active users. Spike pitches "360° Health Data for AI": wearables and IoT sensors, lab report data, food-photo nutrition and EMR access behind one API, with a dedicated implementation engineer from its entry plan.

Rook vs Spike at a glance#

Where Rook wins#

You can price it before the first call. ROOK's pricing page lists every self-serve ceiling: Core "$399 USD per month" for up to 750 active users, Core+ $999 for up to 5,000, Business $1,999 for up to 15,000, and add-ons with listed prices. Spike lists a starting price and a custom Enterprise plan. Past a ROOK plan's limit, "billing adjusts based on usage", which is the one number ROOK does not publish.

Device provenance on every reading. ROOK's Medical Device API delivers readings "with the device that recorded each one", so a remote-monitoring program can tell a cuff from a watch. Spike integrates medical IoT too; the device-metadata detail is what ROOK documents.

Phone stores without your own app. The ROOK App "lets end users connect supported sources without embedding the SDKs", for programs that have no mobile app of their own.

The honest trade-off. The standard contract is 12 months, several products are add-ons on Core, and four popular providers need your own developer accounts, which ROOK says "can take several weeks".

Where Spike wins#

A human on your implementation. "Every organization gets a dedicated implementation engineer from the sandbox level to help with setup and optimization." That is a checkable differentiator in a category where onboarding is normally the docs.

Food photos and LLM tooling in the box. Spike's Nutrition AI converts "any food image into complete nutritional data", and Spike MCP "connects wearables data, medical IoT devices, lab reports, and nutrition logs to your LLM of choice". ROOK lists neither.

EMR data today. Spike's homepage offers EMR and EHR connections now; ROOK's page says bringing EHR and EMR data into ROOK is coming soon.

The honest trade-off. Spike publishes less: no tier ceilings, no contract terms, and no word on provider credentials in the docs we read. Its integrations and blog pages carry a banner announcing that Raintree Systems acquires Spike Technologies, with no further detail on its own pages.

What we could not verify#

• For Rook: the usage rate past a plan's ceiling, and whether webhooks carry a signature.
• For Spike: how the bill grows past the Sandbox starting price, whether any provider needs your own developer account, and what the acquisition changes.
• For both: coverage counts are each vendor's marketing; check your users' providers on the live lists.

How to choose#

• A budget you need to model now, at a few thousand users → Rook. Core+ at $999 a month covers up to 5,000 active users.
• Remote-monitoring readings where the device matters → Rook's Medical Device API.
• Implementation help, food logging from photos, or an LLM-facing MCP layer → Spike.
• EMR and EHR data flowing into your product today → Spike, after confirming the integration you need is live.
• You have not compared the category leaders → do that first: Terra vs Rook and Terra vs Spike take those pairs, and Terra vs Vital (Junction) covers lab ordering.

Honest close#

Neither vendor saves you from the core aggregator trade: you pay to remove per-provider integration work, and you still own your infrastructure, token handling and health-data compliance. What separates them now is visibility and support: Rook publishes a price sheet you can model and a broader set of clinical-adjacent APIs than it used to, while Spike pairs a wide data reach with an engineer on your build and a price you learn on a call. Re-check both live pages before you commit; for the wider field, see the health-data aggregator APIs overview.