Install Jentic One Beta

Connect the Lucis public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lucis public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flucis.life%2Flucis" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flucis.life%2Flucis" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lucis public API.

List the biomarkers on a Lucis panel with uuid, unit, category, and translations via GET /v1/biomarkers/public

Switch between panel variants with the template parameter, such as public-complete-eu, public-light-eu, public-v2-complete-uk, or public-v2-light-uk

Tell premium markers and internally computed markers apart using the premium and computedInternally fields

Read the live RateLimit and RateLimit-Policy headers on catalog responses to pace requests

GET STARTED

Start building with Lucis public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lucis public API for, with concrete tasks.

★ Answering panel questions with an agent through Jentic

A wellness assistant answers 'what does the Lucis panel test for?' from the live catalog instead of a stale copy. It searches Jentic for 'list Lucis biomarkers', receives GET /v1/biomarkers/public with its template parameter, and summarises the returned markers by category and unit. No credential is involved, because the catalog is public.

Call GET /v1/biomarkers/public with template public-complete-eu and group the returned biomarkers by category, listing each marker's unit

Panel comparison

Show a prospective member what they gain by moving from a light panel to a complete one. Fetching the catalog twice, once with public-light-eu and once with public-complete-eu, and diffing the uuid sets gives the exact markers added, and the premium flag marks those on a premium panel.

Call GET /v1/biomarkers/public with template public-light-eu and again with public-complete-eu, then list the biomarkers present only in the complete panel

Localised marker glossaries

Build a marker glossary in the reader's language. Each catalog item carries translations alongside its stable uuid, so a site or app can render marker names in the language it needs and keep links stable across catalog updates by keying on the uuid.

Call GET /v1/biomarkers/public with template public-v2-complete-uk and produce a glossary of uuid, translated name, and unit for each marker

Key Endpoints

11 endpoints — the lucis public api publishes the biomarker catalog behind the lucis preventive wellness membership, listing each panel marker with its stable uuid, display unit, category, translations, and flags for premium or internally computed markers.

METHOD

PATH

DESCRIPTION

GET

/v1/biomarkers/public

List public Lucis biomarkers

POST

/oauth/token

Issue a client_credentials access token

GET

/.well-known/oauth-authorization-server

OAuth 2.0 authorization server metadata

GET

/.well-known/oauth-protected-resource

OAuth 2.0 protected resource metadata

GET

/openapi.json

Download the OpenAPI document as JSON

GET

/v1/biomarkers/public

List public Lucis biomarkers

POST

/oauth/token

Issue a client_credentials access token

GET

/.well-known/oauth-authorization-server

OAuth 2.0 authorization server metadata

GET

/.well-known/oauth-protected-resource

OAuth 2.0 protected resource metadata

GET

/openapi.json

Download the OpenAPI document as JSON

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Lucis biomarker list by hand means choosing the right panel template and pacing requests against its RateLimit headers; the optional client_credentials token adds a token request you rarely need. Through Jentic you install once, import Lucis from the API Directory, and your agent calls it.

Permission scoping

Rules filter by method and path, and the panel choice travels in the template query parameter rather than the path, so bound the agent to the operations it needs, such as reading the public biomarker list, rather than to one panel. Token issuance and discovery operations stay out unless you add them.

Credential isolation

Reading biomarkers needs no credential. If you choose to use the optional client_credentials client, it is stored encrypted by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Lucis biomarkers' or 'compare Lucis panels', and Jentic returns GET /v1/biomarkers/public with its input schema, including the template enum, so the agent picks a valid panel without reading the docs.

FAQs

Specific to using Lucis public API through Jentic.

What authentication does the Lucis public API use?

The biomarker catalog needs no authentication. Per its OpenAPI spec, an optional oauth2 client_credentials token with scope catalog.read can be requested from POST /oauth/token, and the catalog accepts it as a Bearer token but ignores it for authorization. Public clients may omit client authentication at the token endpoint.

Does the Lucis public API return member test results?

No. The spec states that it never returns individual member results or other health data. It publishes the catalog of markers on each panel, with their units, categories, translations, and premium or computed flags, plus OAuth and OpenAPI discovery documents.

What are the rate limits for the Lucis public API?

Per the spec, the catalog policy is advertised as RateLimit-Policy "catalog";q=60;w=60, with RateLimit-Limit 60, a live RateLimit header on each catalog response, and Retry-After on HTTP 429. The quota is best-effort per compute instance. See https://www.lucis.life/developers for current details.

Which panels can I query in the Lucis biomarker catalog?

The template parameter on GET /v1/biomarkers/public accepts public-complete-eu, public-light-eu, public-v2-complete-uk, and public-v2-light-uk, and defaults to public-complete-eu. An unknown template returns HTTP 400.

How do I list Lucis biomarkers through Jentic?

Install Jentic One, add the Lucis public API from the Jentic directory, and have your agent search for 'list Lucis biomarkers'. Jentic returns GET /v1/biomarkers/public with its template parameter, and the agent calls it without any credential because the endpoint is public. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Lucis public API?

Yes. A rule that allows only GET /v1/biomarkers/public lets the agent read panel markers and nothing else, keeping token issuance and discovery documents out of its reach. The agent's calls are logged for review.

Lucis Life Lucis public API

AI ReadinessAI-Ready (A-)76/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareClinical Datanone required for the catalog; optional oauth2 client_credentials token with scope catalog.read11 EndpointsREST

For Agents

Read the public Lucis biomarker catalog for EU and UK panels, including marker units, categories, and translations. No authentication required; an optional client_credentials token is available.

Use for: List all biomarkers on the Lucis complete EU panel, Compare the markers on the light and complete Lucis panels, Find which Lucis biomarkers are premium, Get the display unit for a Lucis biomarker

Not supported: Does not return member test results, book blood draws, or manage memberships. Use for reading the public Lucis biomarker catalog and its OAuth discovery documents only.

The Lucis public API publishes the biomarker catalog behind the Lucis preventive wellness membership, listing each panel marker with its stable uuid, display unit, category, translations, and flags for premium or internally computed markers. A template parameter selects the panel variant, such as the complete or light EU panels and their UK v2 counterparts. The catalog is readable without authentication, an optional OAuth 2.0 client_credentials token with scope catalog.read is available from the token endpoint, and discovery documents describe the authorization server and protected resource. It never returns individual member results or other health data.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: BSignals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

45%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Lucis public API to your agent

Capabilities

Start building with Lucis public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lucis Life Lucis public API

Jentic AI Readiness Score

Lucis public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness