Install Jentic One Beta

Connect the Meetzi Booking Automation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meetzi Booking Automation 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%2Fmeetzi.co%2Fmeetzi" | 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%2Fmeetzi.co%2Fmeetzi" | 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 Meetzi Booking Automation API.

Confirm which Meetzi account an API key belongs to via GET /v1/me before running any automation

List the booking pages the key owner owns, with ids to filter later booking reads

Pull recent new bookings with guest_email, start_datetime, end_datetime, and meeting_option_url, optionally filtered by booking_page_id

Retrieve recently cancelled and rescheduled bookings to keep a CRM or calendar mirror in sync

GET STARTED

Start building with Meetzi Booking Automation API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Meetzi Booking Automation API for, with concrete tasks.

★ Agent-run booking follow-up through Jentic

An assistant agent watches Meetzi for fresh bookings and drafts a follow-up for each guest. Through Jentic it searches for 'list new Meetzi bookings', calls the new-bookings trigger with a booking_page_id, and reads guest_fullname, guest_email, and start_datetime from each record. The API key stays in your own Jentic One instance, so the agent only sees booking data, never the key.

Call GET /v1/booking-pages to find the id of the page named 'Discovery Call', then call GET /v1/triggers/new-bookings with that booking_page_id and limit 20, and return guest_fullname, guest_email, and start_datetime for each booking

Real-time booking webhooks

Instead of polling, an integration registers a webhook so Meetzi posts one booking object to a callback URL the moment a guest books, cancels, or reschedules. The subscription takes a required trigger_type and target_url, and an optional booking_page_id; leaving the page filter null covers every owned page, including pages created later. Deliveries carry no signature and are attempted once with no automatic retry, so the receiver should acknowledge quickly.

Call POST /v1/subscriptions with trigger_type 'booking_cancelled' and target_url 'https://example.com/webhooks/meetzi' and booking_page_id null, then store the returned subscription id

CRM sync for cancellations and reschedules

Sales teams keep their CRM accurate by reconciling changed meetings. The cancelled-bookings and updated-bookings triggers each return up to 500 recent records per call, so a nightly job can mark cancelled meetings as lost and move rescheduled ones to their new start time. There is no cursor or offset pagination, so the job reads the latest window rather than paging back through history.

Call GET /v1/triggers/cancelled-bookings with limit 100 and GET /v1/triggers/updated-bookings with limit 100, then list the booking_id and new start_datetime of each rescheduled booking alongside the cancelled booking ids

Integration health check

Before a scheduled automation runs, it can confirm the stored Meetzi key still works and points at the expected account. The identity endpoint returns the connected account, and a 401 response signals a missing, invalid, or revoked key, letting the automation stop early and alert the owner instead of silently missing bookings.

Call GET /v1/me and report the connected account identity, or report that the key was rejected if the response is 401

Key Endpoints

7 endpoints — the meetzi booking automation api exposes the booking pages a meetzi account owns and the bookings guests make on them.

METHOD

PATH

DESCRIPTION

GET

/v1/me

Get connection identity

GET

/v1/booking-pages

List owned booking pages

GET

/v1/triggers/new-bookings

List new bookings

GET

/v1/triggers/cancelled-bookings

List cancelled bookings

GET

/v1/triggers/updated-bookings

List rescheduled bookings

POST

/v1/subscriptions

Create webhook subscription

DELETE

/v1/subscriptions/{id}

Deactivate webhook subscription

GET

/v1/me

Get connection identity

GET

/v1/booking-pages

List owned booking pages

GET

/v1/triggers/new-bookings

List new bookings

GET

/v1/triggers/cancelled-bookings

List cancelled bookings

GET

/v1/triggers/updated-bookings

List rescheduled bookings

POST

/v1/subscriptions

Create webhook subscription

DELETE

/v1/subscriptions/{id}

Deactivate webhook subscription

Why Jentic?

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

Setup

Wiring Meetzi by hand means generating a key under Integrations, sending it as a bearer token on every /v1 call, and standing up a callback receiver for subscriptions that deliver once with no retry. Through Jentic you install once, import Meetzi from the API Directory, store the key once, and your agent calls it.

Permission scoping

Meetzi passes the booking page as a query or body field rather than in the URL path, so rules bound which operations your agent may call, not which booking page it reads. You choose the operations it may call, so webhook creation and subscription deactivation are not included unless you add them.

Credential isolation

Your Meetzi API 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 'list new bookings' or 'subscribe to cancelled meetings', and Jentic returns the matching Meetzi operation with its input schema, including booking_page_id and limit, so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Meetzi Booking Automation API through Jentic.

What authentication does the Meetzi Booking Automation API use?

Per its OpenAPI spec, the Meetzi API authenticates with HTTP bearer auth: you send a Meetzi API key, generated under Integrations then Zapier, in the Authorization header as a bearer token. The same key works for Zapier and custom server integrations. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

Can I get notified when a guest cancels a Meetzi booking?

Yes. POST /v1/subscriptions with trigger_type booking_cancelled and a target_url, and Meetzi posts the cancelled booking object to that URL. Set booking_page_id to one owned page, or leave it null to cover all owned pages. Deliveries are attempted once with no signature, and a 410 response from your receiver prompts Meetzi to deactivate the subscription.

What are the rate limits for the Meetzi Booking Automation API?

The OpenAPI spec states that no request quota or rate-limit headers are specified. The trigger endpoints accept a limit of up to 500 recent records per call with no cursor pagination. Check the Meetzi documentation at https://docs.meetzi.co for any current limits.

Is there a Meetzi MCP server?

You don't need an MCP server to give your agent Meetzi. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the booking operations it needs on demand without loading another server's tool definitions into its context.

How do I read new bookings for one booking page through Jentic?

Search Jentic for 'list new Meetzi bookings', load the GET /v1/triggers/new-bookings operation, and execute it with the booking_page_id from GET /v1/booking-pages and an optional limit. Each record returns the guest, the start and end time, and the meeting option. 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 Meetzi API?

Yes. Write a rule that allows only the three booking trigger reads and the booking-page list, and the agent can report on bookings without being able to register or deactivate webhooks. Every call it makes is logged, so you can review exactly which booking reads it ran.

Meetzi Booking Automation API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCalendar Schedulingbearer7 EndpointsREST

For Agents

Read new, cancelled, and rescheduled Meetzi bookings for the booking pages an account owns, and subscribe a webhook URL to booking events so an agent reacts as soon as a guest books or changes a meeting.

Use for: I need to see the bookings made on my Discovery Call page this week, List all booking pages on my Meetzi account, Check whether my Meetzi API key is still valid, Retrieve the meetings that guests cancelled recently

Not supported: Does not create, reschedule, or cancel bookings, manage availability, or edit booking pages. Use for reading Meetzi bookings and subscribing to booking events only.

The Meetzi Booking Automation API exposes the booking pages a Meetzi account owns and the bookings guests make on them. It returns recent new, cancelled, and rescheduled bookings with guest name and email, start and end times, duration, and the meeting option such as a Google Meet link, filtered by booking page. Webhook subscriptions push one booking event to a callback URL for the new_booking, booking_cancelled, or booking_updated trigger types. Every request authenticates with a Meetzi API key sent as a bearer token, and booking data is limited to pages owned by the key holder.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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).

75%

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: A-Signals: 4

13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: DSignals: 4

31%

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.

47%

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

80%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Meetzi Booking Automation API to your agent

Capabilities

Start building with Meetzi Booking Automation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Meetzi Booking Automation API

Jentic AI Readiness Score

Meetzi Booking Automation 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