Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CalendarHero 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%2Fcalendarhero.com%2Fcalendarhero" | 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%2Fcalendarhero.com%2Fcalendarhero" | 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 CalendarHero API.
Schedule and manage meetings and their categories
Create and track follow-up tasks on a meeting
Manage contacts and look them up across the account
Read and update the user profile and connected directories
Subscribe to webhooks for meeting events
GET STARTED
Handle web conversation messages
Patterns agents use CalendarHero API for, with concrete tasks.
★ Agent Meeting Scheduling
An AI agent connected through Jentic creates a meeting, attaches follow-up tasks, and links the right contact, so a scheduling assistant runs without a person clicking through the app. Because contacts and meetings are separate resources, the agent can reuse a known contact when booking.
Schedule a 30-minute meeting with the contact named Jordan and add a follow-up task to send notes
Contact-Linked Follow-ups
An assistant creates follow-up tasks on a meeting and ties them to the contacts involved, so action items are tracked against the right people after a call. The meeting-tasks operations let an agent add, list, and remove tasks as the follow-up progresses.
Create two follow-up tasks on today's client meeting and link them to that client's contact
Webhook-Driven Meeting Sync
An integration subscribes to meeting webhooks so an external system is notified when a meeting is created or changed, keeping a CRM or planner in sync without polling. A sample payload operation helps an agent set up the handler before going live.
Subscribe to the new-meeting webhook and confirm the handler with the sample payload
40 endpoints — the calendarhero api schedules meetings and manages the people and conversations around them for a meeting-automation assistant.
METHOD
PATH
DESCRIPTION
/user
Get the user profile
/contact
List contacts
/contact
Create a contact
/meeting
List meetings
/meeting/tasks
Create a meeting follow-up task
/search
Search records across the account
/provider
Get the connected provider
/user
Get the user profile
/contact
List contacts
/contact
Create a contact
/meeting
List meetings
/meeting/tasks
Create a meeting follow-up task
/search
Search records across the account
/provider
Get the connected provider
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CalendarHero API by hand means handling its API token auth, keeping contacts, meetings, and tasks in sync, and registering webhook handlers for meeting events. Through Jentic you install once, import CalendarHero from the API Directory, store the token once, and your agent calls it.
Permission scoping
You choose which operations your agent may call, so you can allow scheduling meetings and reading contacts while leaving contact deletion and directory changes out. Meeting and contact details travel in the request body, so rules bound which operations run rather than which record is touched.
Credential isolation
Your CalendarHero 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 'schedule a meeting' or 'add a follow-up task', and Jentic returns the matching CalendarHero 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 CalendarHero API through Jentic.
Is there a CalendarHero MCP server?
You don't need an MCP server to give your agent the CalendarHero API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can schedule meetings and manage contacts 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 CalendarHero API?
Yes. You choose which operations your agent may call, so you can allow scheduling meetings and reading contacts while leaving contact deletion and profile changes out, and every call it makes is logged. That keeps a scheduling agent from editing your account settings.
What authentication does the CalendarHero API use?
The CalendarHero API authenticates with an API token sent in the Authorization header per its OpenAPI spec. Through Jentic the token is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.
Can I attach follow-up tasks to a meeting with the CalendarHero API?
Yes. The meeting resource has operations to list, create, and remove follow-up tasks, so an agent can add action items to a meeting and track them afterward alongside the meeting's category and details.
What are the rate limits for the CalendarHero API?
The OpenAPI spec does not specify rate limits for the CalendarHero API. For current limits, see the CalendarHero documentation at https://api.calendarhero.com.
How do I schedule a meeting with the CalendarHero API through Jentic?
Import the CalendarHero API from the Jentic API Directory, then have your agent issue a request such as 'schedule a meeting with this contact'. Jentic matches the intent to the create-meeting operation and returns its input schema so the agent builds a valid request, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Schedule and manage meetings, contacts, follow-up tasks, and webhooks for a CalendarHero account. Authenticates with an API token sent in the Authorization header.
Use for: Schedule a meeting with a contact, Add a follow-up task to a meeting, Find a contact by name, List the meetings on my account
Not supported: Does not handle payments, video conferencing, or email marketing. Use for scheduling meetings and managing their contacts and follow-up tasks only.
The CalendarHero API schedules meetings and manages the people and conversations around them for a meeting-automation assistant. You read and update the user profile and connected directories, manage contacts, and work with meetings, their categories, and follow-up tasks. Search operations look up records across the account, webhooks notify your app when meeting events occur, and a messaging operation handles web conversation threads.
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>