Install Jentic One Beta

Connect the API de Control de Acceso - Gimnasio to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API de Control de Acceso - Gimnasio, 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%2Flonvia.cl%2Flonvia" | 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%2Flonvia.cl%2Flonvia" | 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 API de Control de Acceso - Gimnasio API.

Validate gym entry for a member by Chilean RUT with POST /access/check and receive an access true or false decision

Restrict the check to one gym location by passing an optional branch_id

Accept RUTs with or without dots and hyphen, such as 16.937.044-3, 16937044-3, or 169370443

Return the member's name and membership_expires date when access is granted, and a reason such as no active membership when denied

GET STARTED

Start building with API de Control de Acceso - Gimnasio API

Explore with Jentic One

View OpenAPI Document

★ Front-desk agent access checks through Jentic

A front-desk assistant agent asks Jentic for the Lonvia access check, sends the RUT a visitor gives at reception, and tells staff whether the person may enter, showing the member's name and membership_expires date when access is granted. The X-API-Token header value stays in your self-hosted Jentic One instance instead of in the agent's prompt.

Search Jentic for 'check gym access by RUT', call POST /access/check with rut '16.937.044-3', and report the access value and membership_expires

Turnstile and door integration

A door controller reads a member's RUT from a card, QR code, or keypad, posts it to the access check, and opens the turnstile only when the response carries access true. Because every attempt is recorded, granted and denied entries both leave a trail on the gym side.

Call POST /access/check with rut '169370443' and open the turnstile only if access is true

Branch-specific membership validation

Gyms with several locations pass branch_id so the check validates membership for that branch only. A member with an active plan at one location is then refused at another branch their plan does not cover.

Call POST /access/check with rut '16937044-3' and branch_id 2, then report whether access is allowed at that branch

Key Endpoints

1 endpoints — the lonvia gym access control api decides whether a person may enter a gym, given their chilean rut.

METHOD

PATH

DESCRIPTION

POST

/access/check

Validate a member's gym access by RUT

POST

/access/check

Validate a member's gym access by RUT

Why Jentic?

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

Setup

Wiring this API by hand means sending its static token in the X-API-Token header and normalizing RUT formats yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

The spec exposes a single operation, POST /access/check, and the RUT and branch travel in the request body, so a rule bounds the agent to that access check rather than to particular members or branches.

Credential isolation

Your Lonvia token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check gym access by RUT' or 'is this member allowed in', and Jentic returns the Lonvia access check with its input schema so the agent sends the right fields without browsing the reference docs.

FAQs

Specific to using API de Control de Acceso - Gimnasio API through Jentic.

What authentication does the Lonvia gym access control API use?

Per its OpenAPI spec, the API uses an apiKey scheme: a static token sent in the `X-API-Token` header. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I check gym access for a specific branch with the Lonvia API?

Yes. POST /access/check accepts an optional branch_id alongside the required rut. When branch_id is set, the API validates membership for that branch only; without it, any active, unexpired membership grants access.

What are the rate limits for the Lonvia gym access control API?

The OpenAPI spec does not specify rate limits. Ask the Lonvia team for current limits before connecting several turnstiles to the same token.

How do I validate a member's access with the Lonvia API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add the API from the Jentic API Directory, and have your agent search for 'check gym access by RUT'. Jentic returns POST /access/check with its schema, and the agent sends the rut and, if needed, branch_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Lonvia MCP server?

You don't need an MCP server to give your agent the Lonvia gym access control API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it.

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

Yes. Write a rule that allows only POST /access/check, so the agent can answer whether a RUT may enter and nothing more; with a single operation in the spec, that rule is the agent's whole reach, and every call it makes is logged in your Jentic One instance.

What does the Lonvia API return when access is denied?

A 200 response with access false and a message explaining the reason, such as no active membership or user not found. A granted response carries access true, a message, and a user object with name and membership_expires. Invalid input returns 422 and a bad token returns 401.

Lonvia Cl API de Control de Acceso - Gimnasio

AI ReadinessFoundational (C+)58/100

See full scorecard

Community OpenAPI document · agent-readyIdentity AuthAuthorizationapiKey (X-API-Token header)1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Check whether a gym member may enter by sending their Chilean RUT, optionally for a specific branch, and get back an access decision with the member's name and membership expiry.

Use for: Check whether RUT 16.937.044-3 can enter the gym, Is this member allowed into branch 1?, Find out when a member's membership expires, I want to know why a member was denied at the turnstile

Not supported: Does not sell or renew memberships, register new members, or book classes. Use for checking whether a member may enter the gym by RUT only.

The Lonvia gym access control API decides whether a person may enter a gym, given their Chilean RUT. Door controllers, turnstiles, and front-desk systems send the RUT, in any format with or without dots and hyphen, and optionally a branch_id to validate membership for one location. The API checks that the user exists, that the membership status is active, and that it has not expired, then returns access true with the member's name and membership_expires date, or access false with a reason, and records every attempt, granted or denied.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 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).

75%

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: ASignals: 4

62%

Example Density

How richly the API is illustrated with examples.

90%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: FSignals: 4

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

89%

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: C-Signals: 1

50%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the API de Control de Acceso - Gimnasio to your agent

Capabilities

Start building with API de Control de Acceso - Gimnasio API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lonvia Cl API de Control de Acceso - Gimnasio

Jentic AI Readiness Score

API de Control de Acceso - Gimnasio

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