canonical: https://jentic.com/apis/longevityworldcup.com/longevityworldcup

# Longevity World Cup Public API

Public no-auth JSON endpoints for Longevity World Cup athlete, field, biological aging clock calculation, and rank-preview data. The documented endpoints are public data and biological aging clock calculation surfaces used by the website and external clients. They do not require API keys, OAuth, cookies, or other authentication. The API exposes 6 endpoints.

## For AI agents

Programmatically list selectable flags, list competition divisions. Covers 6 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- List selectable flags
- Calculate Pheno Age
- Preview a hypothetical Ultimate League rank
- Query and filter Longevity World Cup Public API records by parameters
- Monitor Longevity World Cup Public API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Longevity World Cup Public API to perform identity auth operations programmatically. The API provides 6 endpoints covering core functionality including list selectable flags, list competition divisions, list public longevity athlete data.

Example prompt: Call GET `/api/data/flags` to list selectable flags

### Automated Data Management

Automate data operations by combining multiple Longevity World Cup Public API endpoints. Agents can list competition divisions and then list public longevity athlete data in a single workflow.

Example prompt: Call GET `/api/data/divisions` to list competition divisions, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Longevity World Cup Public API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'list selectable flags', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/data/flags` | List selectable flags |
| GET | `/api/data/divisions` | List competition divisions |
| GET | `/api/data/athletes` | List public longevity athlete data |
| POST | `/api/data/pheno-age` | Calculate Pheno Age |
| POST | `/api/data/bortz-age` | Calculate Bortz Age |
| POST | `/api/data/hypothetical-rank` | Preview a hypothetical Ultimate League rank |

## Key resources

- **Data** — Operations related to Data

## Why Jentic

- **Setup:** Wiring the Longevity World Cup Public API by hand still means reading its docs, matching the right endpoint for flags, divisions, athletes, and age calculations, and shaping each request body against longevityworldcup.com yourself. Through Jentic you install once, import Longevity World Cup from the API Directory, and your agent calls it without you writing that client code.
- **Permission scoping:** The Longevity World Cup Public API needs no credential and carries its inputs in query strings and request bodies rather than an account id in the URL path, so scoping is by operation: limit the agent to the operations it needs, such as listing divisions or computing a pheno-age, and leave out the others.
- **Credential handling:** This API requires no credential, so there is no secret to store: Jentic calls the public endpoints at execution time and no key ever enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list selectable flags' or 'calculate a biological age', and Jentic returns the matching Longevity World Cup operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Longevity World Cup Public API use?

The Longevity World Cup Public API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list selectable flags with the Longevity World Cup Public API?

Yes. Use the GET `/api/data/flags` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Longevity World Cup Public API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list selectable flags through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list selectable flags'. Jentic returns the matching Longevity World Cup Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Longevity World Cup Public API have?

The Longevity World Cup Public API exposes 6 endpoints covering data operations.

### Can I limit what my agent is allowed to do with the Longevity World Cup Public API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and scoping here is per operation since the API needs no credential and carries its inputs in query strings and request bodies rather than an account id in the path. You can allow only the calls the agent needs, such as listing divisions or computing a Pheno Age, while leaving out listing athletes, listing flags, computing a Bortz Age, or previewing a hypothetical Ultimate League rank. The operator sets these limits, so the agent can reach only the endpoints you have approved.