Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GymFlexa 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%2Fgymflexa.com%2Fgymflexa" | shStep 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%2Fgymflexa.com%2Fgymflexa" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with GymFlexa API.
Book, reschedule, and look up member appointments across a gym's schedule
Manage member records and attach them to a specific gym location
Maintain the gym's service catalogue and pricing
Record and retrieve member payments
Subscribe to webhooks for member, appointment, and payment changes
GET STARTED
Patterns agents use GymFlexa API for, with concrete tasks.
★ Automated Member Booking
An agent books and reschedules gym appointments on behalf of members. It lists a member's existing appointments, creates a new one against the right gym and service, and confirms the booking. Because members, gyms, and services are separate resources, the agent can validate that a member belongs to the gym and that the service exists before it writes the appointment.
Create an appointment for a member at a given gym for a selected service and confirm the appointment was created
Membership and Payment Sync
A gym keeps its own CRM or billing tool in sync with GymFlexa. The agent lists members per gym, records payments as they are collected, and reads payment history for reconciliation. Keeping member and payment records aligned lets the gym answer who has paid and who is overdue without a manual export.
List members for a gym, record a payment for one member, and return that member's recent payment history
Event-Driven Front Desk
An agent reacts to gym activity in real time using webhook subscriptions. It subscribes to member, appointment, and payment events, then takes a follow-up action such as sending a welcome message when a member is created or flagging a failed payment. Subscriptions are managed through the API, so the agent can add and remove them as the gym's needs change.
Create a webhook subscription for new member events and confirm the subscription is active
28 endpoints — the gymflexa api manages the members, appointments, services, and payments behind a gym or fitness studio.
METHOD
PATH
DESCRIPTION
/api/members
List members
/api/members
Create a member
/api/appointments
List appointments
/api/appointments
Create an appointment
/api/payments
Create a payment
/api/webhooksubscriptions
Create a webhook subscription
/api/members
List members
/api/members
Create a member
/api/appointments
List appointments
/api/appointments
Create an appointment
/api/payments
Create a payment
/api/webhooksubscriptions
Create a webhook subscription
What agents get from Jentic-routed access to this vendor.
Setup
Wiring GymFlexa by hand means handling two auth styles, HTTP basic and an Authorization-header token, and tracking separate member, gym, service, and payment resources. Through Jentic you install once, import GymFlexa from the API Directory, store the credential once, and your agent calls it.
Permission scoping
GymFlexa puts resource ids in the URL path, such as a gym id or member id, so a rule can pin your agent to the member and appointment operations for one gym. You choose the operations it may call, so destructive ones like member or payment deletion are not included unless you add them.
Credential isolation
Your GymFlexa credential 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 'book a gym appointment' or 'record a membership payment', and Jentic returns the matching GymFlexa operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using GymFlexa API through Jentic.
What authentication does the GymFlexa API use?
Per its OpenAPI spec, the GymFlexa API accepts HTTP basic authentication and an access token sent in the Authorization header. Through Jentic the credential is stored by your own self-hosted instance and injected when the agent calls an operation, so it never appears in the agent's prompt or logs.
Can I book and reschedule appointments with the GymFlexa API?
Yes. The API exposes list, create, read, and update operations on appointments, so an agent can look up a member's existing bookings, create a new appointment against a gym and service, and update it to reschedule. Members, gyms, and services are separate resources, so the agent can confirm each exists before writing the booking.
What are the rate limits for the GymFlexa API?
The OpenAPI spec does not state a numeric rate limit. Add retry and backoff around 429 responses and poll on a reasonable cadence, and check the GymFlexa documentation at https://www.gymflexa.com for any published limits before running high-volume jobs.
Can I limit what my agent is allowed to do with the GymFlexa API?
Yes. Write a rule that allows the appointment list and create operations plus member reads for a single gym id, so the agent can book and look people up without reaching the payment or delete operations, and every call it makes is logged. GymFlexa carries gym and member ids in the URL path, which is what makes that per-gym boundary possible.
Is there a GymFlexa MCP server?
You do not need an MCP server to give your agent the GymFlexa API. Jentic connects it directly from the Jentic API Directory: import GymFlexa, store your credential once, and your agent calls the member, appointment, and payment operations on demand without loading another server's tool definitions into its context.
How do I book a gym appointment with the GymFlexa API through Jentic?
Search Jentic by intent such as 'book a gym appointment', and Jentic returns the GymFlexa appointment create operation with its input schema so the agent sends the right fields. To run it on your own infrastructure, install Jentic One from its GitHub repo with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add GymFlexa from the directory.
For Agents
Manage gym members, appointments, services, payments, and multiple gym locations, and subscribe to webhooks so an agent reacts when any of them change.
Use for: Book an appointment for a member at one of our gyms, List all members registered at a specific gym, Create a new service and add it to the gym's catalogue, Record a payment against a member's account
Not supported: Does not handle workout programming, marketing campaigns, or accounting. Use for gym member, appointment, service, and payment management only.
The GymFlexa API manages the members, appointments, services, and payments behind a gym or fitness studio. It lets a backend list and create members, book and reschedule appointments, maintain the gym's service catalogue, record payments, and keep multiple gym locations in sync. Webhook subscriptions let a system react the moment a member, appointment, or payment changes, so a gym's own tools stay current without polling.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>