Root lives where your community works. It answers with the right context, operates your tools, and brings in a human when judgment matters.
Case study · FoundationsRoot was built by and is used every day inside the fndtns.org community. Foundations connected its member system, offices, and operating workflows, turning Root into the conversational front door for the entire community.
Explore Root at FoundationsRoot grants access in the building's system on the spot and triggers the registration invite to the member's email, so they can badge in before they arrive.
Root sees the member's session that afternoon, issues a full-day pass with a door PIN, and hands back the details ready to forward to the guest.
Root checks availability, books the right room, and sends the calendar invite — members reschedule or cancel by simply replying.
Root finds the open slot, books it on the member's behalf, and sends the invite; hosts manage their blocks the same way.
Members shape each office basket, Root matches real products, and admins can approve and submit the actual order.
Search members, companies, investors, and trusted service providers using structured community data.
Root's built-in action alerts watch Foundations tools and send the member a Slack DM when the event happens.
Members mint personal keys so their agents can use the same approved capabilities with their identity and permissions.
One agent across the work your team does every day
These capabilities are native to Root—not custom integrations. Every workspace starts with the channels, knowledge, memory, access controls, follow-through, and human safety net an agent needs.
Ground responses in managed knowledge pages, synced URLs, and attributed guidance shared by your community.
Semantically search indexed Slack discussions and inspect the people, replies, and reactions around a conversation.
Use live web research when freshness matters, while keeping your own knowledge as the primary source of truth.
Retain user preferences, schedule reminders, and trigger alerts the moment a matching action happens.
Operate in Slack, email, web chat, and APIs with resolved identity, access tiers, and one auditable history.
When judgment is needed, open a tracked intervention with the request, member, and conversation context assembled.
Root sits between your community and the systems behind it—translating everyday requests into safe, auditable work.
Members reach Root through the channel that is natural to them.
Root resolves identity, retrieves the right knowledge, selects approved tools, and explains the result.
Connected tools complete the job—or a human gets a clear request to finish it.
Set the boundary. Root resolves routine work on its own and creates a structured handoff when a request needs approval, empathy, or judgment.
Root owns the hard agent infrastructure. Your integration supplies the community-specific data and actions. Together, they become one permission-aware tool surface.
Maintained once and available to every community.
Declare tools from the systems that make your community unique.
Integration protocolExpose signed, tenant-scoped tools with descriptions, schemas, permissions, and channel rules.REST APIRun agent turns, send messages, resolve identity, and manage integrations from your own product.MCP serverLet members use Root and its approved tools from Claude, Cursor, or another MCP client.Core + extensionRoot decides which approved tool fits the request, enforces the user's access, executes it, and carries the result back to the original channel.
Start with Root's built-in agent platform. Then connect the tools that make your community yours—and turn conversation into the work only your systems can do.
Get started with Root