LEAF4Life
LEAF4Life Inc. is a privately held, clinical-stage biopharmaceutical company headquartered in Woburn, Massachusetts, founded in 2018 by Dr. Clet Niyikiza to develop transformative therapies for hypoxia — insufficient oxygen at the tissue and cellular level — which the company describes as implicated in the world's ten leading causes of death and more than 30 million deaths a year. Its lead asset, KizaVie™ (LEAF-4L6715), is a proprietary liposomal formulation of transcrocetin, a naturally occurring carotenoid from saffron and cape jasmine, designed to enhance oxygen diffusion in plasma and interstitium, restore microcirculatory oxygen delivery and repair hypoxia-driven microvascular and tissue damage, thereby improving the effectiveness of standard-of-care treatment. KizaVie™ is in three Phase 3 registrational studies in Europe — acute respiratory distress syndrome (ARDS), glioblastoma and sarcoma — and has received Compassionate Use Authorization in France for ARDS. The company also describes application to shock and trauma, cardiovascular disease, neurodegenerative disorders and aging. LEAF4Life runs no developer program and publishes no product API, developer portal, API reference, SDK or OpenAPI definition. The only machine-readable surface reachable without credentials is the WordPress REST content API behind leafforlife.com, catalogued here, and even that returns page identity and media only — every page body is empty over the API because the site is assembled by a page builder.
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 LEAF4Life the way a machine reads it — 13 machine-readable artifacts across 9 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 — LEAF4Life scores 24.2/100 (emerging), with a separate agent-readiness read of 22/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from LEAF4Life's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/leaf4life/"
title="LEAF4Life on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/leaf4life.svg"
alt="LEAF4Life Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/leaf4life/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/leaf4life/"
title="LEAF4Life on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/leaf4life/card.svg"
alt="LEAF4Life Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile LEAF4Life
Each block below is one kind of artifact we hold for LEAF4Life. 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 9
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.
LEAF4Life Content Pages API
The page collection behind leafforlife.com — 8 published pages covering the mission, the science, leadership, the advisory board and contact. Anonymously readable. Verified 2026...
LEAF4Life Media API
The WordPress media library behind leafforlife.com — 59 image attachments (43 PNG, 16 JPEG) spanning September 2020 to July 2026, including the brand marks, leadership headshots...
LEAF4Life Taxonomy API
Category and tag terms. Registered and anonymously reachable but effectively unused — one category (the WordPress default `uncategorized`) and 21 tags, every one with an item co...
LEAF4Life API Discovery
The self-describing routes of the deployment — registered post types, taxonomies and post statuses, plus the route index at the server root that publishes name, description, nam...
LEAF4Life Search API
Cross-type site search returning lightweight result stubs. Live and correct, but it returns zero for every site term tried — including with subtype=page — because WordPress inde...
LEAF4Life Authors API
Published authors. One entry — a shared editorial account, `leaf4l` — exposing only id, name, slug, link, description and avatar URLs anonymously. No personal names, e-mail addr...
LEAF4Life Posts and Comments API
Post and comment collections. Registered and anonymously reachable, both empty — LEAF4Life publishes no news archive, press-release feed or blog through WordPress, so the /feed/...
LEAF4Life oEmbed API
oEmbed 1.0 provider endpoint for URLs on leafforlife.com. Verified anonymously against the site root — provider_name "LEAF4life". This is the only formally standardised interfac...
LEAF4Life Comments API
Comment collection — registered, zero items.
Scroll within the panel for all 9 ·
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Leaf4Life Rate Limits
RATE LIMITSSecurity Posture 2
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 LEAF4Life — 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.
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/leaf4life · machine-readable index on apis.io
This is an independent, third-party profile of LEAF4Life, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.