Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Lenus eHealth website screenshot

Lenus eHealth

Lenus eHealth is a Copenhagen-headquartered health and fitness technology company that builds a coaching platform for online health and fitness coaches, positioning itself as a growth partner rather than a consumer fitness app. Coaching partners run their businesses through the Lenus web dashboard and branded consumer mobile apps: client onboarding and screening, training and nutrition programming, habit and progress tracking, in-app messaging, content delivery, subscription billing and business analytics. The company also operates Lenus Academy, a certified education program for online coaches, and in the United States offers a GLP-1 weight management program delivered with independent medical partner Beluga Health. Lenus operates from 20+ offices including Copenhagen, Berlin, London, Amsterdam, Stockholm, Madrid, New York and Toronto, and is backed by EQT Ventures. The platform is closed and invitation-based: as of July 2026 Lenus publishes no public API, developer portal, SDKs or machine-readable API specifications, and access is available only to coaching partners under a partnership agreement.

human only

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.

Kin Score

API Evangelist profiles Lenus eHealth the way a machine reads it — 1 machine-readable artifact, 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 — Lenus eHealth scores 17.8/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 17.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Health 4.6 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Lenus eHealth

Each block below is one kind of artifact we hold for Lenus eHealth. 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.

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.

Lenus Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Lenus eHealth — 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

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/lenus · machine-readable index on apis.io