Wato
Wato is the control point for AI agents at work — a governed, shared AI workspace that gives teams reviewed memory, approved MCP connectors and tools, versioned skills, cloud agent sessions, triggered automations, live artifacts and dashboards, and full tool-call tracing, all exposed to Claude Code, Codex, Cursor, and any MCP-compatible client through a single remote MCP gateway. Login, SSO, and directory sync are handled by WorkOS; agents only ever see a team's reviewed memory and approved tools, never raw credentials, and every MCP call is recorded as an auditable trace. Wato is a Y Combinator (Spring 2026) company based in San Francisco.
Wato publishes 1 API on the APIs.io network. Tagged areas include Company, MCP, Model Context Protocol, AI Agents, and Agent Governance.
Wato’s developer surface includes documentation, API reference, getting-started guide, quickstart, engineering blog, signup flow, pricing, and 14 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Wato MCP Gateway
Wato exposes each team's reviewed memory and approved connector tools through a single remote MCP (Model Context Protocol) gateway over Streamable HTTP with OAuth. Any MCP-capab...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
wato-mcp.yml
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Wato Plans
PLANSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API