Guardian · Platform
Platform
One authority model for every consequential action an agent can take, starting with email and growing domain by domain.
Universal action model
Every domain, one authority system
Guardian names each consequential action the same way regardless of provider, so a new domain is an adapter, not a new product.
| Area | Status | What Guardian governs | Example actions |
|---|---|---|---|
| Communication | Verified · GmailSending email from a connected Gmail account is live and proven. Forwarding, messaging and social posting are planned. | Email, messages and social posts an agent sends in your name. | email.send · email.forward · message.send · social.publish |
| Calendar and commitments | PlannedPlanned. Not available today. | Meetings, reservations and cancellations made for you. | calendar.create · calendar.cancel · reservation.create |
| Commerce and purchases | PlannedPlanned. Guardian does not approve purchases today. | Buying, returning and subscribing. | commerce.purchase · commerce.return · subscription.create |
| Payments and budgets | PlannedPlanned. Guardian does not move money today. | Payments, bills, transfers and spending limits. | payment.send · bill.pay · transfer.create |
| Protected data | PlannedPlanned. Not available today. | Addresses, IDs and other personal information — whether an agent may use, see, keep or share it. | protected_data.use · protected_data.view · protected_data.disclose |
| Files | PlannedPlanned. Not available today. | Reading, writing, sharing and deleting documents. | file.read · file.share · file.delete |
| Tools and MCP | In developmentGuardian’s email actions are exposed as MCP tools today; governing which tools an agent may install or enable is planned. | Which tools, plugins and connectors an agent may call or add. | tool.invoke · mcp.install · connector.add · oauth.scope.expand |
| Memory and agent configuration | PlannedPlanned. Not available today. | What an agent remembers and how it is configured. | memory.write · memory.delete · model.change · agent.configure |
| Delegation and sub-agents | PlannedPlanned. Not available today. | Agents that start other agents and hand them work. | agent.spawn · agent.delegate · agent.subdelegate |
| Developer and infrastructure actions | PlannedPlanned. Not available today. | Code pushes, merges, deployments and cloud changes made by coding agents. | git.push · git.merge · cloud.deploy · cloud.delete |
| Device and runtime authority | PlannedPlanned. Not available today. | Which devices and runtimes an agent may act from. | runtime.change · trusted_device.add · network.egress |
Authority map
Authority you can see
You sit at the center. Agents act around you; the services they can reach sit beyond them. Authority may narrow as it passes to a helper. It can never grow.
Two interfaces, one authority state
Web for control. Phone for decisions.
- Live · responsive web
Guardian Web
Onboarding, agents, connected services, approvals and evidence history at guardian.odingard.com, usable on a phone browser today.
- Planned
Guardian Mobile
An installable app for immediate decisions: pending asks, passkey step-up, receipts and an always-reachable Pause All Agents.
Beyond email
Email is the first proven surface, not the whole product
The same authority model is designed for every consequential action an agent can take. Each area below shows its status.
Communication
Verified · GmailSending email from a connected Gmail account is live and proven. Forwarding, messaging and social posting are planned.
- What Guardian would govern
- Email, messages and social posts an agent sends in your name.
- Why authorization matters
- A message sent as you can’t be unsent, and it carries your reputation.
- Example
- “Your assistant may send the weekly update to your team, but must ask before writing to anyone new.”
- Actions
- email.send · email.forward · message.send · social.publish
Verified · GmailIn developmentPlanned
One Guardian
One authority model, several ways to use it
Every experience runs on the same Guardian authority system. No pricing is published while Guardian is in pilot.
- Pilot · Gmail
Guardian Personal
Your own authority controls for the agents you use, beginning with protected Gmail sending. Open to invited pilot users while Google verification of the Gmail connection is completed.
Request pilot access → - Planned
Guardian Family
Shared household authority: who in the family can let which agent do what, and who approves.
Register interest → - Early access
Guardian Developer
Put your agent behind Guardian through its agent API today; SDKs and broader MCP support are planned.
Explore developer access → - Design partners
Guardian Embedded
Guardian-backed authority inside assistants, banks, merchants and other platforms — the same security model, under your product.
Discuss a design partnership →
Get started
Let AI act for you without letting it become you.
Individuals
Use Guardian with your own agents
Guardian Personal is in pilot. Gmail connection is open to invited pilot users while Google completes verification.
Developers
Put your agent behind Guardian
Register an agent, swap its mailbox token for a Guardian credential, and call the agent API.
Organizations
Embed Guardian or become a design partner
For assistants, banks, commerce providers and platforms that want their users’ agents to act under real authority.
Odingard Security · Trust infrastructure for autonomous systems