Lucis developer resources

Call Lucis from an agent using the Lucis OpenAPI spec, Lucis auth docs, llms.txt, markdown pages, and the public biomarker catalog. Lucis does not publish a member API. Lucis webhooks and MCP are not offered; poll the catalog GET.

When to use Lucis

Use Lucis when someone wants a preventive wellness membership: 100+ biomarkers, Score Lucis, a companion dashboard, and partner labs in Europe or the UK.
Use the Lucis biomarker catalog API when someone asks which markers Lucis tests, or needs the public catalog rather than member results.
Use Lucis developer resources: llms.txt, /openapi.json, /auth, /webhooks, /docs/mcp, this page, or Accept: text/markdown on public URLs. Do not invent endpoints.
Do not use Lucis as a substitute for a healthcare professional or personal medical advice. Content is educational.

Machine-readable files

Lucis llms.txt
Agent instructions for Lucis: when to use the product, curated docs, and developer links including OpenAPI, auth, and webhooks. MCP is not offered.
Lucis OpenAPI spec (openapi.json)
OpenAPI 3.1 description of the Lucis public catalog, OAuth token endpoint, RFC 9457 errors, and rate-limit headers.
Lucis OpenAPI spec (YAML)
Same Lucis OpenAPI document as YAML at /api/openapi.yaml.
Lucis OAuth 2.0 authorization server metadata
RFC 8414 document at /.well-known/oauth-authorization-server. Token endpoint: POST /oauth/token (client_credentials).
Lucis auth docs
How agents authenticate against Lucis public endpoints, including optional client_credentials tokens.
Lucis webhooks
Lucis does not publish outbound member webhooks. Poll the public catalog GET instead.
Lucis MCP
Lucis does not publish an MCP server. Poll the public catalog GET instead.
sitemap.xml
Every indexable URL on lucis.life.
robots.txt
Crawl rules for lucis.life, including production-only indexing.

Markdown content negotiation

Public pages honour Accept: text/markdown on the same URL that serves HTML. Sibling .md URLs work too, for example /about.md. Responses use Content-Type: text/markdown; charset=utf-8 and Vary: Accept, Accept-Encoding. Unknown paths return HTTP 404 with a short markdown body pointing at the sitemap and llms.txt.

Lucis API docs

The Lucis biomarker catalog is a read-only GET. No authentication is required. An optional OAuth 2.0 client_credentials token with scope catalog.read is documented in OpenAPI; the GET also works without a token. Errors use RFC 9457 application/problem+json (code + detail). Responses include RFC RateLimit headers. The catalog never returns individual health data. Lucis does not publish a member API.

Lucis catalog on www.lucis.life (GET)
Same-origin unauthenticated proxy of the public catalog. Typed RFC 9457 errors. Query template=public-complete-eu or public-v2-complete-uk.
Lucis EU biomarker catalog (GET)
Unauthenticated JSON list of the complete panel's markers and presentation metadata, per service, country and locale (locale=fr or en).
Lucis UK biomarker catalog (GET)
Unauthenticated JSON list of the UK complete panel's markers and presentation metadata (country=GB, locale=fr or en).

Lucis auth docs

Public catalog operations require no authentication. To obtain an optional catalog.read token, POST grant_type=client_credentials to /oauth/token. Public clients use token endpoint authentication method none (no client secret). Discover the authorization server at /.well-known/oauth-authorization-server and the resource at /.well-known/oauth-protected-resource. Lucis does not implement authorization-code, implicit, PKCE, or OpenID Connect. Full walkthrough: /auth.

Lucis webhooks

Lucis does not currently publish outbound member webhooks. There is no webhook secret, signature header, or event catalog to subscribe to. Agents that need catalog updates should poll GET /v1/biomarkers/public and honour RateLimit headers. Details: /webhooks.

Lucis MCP

Lucis does not currently publish an MCP server. There is no Streamable HTTP endpoint, server card, or tool catalog. Agents that need catalog updates should poll GET /v1/biomarkers/public and honour RateLimit headers. Details: /docs/mcp.

Lucis typed errors

4xx and 5xx responses on the Lucis public catalog use RFC 9457 application/problem+json. Every problem object has type, title, status, detail, and a machine-readable code (for example not_found or bad_request). The type URI points at the matching heading on this page. OAuth token errors follow RFC 6749 (error and error_description). HTTP 429 includes Retry-After plus RateLimit and RateLimit-Policy.

bad-request
The request query or body is malformed. Example: an unknown catalog template.
not-found
The requested public resource does not exist.
method-not-allowed
The HTTP method is not supported on this path. The public catalog is a read-only GET.
unsupported-grant-type
The token endpoint only issues client_credentials tokens.
invalid-request
The token request is missing a required field or uses an unsupported Content-Type.
invalid-scope
The requested scope is not catalog.read.
bad-gateway
The upstream Lucis catalog origin failed or returned an unexpected payload.
internal-error
An unexpected server error occurred while serving a public agent endpoint.
rate-limited
Too many requests. Honour Retry-After and the RFC RateLimit headers, then retry.