Graduated autonomy for AI scheduling agents

Let agents book for you, without handing them the calendar.

Agents and external requesters ask for time through Openavail. Calendar owners keep the rules, approvals, and audit trail.

Connect Calendar Integrate an agent

Private beta · Google Calendar supported today

Openavail booking approval showing a request from Codex MCP, three candidate times, and owner controls to approve, revise, or reject the proposal — Nothing reaches the connected calendar until the owner approves a candidate.

One path from request to calendar.

New agents begin with reviewable proposals. Owners can grant narrower direct-booking scopes later without bypassing policy or the audit trail.

Request

An agent sends the window, duration, attendees, and meeting class.

No calendar write

Review

Openavail curates candidate times and waits for the calendar owner to decide.

Owner decision

Write

An approved proposal becomes a calendar event through the owner's policy.

Controlled action

Record

The requester, rule, decision, and side effect are added to the audit trail.

Readable receipt

Run an Agent Test Flight to propose a time, approve the write, and inspect the receipt before issuing reusable access.

Test flight guide

Two ways to ask. One policy boundary.

The owner controls what each requester can see and whether the request needs review.

Agent API

Owner-authorized agents

Agents propose first, then gain narrower hold, booking, cancellation, or preemption permissions as trust grows.

Scoped API keys
Auditable decisions

Public links

External requesters

Published meeting types expose only the times and actions the owner permits for that requester.

Published meeting types
Review-first by default

The owner keeps four controls.

Openavail keeps access, authority, policy, and history visible in one control layer.

Connect Calendar

Calendar access

Choose which Google calendars and allocations are bookable.

Google Calendar · Bookable allocations

Requester authority

Separate requester identity from permission to change the calendar.

Agent scopes · Requester audiences

Scheduling policy

Rank, hold, reject, or preempt according to owner rules.

Meeting classes · Preemption policy

Decision history

Inspect outcomes and test policy before it affects real calendars.

Audit log · Simulator

Built for REST, SDK, and MCP workflows.

Agent keys act inside an owner account. Requester credentials prove identity without granting calendar authority.

REST APITypeScript SDKMCP server

sdk exampleQuickstart

const openavail = new OpenavailClient({
  apiKey: process.env.OPENAVAIL_API_KEY
});

const proposal = await openavail.createBookingProposal({
  ownerEmail: "[email protected]",
  title: "Customer demo",
  durationMinutes: 30,
  meetingClass: "customer_demo",
  requestedWindow: {
    start: "2026-06-25T09:00:00Z",
    end: "2026-06-25T17:00:00Z"
  },
  attendees: [{ email: "[email protected]" }]
});

// Owner reviews in Dashboard -> Approvals.
const latest = await openavail.getBookingProposal(
  proposal.proposalId
);

status: pending_owner_decision
proposal: bp_7F2kQ9
audit: dec_8XnPq7r3
next: owner approval