For Agents
Manage fitness studio scheduling, book appointments, query available time slots, and administer people and event records for class-based businesses.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pike13 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Pike13 API.
Find available appointment slots for specific services and instructors
Create and manage class bookings with participant details
List and filter events and their recurring occurrences
Administer people records including staff and client profiles
GET STARTED
Use for: I need to find available time slots for a yoga class, I want to book an appointment for a client, List all upcoming events at this studio location, Retrieve a specific booking by ID
Not supported: Does not handle payment processing, membership billing, or marketing campaigns — use for class scheduling and booking management only.
Jentic publishes the only available OpenAPI specification for Pike13 API, keeping it validated and agent-ready. Pike13 API manages fitness studio and class scheduling operations including appointment bookings, event management, people records, custom fields, and business account administration. The API supports finding available time slots, creating bookings, managing event occurrences, and handling multi-location franchise configurations.
Configure custom fields for business-specific data collection
Manage multi-location franchise configurations and branding
Patterns agents use Pike13 API for, with concrete tasks.
★ Class Availability and Booking
Query available appointment slots for fitness classes and services, then create bookings for clients. The Pike13 API returns time slots based on service type, instructor availability, and location, enabling automated scheduling for yoga studios, gyms, and wellness centers.
Query available slots for service ID 42 on 2026-06-20 and create a booking for the first available time
Event and Schedule Management
Manage recurring classes, workshops, and special events through the Pike13 API. The /front/events and /front/event_occurrences endpoints handle scheduling, capacity tracking, and occurrence listing, supporting studios that run weekly classes with varying instructors and rooms.
List all event occurrences for the current week and retrieve participant counts for event ID 101
Client and Staff Administration
Maintain people records for clients and staff through the Pike13 API. The /account/people endpoint supports profile management, custom field data, and business association, enabling studios to track membership details, attendance history, and instructor qualifications.
Retrieve the people list filtered by active membership and export their custom field data
AI Agent Studio Scheduling
AI agents use the Pike13 API through Jentic to automate class bookings and schedule queries without manual API configuration. Agents search for scheduling operations by intent, load the endpoint schema, and execute calls with Jentic handling Bearer token authentication.
Search Jentic for 'book a fitness class appointment', load the Pike13 bookings endpoint schema, and create a booking for a client
16 endpoints — jentic publishes the only available openapi specification for pike13 api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/front/appointments/{service_id}/available_slots
Find available time slots for a service
/front/bookings
Create a new booking
/front/bookings/{id}
Retrieve a specific booking
/front/events
List all events
/front/event_occurrences
List event occurrences
/account/people
List people records
/front/business
Retrieve business configuration
/desk/custom_fields
List custom field definitions
/front/appointments/{service_id}/available_slots
Find available time slots for a service
/front/bookings
Create a new booking
/front/bookings/{id}
Retrieve a specific booking
/front/events
List all events
/front/event_occurrences
List event occurrences
Three things that make agents converge on Jentic-routed access.
Credential isolation
Pike13 OAuth Bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens with automatic refresh so raw credentials never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'book a fitness class') and Jentic returns matching Pike13 operations with their input schemas, so the agent can call the right endpoint without reading docs.
Time to first call
Direct Pike13 integration: 2-4 days for OAuth setup, availability queries, and booking flow. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Pike13 API through Jentic.
Why is there no official OpenAPI spec for Pike13 API?
Pike13 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pike13 API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Pike13 API use?
The Pike13 API uses Bearer token authentication via OAuth 2.0. You include your access token in the Authorization header. Through Jentic, these tokens are stored encrypted in the MAXsystem vault and refreshed automatically.
Can I check class availability and book appointments with the Pike13 API?
Yes. Use GET /front/appointments/{service_id}/available_slots to query open time slots for a specific service, then POST /front/bookings to create a booking in an available slot.
How do I list upcoming class occurrences through the Pike13 API?
Use GET /front/event_occurrences with date range filters to retrieve upcoming class instances. Each occurrence includes the event details, instructor, time, and current participant count.
How do I book a class through the Pike13 API using Jentic?
Search Jentic for 'book a fitness class appointment', load the /front/bookings operation schema, and execute with participant and time slot details. Jentic handles OAuth Bearer token injection and returns the booking confirmation.
Does the Pike13 API support multi-location studios?
Yes. The /front/business/franchisees endpoint lists franchise locations, and the /account/businesses endpoint manages multiple business entities. Events and bookings are scoped to specific locations through the subdomain configuration.
/account/people
List people records
/front/business
Retrieve business configuration
/desk/custom_fields
List custom field definitions