Owner-authorized agents
Trusted agents propose first, then can hold, book, cancel, or preempt only through owner-granted permissions.
- API keys act inside the owner account
- Permission scopes narrow each action
- Every decision is auditable
Graduated autonomy for AI scheduling agents
Let agents book for you, without handing them the calendar.
Agents, scripts, and external requesters can ask for time through Openavail. Calendar owners keep the rules, approval flow, requester visibility, and audit trail.
Decision workbench
Tue 09:00, [email protected]
sales-agent
Customer demo
proposal
partner-script
Office hours
public request
exec-agent
Board prep
direct
Receipt
Every requester passes through owner policy.
- Mode
- policy-first
- Audit
- dec_8XnPq7r3
Before any write, the request becomes a decision.
Openavail turns an agent ask into a reviewable proposal, then records the policy receipt once the owner decides.
01
Proposal created
The agent sends the window, duration, attendees, and meeting class.
No calendar write
02
Owner approves
Openavail shows the candidate times and waits for a scoped owner decision.
Approval required
03
Receipt recorded
The decision, rule, requester, and side effect are written to the audit trail.
Readable receipt
Two request channels. One owner policy.
Whether the ask comes from an agent, workflow, partner script, or public link, owner policy stays between the request and the calendar write.
External requesters
External requesters ask for time through published meeting types; owner policy decides what needs review and what can auto-book.
- Public meeting types expose only what is published
- Requester credentials prove identity, not authority
- Anonymous requests stay review-first
Calendar providers store events. They do not decide agent autonomy.
Direct calendar access is too much for new agents and too little governance for trusted ones. Openavail gives you the steps between.
Agents need a safe first step
A new assistant should be able to find good times without immediately writing to the calendar.
Requesters are not all the same
A requester may be an agent, a script, a workflow, or a human on a public link. They still need owner policy between them and the calendar.
Humans still need the reason
When a meeting lands, the owner needs to know which agent asked, what rule answered, and what changed.
Start with proposals. Promote only what earns trust.
Openavail turns scheduling into a sequence that can begin with human approval and graduate toward direct execution.
Propose
Agents and requester-side workflows create proposals with requested window, duration, attendees, and meeting class.
No calendar write
Review
Openavail ranks candidates and sends the proposal to the dashboard for the calendar owner to approve, reject, or ask for a new window.
Owner decision
Grant
Once an agent earns trust, give it narrower direct-booking scopes: search, hold, confirm, or preempt only when rules allow.
Earned autonomy
Audit
Every proposal, approval, hold, booking, rejection, and preemption leaves a decision record humans can inspect.
Readable receipt
Before production keys
Run a guided Agent Test Flight to watch a test agent propose a time, approve the calendar write yourself, and inspect the receipt before giving a real agent reusable access.
Permission scopes are the controls. Proposals are the on-ramp.
The dashboard keeps calendar owners in charge of proposals, public links, rules, keys, requester audiences, permissions, and decision history.
Calendar access
Connect the calendar and decide what is bookable before any agent can write.
Google CalendarBookable allocationsOwner scopes
Request channels
Separate who is asking for time from who has authority to create the event.
Agent API keysPublic linksMeeting typesRequester audiences
Policy decisions
Rank, hold, reject, or preempt based on owner rules and meeting priority.
Approval queueBooking proposalsMeeting classesPreemption policy
Review trail
Inspect what happened and test policy changes before they affect real calendars.
Audit logSimulatorVerified domains
Built for REST, SDK, and MCP workflows.
Owner-agent API keys act inside the owner's account. Requester credentials prove external identity for public scheduling. Both paths keep calendar authority with the owner.
REST APITypeScript SDKMCP serverRequester credentials
sdk exampleRead docs
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
);returnspolicy receipt
- status
- pending_owner_decision
- proposal
- bp_7F2kQ9
- audit
- dec_8XnPq7r3
- next
- owner approval
Pricing you can understand before you click.
Start free with one calendar. Upgrade when you need more agents, more calendars, or longer audit history.
Free
$0forever free
1 agent, 1 calendar, 50 bookings each month.
Start freePro
$20per month
5 agents, 5 calendars, simulator, drift detection.
Get ProTeam
$70per month
Unlimited agents, 10 owners, 365 day audit retention.
Get TeamQuestions before you connect.
A few answers about proposals, direct booking, providers, and what Openavail is not.
Is Openavail becoming a scheduling-link app?
No. Public links are one request channel inside the same control layer. Openavail is still focused on governed calendar access for agents, scripts, workflows, and other requesters.
What is a booking proposal?
A proposal is an approval-first scheduling request. The agent asks for a meeting window, Openavail finds candidates, and the owner decides before anything is written.
Which calendar provider works today?
The current product supports Google sign-in and Google calendar connection. Microsoft 365 is roadmap.
Can trusted agents book directly?
Yes. You can grant direct booking scopes later. Those agents still pass through owner rules, meeting class priority, idempotency, and audit logging.
What does a requester credential do?
It proves external requester identity for public scheduling. It does not grant calendar authority; the target owner still controls visibility, review, and auto-book behavior.
Let the next agent booking start as a proposal.
Connect Google Calendar, register an agent, publish public links, and grant autonomy one permission at a time.