Agent-ready OpenAPI document · curated by JenticProductivityCalendar SchedulingapiKey6 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Schedule, list, and cancel meetings against a host's connected calendars and check availability through a small REST surface.
Use for: I want to schedule a 30-minute meeting with a customer, List all meetings booked this week, Cancel a meeting that the customer can no longer attend, Check the host's availability tomorrow afternoon
Not supported: Does not handle video conferencing, payment collection, or contact management - use for meeting scheduling and availability lookups only.
Jentic publishes the only available OpenAPI specification for iMeetify API, keeping it validated and agent-ready. iMeetify is a meeting scheduling service that exposes endpoints for creating, listing, and cancelling meetings, plus availability and calendar lookups. The API targets sales tools, recruiting platforms, and internal apps that need to book a meeting against a host's connected calendars without redirecting users to a third-party scheduler page. The surface is compact - six endpoints - and uses an API key header for authentication.
Install Jentic One Beta
Connect the iMeetify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iMeetify 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.
1
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%2Fimeetify.com%2Fimeetify" | sh2
Step 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%2Fimeetify.com%2Fimeetify" | 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.
Capabilities
What an agent can do with iMeetify API.
Create a meeting with a chosen host, time slot, and invitees
List meetings on the account with filtering by status or host
Retrieve a single meeting record by its identifier
Cancel an existing meeting and notify attendees
Check a host's availability for a candidate window
List the calendars connected to the iMeetify account
Use Cases
Patterns agents use iMeetify API for, with concrete tasks.
★ In-App Meeting Booking
SaaS apps that already authenticate users do not want to redirect them out to a public scheduler page. Calling /availability followed by /meetings booking inside the app keeps the booking flow on-brand and on-domain. iMeetify handles the calendar conflict checks via the host's connected calendars.
GET /availability for the host, present open slots to the user, then POST /meetings with the chosen slot and invitee details.
Sales Outreach Automation
Sales tools that book follow-up meetings after a lead converts can automate the booking via the iMeetify API. The tool calls /availability, picks the next open 30-minute slot, and posts a /meetings creation with the lead's email. The booked meeting writes back to the rep's connected calendar automatically.
After a lead converts, GET /availability for the assigned rep, POST /meetings with the next open slot and the lead's email, and log the meeting ID on the lead record.
Recruiting Interview Coordination
Recruiting platforms book interviews with multiple panel members. The platform queries /calendars and /availability for each panel member, finds an overlap, and creates the meeting once a slot is agreed. Cancelling and rescheduling go through DELETE /meetings/{meeting_id} so candidates always see fresh state.
GET /availability for each panellist, intersect the open windows, POST /meetings with the agreed slot, and DELETE /meetings/{meeting_id} on cancellation.
Agent-Driven Calendar Booking
An AI scheduling assistant that reads emails and proposes meeting times can call iMeetify directly through Jentic. The agent reads the host's availability, proposes a slot, and creates the meeting once both sides confirm. Jentic keeps the API key vaulted and returns the booking schema so the agent fills only the slot, host, and invitee fields.
Search Jentic for 'schedule a meeting with iMeetify', execute /availability and /meetings POST, and confirm the booking ID back to the user.
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for imeetify api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/meetings
Create a meeting
GET
/meetings
List meetings on the account
GET
/meetings/{meeting_id}
Retrieve a meeting by ID
DELETE
/meetings/{meeting_id}
Cancel a meeting
GET
/availability
Check host availability
GET
/calendars
List connected calendars
POST
/meetings
Create a meeting
GET
/meetings
List meetings on the account
GET
/meetings/{meeting_id}
Retrieve a meeting by ID
DELETE
/meetings/{meeting_id}
Cancel a meeting
GET
/availability
Check host availability
GET
/calendars
List connected calendars
Jentic AI Readiness Score
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.
I
iMeetify API
- AI-Aware (B)64/100
100
Foundational Compliance56
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
25%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring iMeetify by hand means setting up its X-API-Key header against api.imeetify.com and handling the meeting and availability lookups yourself. Through Jentic you install once, import the iMeetify API from the API Directory, store the key once, and your agent calls it.
Permission scoping
iMeetify puts the meeting id in the URL path (/meetings/{meeting_id}), so a rule can pin your agent to one meeting. You choose the operations it may call, so destructive ones like deleting a meeting are not included unless you add them.
Credential isolation
Your iMeetify API key is stored once, encrypted, by your own Jentic One instance and injected into the request header 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 'check availability', and Jentic returns the matching iMeetify operation with its input schema, including the slot and invitee fields, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using iMeetify API through Jentic.
Why is there no official OpenAPI spec for iMeetify API?
iMeetify does not publish a canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call iMeetify via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the iMeetify API use?
The API uses an API key in a request header (ApiKey scheme). Through Jentic the key is held in the encrypted vault and added to the request at execute time, so the agent prompt never sees it.
Can I check a host's availability before booking?
Yes. GET /availability returns open windows for the connected host's calendars, which you can present to the user before calling POST /meetings to confirm the booking.
How do I cancel a meeting?
DELETE /meetings/{meeting_id} cancels the meeting and notifies the participants based on the host's iMeetify settings.
How do I book a meeting through Jentic?
Run pip install jentic, search for 'schedule a meeting with iMeetify', load the /meetings POST schema, and execute with the host, slot, and invitee details. Jentic chains the availability check if requested.
What are the rate limits for the iMeetify API?
The OpenAPI spec does not list explicit rate limits. Plan for normal scheduling-app traffic and back off on HTTP 429 responses if running bulk imports.
Can I limit what my agent is allowed to do with the iMeetify API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which iMeetify operations and credentials your agent may use. You can grant read-only calls like GET /availability, GET /calendars, and GET /meetings while withholding write and destructive operations such as POST /meetings or DELETE /meetings/{meeting_id} unless you explicitly add them. Since the meeting id sits in the URL path, a rule can also pin the agent to a single meeting so it cannot touch others.
GET STARTED