Install Jentic One Beta

Connect the AllMyMeetings API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AllMyMeetings 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%2Fallmymeetings.com%2Fallmymeetings" | sh

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%2Fallmymeetings.com%2Fallmymeetings" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 AllMyMeetings API.

Create, update, and remove calendar events across connected Google and Microsoft accounts

Manage sync pairs that mirror events between two calendars

Create and manage scheduling links for booking meetings

Look up availability and detect scheduling conflicts before booking

Receive real-time calendar change notifications from Google Calendar and Microsoft Graph via webhooks

GET STARTED

Start building with AllMyMeetings API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AllMyMeetings API for, with concrete tasks.

★ Agent Scheduling Across Calendars

An assistant agent can look up availability, detect conflicts, and create an event across a user's connected Google and Microsoft calendars through one JSON-RPC endpoint, without wiring each provider separately. Because the endpoint also exposes scheduling links and sync pairs, the agent can hand out a booking link or mirror an event between calendars in the same flow. This lets an agent own meeting scheduling end to end over a single integration.

Look up availability for a one-hour slot this week, detect conflicts, and create the event on the user's primary connected calendar.

Keeping Calendars in Sync

AllMyMeetings receives push notifications from Google Calendar and Microsoft Graph, so changes made in one place propagate without polling, and sync pairs mirror events between two calendars. An agent sets up a sync pair and then relies on the inbound webhooks to keep both sides current. This keeps a unified view of meetings accurate as events change at the source.

Create a sync pair between a work and a personal calendar so events created in one are mirrored to the other.

Offering a Booking Link

The endpoint exposes scheduling links so an agent can generate a shareable link that respects the user's real availability and conflict rules. A recipient books into an open slot, and the resulting event lands on the connected calendar. This gives an agent a self-service booking surface without building a scheduling page.

Generate a scheduling link for a 30-minute meeting that reflects the user's current availability and conflict rules.

Key Endpoints

6 endpoints — the allmymeetings api exposes calendar operations through a single authenticated json-rpc endpoint and keeps connected calendars in sync by receiving real-time change notifications from google calendar and microsoft graph.

METHOD

PATH

DESCRIPTION

POST

/mcp/calendar

Authenticated JSON-RPC calendar endpoint exposing calendar, sync, availability, and conflict tools

POST

/api/webhooks/google

Inbound Google Calendar push notification

POST

/api/webhooks/microsoft

Inbound Microsoft Graph change notification

POST

/api/webhooks/stripe

Inbound Stripe billing event

GET

/.well-known/mcp/server-card.json

Server card discovery document

GET

/.well-known/api-catalog

API catalog linkset

POST

/mcp/calendar

Authenticated JSON-RPC calendar endpoint exposing calendar, sync, availability, and conflict tools

POST

/api/webhooks/google

Inbound Google Calendar push notification

POST

/api/webhooks/microsoft

Inbound Microsoft Graph change notification

POST

/api/webhooks/stripe

Inbound Stripe billing event

GET

/.well-known/mcp/server-card.json

Server card discovery document

GET

/.well-known/api-catalog

API catalog linkset

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the AllMyMeetings API by hand means minting a Sanctum personal access token, sending it as a bearer token on the calendar endpoint, and leaving the inbound provider and billing webhooks open for the providers to call. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the calendar operations.

Permission scoping

A rule can allow your agent only the operations it needs: for example the public discovery reads without the authenticated calendar endpoint, or the calendar endpoint itself. The individual calendar tools travel as methods inside the JSON-RPC request body, so rules bound which endpoints the agent may call rather than which tool inside the calendar endpoint.

Credential isolation

Your AllMyMeetings Sanctum 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 'check availability and create an event' or 'set up a calendar sync pair', and Jentic returns the matching AllMyMeetings operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AllMyMeetings API through Jentic.

What authentication does the AllMyMeetings API use?

Per its OpenAPI spec the calendar JSON-RPC endpoint uses an HTTP bearer scheme carrying a Sanctum personal access token, which you mint at the settings API page and send in the Authorization header. The inbound provider and billing webhook endpoints and the well-known discovery documents are not gated by your token, since they are called by the providers or served publicly.

What calendar operations can I run with the AllMyMeetings API?

The JSON-RPC endpoint exposes calendar event management, sync-pair management, scheduling links, availability lookups, and conflict detection across connected Google and Microsoft accounts. You call these as methods on the single calendar endpoint rather than as separate REST paths.

What are the rate limits for the AllMyMeetings API?

The OpenAPI spec does not publish numeric rate limits for the AllMyMeetings API. For current limits check the vendor documentation at https://allmymeetings.com.

How do I schedule a meeting with the AllMyMeetings API through Jentic?

Import the AllMyMeetings API from the Jentic API Directory, then have your agent search by intent such as 'check availability and create an event' and Jentic returns the calendar endpoint with its input schema. The agent looks up availability, detects conflicts, and creates the event. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the AllMyMeetings API?

Yes. Write a rule that allows only the public discovery reads, so your agent can fetch the server card and API catalog but cannot touch your calendar, or allow the calendar endpoint when you want it to manage events. The specific calendar tool is named inside the JSON-RPC request body, so a rule governs which endpoints the agent may call, and every call it makes is logged.

Is there an AllMyMeetings MCP server?

Yes. AllMyMeetings is built around a Model Context Protocol server for calendar operations, and its discovery documents advertise a server card for MCP-aware clients. You can also connect it through Jentic: your token is injected at call time by your self-hosted instance instead of living in a client config, your rules decide which operations the agent may call, and connecting the next API is an import rather than another install.

Which calendar providers does the AllMyMeetings API support?

The spec shows inbound change notifications from Google Calendar and Microsoft Graph, so connected calendars on both providers stay in sync. Sync pairs then let you mirror events between two of the connected calendars.

AllMyMeetings API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCalendar Schedulingbearer6 EndpointsREST

For Agents

Manage calendars across Google and Microsoft accounts through one authenticated JSON-RPC endpoint: create and update events, manage sync pairs and scheduling links, look up availability, and detect conflicts. Provider webhooks keep connected calendars in sync.

Use for: Create a calendar event next Tuesday at 10am, Check my availability for a one-hour meeting this week, Set up a sync pair between my work and personal calendars, Generate a scheduling link for a 30-minute call

Not supported: Does not host video calls, send email, or transcribe meetings. Use for calendar operations, cross-provider sync, scheduling links, and availability only.

The AllMyMeetings API exposes calendar operations through a single authenticated JSON-RPC endpoint and keeps connected calendars in sync by receiving real-time change notifications from Google Calendar and Microsoft Graph. The JSON-RPC endpoint provides calendar event management, sync-pair management, scheduling links, availability lookups, and conflict detection, authenticated with a Sanctum personal access token. Inbound provider webhooks push calendar changes, a Stripe webhook handles billing events, and well-known discovery documents advertise the server card and an API catalog linkset. It is a hub for agents that need to read and manage calendars across Google and Microsoft accounts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

35%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

29%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AllMyMeetings API to your agent

Capabilities

Start building with AllMyMeetings API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AllMyMeetings API

Jentic AI Readiness Score

AllMyMeetings API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness