Page unavailable? Copy its Markdown and paste it into your chat.
Your calendars. One connected layer.
Connect calendars, control access, and build on Ridian. Find the right path for the way you work.
Agent Mailbox: email for your AI agent
Section titled “Agent Mailbox: email for your AI agent”Give Claude, ChatGPT, Alvin or any MCP agent its own email address at ridianmail.com. One prompt creates the mailbox; your agent then receives, reads, drafts and sends email with the permissions you choose.
Quick start → · Use cases and prompts · Overview
Understand the building blocks
Section titled “Understand the building blocks”Connections bring your existing calendar accounts into Ridian. Sync keeps selected calendars aligned. Assistant access lets an authorized AI client read or act within your rules. Agent Mailbox gives your agents their own email addresses. Workspaces give teams a common policy boundary. Developer interfaces expose supported operations to applications.
Your calendar provider remains the home of your events. Ridian coordinates access and synchronization across those providers. You do not need to move your calendar to a new calendar application.
Start with a real outcome
Section titled “Start with a real outcome”- Connect your first calendar and check the calendars it exposes.
- Use ChatGPT or Claude with a deliberately small permission set.
- Give your agent an Agent Mailbox and send its first email.
- Set team boundaries before inviting colleagues.
- Explore the developer interfaces and their current scope.
Know what is available
Section titled “Know what is available”Capabilities differ by provider, permission and access channel. Check the capability guide before designing a workflow. Pilot features need a scoped setup; planned features are not available yet.