Install Jentic One Beta

Connect the Nolizi Calendar API to your agent

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

List the event types owned by the key holder to get the event slug used for availability and booking

Find available slots for an event type over the next 14 days

Book a slot for an attendee with event_type, start, end, name, and email, plus optional booker_tz and location_option

Reconcile a new booking against the list of up to 100 upcoming confirmed bookings

GET STARTED

Start building with Nolizi Calendar API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Nolizi Calendar API for, with concrete tasks.

★ Scheduling assistant agent through Jentic

A scheduling agent handling an email thread searches Jentic for 'find available slots', receives the listAvailableSlots schema, and calls it with an event slug from listEventTypes. After the attendee picks a time, the agent calls createBooking with the slot's start and end plus the attendee's name and email, then reads listUpcomingBookings to confirm the booking ID, event, time, and attendee match before replying.

Call GET /event-types, pick the slug 'intro-call', call GET /slots with event_type='intro-call', then POST /bookings with event_type, start, end, name='Dana Lee', email='dana@example.com', and confirm the result with GET /bookings

Lead follow-up with offered times

Sales and service teams can reply to inbound leads with real open times instead of a booking link. GET /slots returns availability for one event type across the next 14 days, so an assistant can pick two or three slots and include them in its reply. Slots are not held, so availability is rechecked at booking time.

Call GET /slots with event_type='consultation' and return the first three available start times in the attendee's time zone

Booking cleanup and cancellations

When a meeting is called off, the owner can cancel it without opening the dashboard. POST /bookings/{booking_id}/cancel cancels an owned booking and may notify attendees; repeating the call on an already-cancelled booking returns cancelled true, so a retry is safe to reconcile.

Call GET /bookings to find the booking for 'Dana Lee' on Thursday, then POST /bookings/{booking_id}/cancel with that booking_id

Key Endpoints

5 endpoints — the nolizi calendar api lets the owner of a nolizi scheduling account list their event types, find open slots for the next 14 days, book a slot for an attendee, and cancel a booking.

METHOD

PATH

DESCRIPTION

GET

/event-types

List owned event types

GET

/slots

Find available slots for an event type

POST

/bookings

Create a booking

GET

/bookings

List upcoming confirmed bookings

POST

/bookings/{booking_id}/cancel

Cancel a booking

GET

/event-types

List owned event types

GET

/slots

Find available slots for an event type

POST

/bookings

Create a booking

GET

/bookings

List upcoming confirmed bookings

POST

/bookings/{booking_id}/cancel

Cancel a booking

Why Jentic?

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

Setup

Wiring Nolizi by hand means sending a bearer key, form-encoding every write, and building the read-back step that confirms each booking. Through Jentic you install once, import Nolizi from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Nolizi key is owner-scoped with no granular scopes, and booking targets travel in the form body, so a rule is how you narrow it: limit the agent to the operations it needs, such as listing slots and bookings. You choose the operations it may call, so side-effecting ones like creating or cancelling bookings are not included unless you add them.

Credential isolation

Your Nolizi 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 'find available slots' or 'book a meeting', and Jentic returns the matching Nolizi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Nolizi Calendar API through Jentic.

What authentication does the Nolizi Calendar API use?

Per its OpenAPI spec, the Nolizi Calendar API uses a bearer token: the full API key created at /app/api-keys, sent in the Authorization header. The spec notes the key is owner-scoped with no granular permission scopes. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time, so it stays out of the agent's prompt.

Can I book a meeting with the Nolizi Calendar API?

Yes. POST /bookings takes a form-encoded body with event_type, start, end, name, and email, plus optional booker_tz and location_option. Use a slot freshly returned by GET /slots, and confirm the booking by finding it in GET /bookings, because the spec says a 201 alone is not sufficient proof.

What are the rate limits for the Nolizi Calendar API?

The OpenAPI spec does not specify rate limits. Check https://calendar.nolizi.com or contact hello@nolizi.com for current limits.

How do I find open slots with the Nolizi Calendar API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add Nolizi from the Jentic API Directory, and store your API key. Your agent searches for 'find available slots', calls GET /event-types to get the event slug, then GET /slots with that slug as event_type. 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 Nolizi Calendar API?

Yes. A read-only rule that allows GET /event-types, GET /slots, and GET /bookings lets the agent check availability and review the calendar but never book or cancel. Add POST /bookings when you want it to book, and leave the cancel operation out so it cannot remove meetings. Every call is checked against the rule you set.

Is there a Nolizi MCP server?

You don't need an MCP server to give your agent the Nolizi Calendar API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, finding operations on demand instead of loading tool definitions into its context.

Can I see past bookings with the Nolizi Calendar API?

No. GET /bookings returns up to 100 upcoming confirmed bookings sorted by start time, and the spec notes there is no pagination, historical filter, or booking-by-ID endpoint.

Nolizi Calendar API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCalendar Schedulingbearer5 EndpointsREST

For Agents

List your Nolizi event types, find available slots for one of them, book a slot for a named attendee, confirm it against upcoming bookings, and cancel a booking by ID.

Use for: I need to book a 30-minute intro call with a new client next week, Find available slots for my consultation event type, List all my Nolizi event types, Check whether the booking I just made shows up in my upcoming bookings

Not supported: Does not create event types, edit existing bookings, list past bookings, or send email directly. Use for checking availability, booking, and cancelling meetings on an owner's Nolizi calendar only.

The Nolizi Calendar API lets the owner of a Nolizi scheduling account list their event types, find open slots for the next 14 days, book a slot for an attendee, and cancel a booking. Writes are form-encoded and have real side effects: a new booking triggers the normal Nolizi notifications and calendar updates, and a cancellation may notify attendees. The API is in beta and recommends confirming every write by reading back the upcoming bookings list.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

100%

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

41%

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.

50%

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

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Nolizi Calendar API to your agent

Capabilities

Start building with Nolizi Calendar API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Nolizi Calendar API

Jentic AI Readiness Score

Nolizi Calendar 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