For Agents
Read cross-person busy and free availability, find mutual open windows, and propose a meeting time without exposing event details. Authenticates with a bearer API key.
Use for: Find a time when everyone on the team is free, Get the busy blocks for a group this week, Check a person's availability summary for today, List the people I can see availability for
Not supported: Does not expose event titles, attendees, or private calendar contents, and does not send email or video invites. Use for reading cross-person availability and proposing meeting times only.
The BusyBoard API exposes cross-person busy and free availability while keeping the underlying event details private. You read the people and groups you can see, pull busy blocks for a set of users over a date range, and get a rolled-up availability summary. A find-time operation returns mutual free windows for a group, and a booking-proposals operation proposes a meeting time against that availability.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BusyBoard 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%2Fbusyboard.app%2Fbusyboard" | 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%2Fbusyboard.app%2Fbusyboard" | 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 BusyBoard API.
Read the people and groups an account can access
Pull busy blocks for a set of users over a date range
Get a rolled-up availability summary for a date and range
Find mutual free windows across several people
Propose a meeting time against shared availability
Patterns agents use BusyBoard API for, with concrete tasks.
★ Agent Meeting Scheduling
An AI agent connected through Jentic reads a group's availability, finds a mutual free window, and proposes a meeting time, so scheduling happens without exposing anyone's private event details. Because BusyBoard returns only busy and free blocks, the agent can plan a time while event contents stay private.
Find a 30-minute window next week when all five people are free and propose that time
Team Availability Overview
An assistant pulls busy blocks for a set of users across a date range and renders a shared availability view, so a planner sees who is free when without opening each calendar. The summary operation condenses a day or range into a single readable picture.
Get busy blocks for the project group from Monday to Friday and summarize each person's free hours
Privacy-Preserving Free/Busy Lookup
An integration reads free and busy data for external and internal participants without accessing event titles or attendees, so scheduling respects privacy boundaries. The people and groups operations scope which availability a caller is allowed to see.
Read the availability summary for the two named people today and return only their free windows
9 endpoints — the busyboard api exposes cross-person busy and free availability while keeping the underlying event details private.
METHOD
PATH
DESCRIPTION
/me
Get the current user profile
/people
List accessible people
/availability
Get busy blocks for users
/availability/summary
Get a rolled-up availability summary
/find-time
Find mutual free time for a group
/calendars
List connected calendar accounts
/booking-proposals
Propose a meeting time
/me
Get the current user profile
/people
List accessible people
/availability
Get busy blocks for users
/availability/summary
Get a rolled-up availability summary
/find-time
Find mutual free time for a group
/calendars
List connected calendar accounts
/booking-proposals
Propose a meeting time
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BusyBoard API by hand means handling its bearer key auth, passing user id and date-range parameters correctly, and combining the availability and find-time operations. Through Jentic you install once, import BusyBoard from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which operations your agent may call, so you can allow the read-availability and find-time operations and leave the booking-proposal operation out. The user ids and dates travel as parameters, so rules bound which operations run rather than which people are queried.
Credential isolation
Your BusyBoard 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 mutual free time' or 'get a group's busy blocks', and Jentic returns the matching BusyBoard 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 BusyBoard API through Jentic.
Is there a BusyBoard MCP server?
You don't need an MCP server to give your agent the BusyBoard API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can read availability and find free times 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 BusyBoard API?
Yes. You choose which operations your agent may call, so you can allow reading availability and finding mutual times while leaving the meeting-proposal operation out, and every call it makes is logged. That keeps a read-only scheduling agent from proposing meetings on its own.
What authentication does the BusyBoard API use?
The BusyBoard API authenticates with a bearer API key sent in the Authorization header per its OpenAPI spec, and a share link can also serve the same availability data without a key. Through Jentic the key is stored encrypted by your own instance and added to each request at call time.
Can I find a time that works for a whole group with the BusyBoard API?
Yes. The find-time operation returns mutual free windows across several people for a date range and a requested duration, so an agent can hand back a slot that works for everyone without reading each person's calendar.
What are the rate limits for the BusyBoard API?
The OpenAPI spec does not specify rate limits for the BusyBoard API. For current limits, see the BusyBoard documentation at https://busyboard.app.
How do I find a meeting time with the BusyBoard API through Jentic?
Import the BusyBoard API from the Jentic API Directory, then have your agent issue a request such as 'find a free time for this group next week'. Jentic matches the intent to the find-time operation and returns its input schema so the agent builds a valid request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED