Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HairDora 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%2Fhairdora.com%2Fhairdora" | 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%2Fhairdora.com%2Fhairdora" | 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 HairDora API.
Book, reschedule, and cancel client appointments for a salon
Manage client records and their contact details
Maintain the salon's service menu and pricing
Read salon location details
Subscribe to webhooks for appointment and client changes
GET STARTED
Patterns agents use HairDora API for, with concrete tasks.
★ Automated Salon Booking
An agent books and reschedules salon appointments for clients. It looks up the client, confirms the chosen service exists on the salon's menu, creates the appointment, and updates it to reschedule when the client asks. Because clients, salons, and services are separate resources, the agent validates each before writing the booking.
Create an appointment for a client at a salon for a selected service and confirm the appointment was created
Client Record Sync
A salon keeps its own CRM aligned with HairDora. The agent lists clients for a salon, creates new client records as they walk in, and updates contact details. Keeping client records consistent lets the salon run follow-ups and retention outreach from accurate data.
List clients for a salon, create a new client with contact details, and confirm the record was stored
Event-Driven Salon Tools
An agent reacts to salon activity using webhook subscriptions. It subscribes to appointment and client events, then sends a reminder when an appointment is booked or flags a cancellation for the front desk. Subscriptions are created, updated, and deleted through the API, so the agent manages them as the salon's needs change.
Create a webhook subscription for appointment events and confirm the subscription is active
22 endpoints — the hairdora api manages the clients, appointments, and services behind a hair salon across one or more salon locations.
METHOD
PATH
DESCRIPTION
/api/clients
List clients
/api/clients
Create a client
/api/appointments
List appointments
/api/appointments
Create an appointment
/api/services
List services
/api/salons
List salons
/api/clients
List clients
/api/clients
Create a client
/api/appointments
List appointments
/api/appointments
Create an appointment
/api/services
List services
/api/salons
List salons
What agents get from Jentic-routed access to this vendor.
Setup
Wiring HairDora by hand means handling two auth styles, HTTP basic and an Authorization-header token, and tracking separate client, salon, service, and appointment resources. Through Jentic you install once, import HairDora from the API Directory, store the credential once, and your agent calls it.
Permission scoping
HairDora puts resource ids in the URL path, such as a salon id or client id, so a rule can pin your agent to the client and appointment operations for one salon. You choose the operations it may call, so destructive ones like client or appointment deletion are not included unless you add them.
Credential isolation
Your HairDora 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 salon appointment' or 'add a new client', and Jentic returns the matching HairDora 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 HairDora API through Jentic.
What authentication does the HairDora API use?
Per its OpenAPI spec, the HairDora 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 HairDora API?
Yes. The API exposes list, create, read, update, and delete operations on appointments, so an agent can find a client's existing bookings, create a new appointment for a service, update it to reschedule, and delete it to cancel. Clients, salons, and services are separate resources the agent can confirm before writing a booking.
What are the rate limits for the HairDora 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 HairDora documentation at https://www.hairdora.com for any published limits before running high-volume jobs.
Can I limit what my agent is allowed to do with the HairDora API?
Yes. Write a rule that allows the appointment and client read and create operations for one salon id, so the agent can book and look clients up while the service-menu and delete operations stay out of reach, and every call it makes is logged. HairDora carries salon and client ids in the URL path, which is what makes that per-salon boundary possible.
Is there a HairDora MCP server?
You do not need an MCP server to give your agent the HairDora API. Jentic connects it directly from the Jentic API Directory: import HairDora, store your credential once, and your agent calls the client, appointment, and service operations on demand without loading another server's tool definitions into its context.
How do I book a salon appointment with the HairDora API through Jentic?
Search Jentic by intent such as 'book a salon appointment', and Jentic returns the HairDora 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 HairDora from the directory.
For Agents
Manage salon clients, appointments, and services across salon locations, list API keys, and subscribe to webhooks so an agent reacts when a booking changes.
Use for: Book an appointment for a client at the salon, List all clients for a given salon, Create a new service on the salon's menu, Check whether a client appointment was cancelled
Not supported: Does not handle marketing campaigns, inventory, or accounting. Use for salon client, appointment, and service management only.
The HairDora API manages the clients, appointments, and services behind a hair salon across one or more salon locations. It lets a backend list and create clients, book and reschedule appointments, maintain the salon's service menu, read salon details, and manage the API keys and webhook subscriptions that connect HairDora to other tools. Webhook subscriptions let a system react when a client books, reschedules, or cancels, so the salon's own tooling stays current.
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>