Build with Sidekin.

Make Sidekin work the way you do. Use its productivity building blocks with your own agent, frontend, and connected tools.

These are the public contracts available today. Read the agent index, fetch all documentation as text, or choose a reference below.

Initial public contracts · Reviewed September 28, 2026

Start with one project

The owner signs in to Sidekin and opens Calendars → Booking pages. Create or choose a page.
Open Advanced → Agent access and create a project token. Share it with the chosen agent through its secret configuration.
Connect that agent to https://app.sidekin.ai/project-mcp with a Bearer token. Discover tools with tools/list, then call project_get.
Edit through MCP, or clone the page’s hosted Git remote. Preview, commit, and publish when the owner wants the change live.

Follow the complete quickstart for a first edit, commit, preview, and publication.

A project token is scoped to one page. It grants source editing and publication access, including its scheduling configuration. Keep it out of public frontend code. Account access currently requires an invitation; the owner obtains and revokes tokens in Sidekin.

Public contracts

Calendar MCP: Owner-authorized private calendar reads, Google and iCloud source edits, exact previews, audit outcomes, and custom labels.
Projects, MCP, and Git: Authentication, tool calls, conflict handling, previews, publication, rollback, and one-time GitHub export.
Frontend and scheduling configuration: The sure.json format, availability, intake questions, themes, hosted assets, and the explicit private-day preview channel.
Booking RPC: Find times, book, inspect, reschedule, and cancel. Includes capability tokens, idempotency, and pending provider states.
Project MCP tool schemas: A machine-readable catalog generated from Sidekin’s implemented project operations. Authenticated tools/list is the live source of truth.

Choose the right interface

Calendar MCP is for the owner’s calendar agent. In Calendars → Agent connections → Manage calendar access, create a calendar token for https://mcp.sidekin.ai/mcp. It reads the owner’s connected sources; applying source edits needs both an editable token and separate provider-management permission. Read the calendar reference for the preview and apply workflow.

Project MCP and Git are for the owner’s frontend agent. They edit the same project source and history. Git pushes update the draft; publishing is separate. The normal Sidekin Publish button creates a commit for you when needed. Project and calendar MCP use separate credentials and tool catalogs.

Booking RPC is for the booker or their agent. Reading available slots and creating a booking require no owner login. Changing an existing booking requires its private management token. Availability reflects the owner’s published policy and connected calendars.

Use the right scope. External project MCP does not expose private calendar reads or source-event edits; use the separate owner-authorized calendar MCP for those. Account connections, concierge conversations, memory, worker control, and voice remain inside Sidekin. Public booking availability does not reveal event titles or attendees.

Current frontends are static HTML, CSS, and JavaScript with one scheduling offer per project. Hosted Git accepts fast-forward updates to main. Payments, team routing, and webhooks are not public contracts yet.

Use the contracts deliberately

Get the owner’s direction before publishing or changing scheduling policy, and the booker’s direction before booking, moving, or cancelling time. After a timeout, read the current state and reuse the same idempotency key for the same booking request. A pending operation is not a confirmed result.

For exact request bodies, errors, limits, and retry behavior, use the references above. For data handling, read Privacy & data use. Questions can go to founders@onepatch.dev.