Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CallChatSyn 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%2Fcallchatsyn.com%2Fcallchatsyn" | 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%2Fcallchatsyn.com%2Fcallchatsyn" | 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 CallChatSyn API.
Answer a customer's message with the business's bot
List the open appointment times a business offers
Book an open appointment slot for a customer
Cancel an existing booking by id
Patterns agents use CallChatSyn API for, with concrete tasks.
GET STARTED
★ Agent Answering and Booking
An AI agent connected through Jentic passes a customer's question to the answer operation and, when the visitor wants to meet, lists open times and books a slot, so a site assistant can both respond and schedule in one conversation. Because answering and booking are separate operations, the agent only books when the customer confirms a time.
Answer the visitor's question about pricing, then list open times and book the slot they choose
Website Answer Widget
A website sends each visitor message to the answer operation and shows the bot's reply, so a site answers common questions with the business's own knowledge without a live agent. The reply comes back in the same call, ready to render in a chat widget.
Send the visitor's message to the answer operation and return the bot's reply for the chat widget
Self-Serve Appointment Booking
An app lists the business's open slots, books the one a customer picks with their name and contact details, and can cancel it later by id, so appointment scheduling runs end to end through the API. The slots operation reflects the times the business currently offers.
List open slots for a haircut, book the 2pm time for the named customer, and confirm the booking
4 endpoints — the callchatsyn api lets a website, app, or ai agent answer customer questions and book appointments through a business's own answering bot.
METHOD
PATH
DESCRIPTION
/api/v1/answer
Answer a customer's message
/api/v1/slots
List open appointment times
/api/v1/bookings
Book an open time
/api/v1/bookings/{id}
Cancel a booking
/api/v1/answer
Answer a customer's message
/api/v1/slots
List open appointment times
/api/v1/bookings
Book an open time
/api/v1/bookings/{id}
Cancel a booking
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CallChatSyn API by hand means handling its bearer key auth, sequencing the answer, slots, and booking operations, and tracking which bookings count toward the plan. Through Jentic you install once, import CallChatSyn from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which operations your agent may call, so you can allow answering questions and listing slots while leaving booking and cancellation out. The message and booking details travel in the request body, so rules bound which operations run rather than which customer is involved.
Credential isolation
Your CallChatSyn key 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 'answer a customer question' or 'book an appointment', and Jentic returns the matching CallChatSyn 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 CallChatSyn API through Jentic.
Is there a CallChatSyn MCP server?
You don't need an MCP server to give your agent the CallChatSyn API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can answer questions and book appointments straight away, with no extra server to run and no tool definitions loaded into the agent's context.
Can I limit what my agent is allowed to do with the CallChatSyn API?
Yes. You choose which operations your agent may call, so you can allow answering questions and listing open slots while leaving booking and cancellation out, and every call it makes is logged. That lets a read-only assistant respond to visitors without ever scheduling or cancelling.
What authentication does the CallChatSyn API use?
The CallChatSyn API authenticates with a bearer API key per its OpenAPI spec, created in the dashboard under Developers, and a public demo key lets you try the flow before signing up. Through Jentic the key is stored encrypted by your own instance and added to each request at call time.
Can I book an appointment through the CallChatSyn API?
Yes. You list the open times the business offers, then create a booking for a chosen slot with the customer's name and contact details, and you can cancel that booking later by its id. Booking requires a start time and a service.
What are the rate limits for the CallChatSyn API?
The OpenAPI spec does not publish a fixed rate limit; requests count toward the business's own plan usage, as described in the spec. For the limits on your plan, see the CallChatSyn dashboard under Developers.
How do I answer a customer question with the CallChatSyn API through Jentic?
Import the CallChatSyn API from the Jentic API Directory, then have your agent issue a request such as 'answer this customer message'. Jentic matches the intent to the answer operation and returns its input schema so the agent builds a valid request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Answer a customer's question with a business's bot, list open appointment slots, and book or cancel appointments. Authenticates with a bearer API key.
Use for: Answer a customer's question with the business bot, Show the open appointment times for this week, Book an appointment for a customer, Cancel a customer's booking
Not supported: Does not handle live agent handoff, payment collection, or outbound marketing messages. Use for answering customer questions and booking appointments through the business bot only.
The CallChatSyn API lets a website, app, or AI agent answer customer questions and book appointments through a business's own answering bot. You send a customer message to the answer operation and get the bot's reply, list the open appointment times the business offers, create a booking for an open slot, and cancel a booking by id. Requests count toward the business's own plan usage, and a public demo key is available to try the flow without signing up.
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>