LetsGetChecked
LetsGetChecked (operating as LetsGetChecked powered by FuzeHealth) is an Irish-American virtual care company that runs an end-to-end diagnostics and care platform: it manufactures at-home sample-collection kits, operates its own CLIA-accredited laboratories in the United States and Europe, and layers telehealth consultations, clinical review and affiliate-pharmacy prescription delivery on top of the results. Its Halo platform is a purpose-built EMR that exposes B2B REST APIs — the Orders API (v1 and v2), the Results API and the Outreach API — plus event-driven webhook notifications, so employers, health plans, providers, public-sector programs and life-sciences partners can order pre-activated test kits, track kit fulfillment, and retrieve laboratory results in JSON, HL7 or PDF form inside their own systems.
LetsGetChecked is listed with 5 APIs on the APIs.io network. Tagged areas include Company, Health, Healthcare, Diagnostics, and Laboratory.
The LetsGetChecked catalog on APIs.io includes 1 event-driven AsyncAPI specification.
LetsGetChecked’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 27 more developer resources.
Kin Score
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 |
|---|---|---|---|---|
| IVD, Diagnostics and Surgical Devices (FDA / EU regulated device makers) | regulated | 19.2 (thin) | - | - |
| US NPI Health Provider Registry (CMS NPPES) | regulated | 19.2 (thin) | - | - |
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.
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
LetsGetChecked Orders API (Version 1)
Version 1 of the LetsGetChecked Orders API. Create a pre-activated test-kit order against a client-supplied order identifier (PUT is documented as idempotent), query order statu...
LetsGetChecked Orders API (Version 2)
Version 2 of the LetsGetChecked Orders API, documented September 2023. Adds an order-item model with per-item identifiers and statuses, a PATCH endpoint for cancelling an order ...
LetsGetChecked Results API
Read laboratory results for test kits processed by the LetsGetChecked lab. Retrieve a full result set for a barcode (with optional alpha code), fetch just the result status, or ...
LetsGetChecked Outreach API
Retrieve and download the results letters LetsGetChecked generates for patients and for a patient's Primary Care Provider. List outreach notifications for a client program with ...
LetsGetChecked API Notifications (Webhooks)
Event-driven webhook notifications delivered by POST to client-supplied endpoints whenever an order, result or outreach resource changes. Payloads carry a resource identifier, a...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll for all 7
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Source (apis.yml)
LetsGetChecked API — frequently asked questions
Does LetsGetChecked have an API?
Yes. APIs.io lists 5 APIs from LetsGetChecked, including LetsGetChecked Orders API (Version 1), LetsGetChecked Orders API (Version 2) and LetsGetChecked Results API, and 2 more.
How do I authenticate with the LetsGetChecked API?
LetsGetChecked documents its authentication (oauth2/http · 3 schemes). The details are profiled on APIs.io as Letsgetchecked Authentication.
Is the LetsGetChecked API ready for AI agents?
LetsGetChecked has a Kin Score of 48.1 out of 100 (developing) and an Agent Readiness score of 34.2 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.