Leal Health (fka TrialJectory)
Leal Health (formerly TrialJectory) is an AI-powered, patient-first decision-support platform that matches cancer patients to advanced treatments and clinical trials. Its patented natural language processing engine reads inclusion/exclusion eligibility criteria and connects to ClinicalTrials.gov so patients, caregivers, and oncologists can self-screen against every recruiting oncology trial in roughly two minutes. For pharma, biotech, and CRO customers, the Patient Match Optimizer SaaS dashboard delivers de-identified, aggregate real-time datasets on patient barriers, motivators, geography, and competitive landscape to shorten enrollment timelines and improve minority representation in trials. The company was founded as TrialJectory by Tzvia Bader (CEO), Avital Gaziel, Guy Gildor, and Noam Geva, later rebranded to Leal Health, and lists a Clifton, New Jersey mailing address. Leal Health operates no public developer program: a live platform API host exists at api.leal.health, but every path behind the root returns HTTP 401 and no OpenAPI, SDK, or developer documentation is published.
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 Leal Health (fka TrialJectory) the way a machine reads it — 2 machine-readable artifacts across 1 API, 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 — Leal Health (fka TrialJectory) scores 21.2/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Leal Health (fka TrialJectory)
Each block below is one kind of artifact we hold for Leal Health (fka TrialJectory). 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 1
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.
Leal Health Platform API
Private platform API host backing the Leal Health patient-matching web application and the Patient Match Optimizer dashboard. Verified live on 2026-07-19: the root path returns ...
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 Leal Health (fka TrialJectory) — 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 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/leal-health-fka-trialjectory · machine-readable index on apis.io