Current status
See which public routes are supported or retired.
Current Wyatt API and developer access
Wyatt, the AI workspace for teams, documents its current API availability directly: legacy public resource routes are retired, supported app workflows use workspace-scoped APIs with public IDs, and external agents connect through MCP.
- Truthful API status
- Public IDs for supported workflows
- MCP for external agents
Legacy public resource routes are retired
The old public folder, PDF, database, document, and whiteboard contracts now return 410 Gone. Wyatt does not advertise those legacy numeric-ID routes as a supported developer platform.
Supported app workflows use public IDs
Wyatt’s current workspace-scoped clients and APIs use external public identifiers rather than internal database IDs. The status documentation points developers to current supported surfaces without inventing an unauthenticated public API.
External agents connect through MCP
For Codex, Claude, Cursor, ChatGPT, and other OAuth-capable clients, Wyatt’s remote MCP server is the supported public integration surface. It exposes scoped workspace tools through a discoverable protocol.
Check documentation before building
API availability can change during beta. Use the API status page and MCP reference as the source of truth instead of relying on copied endpoints or old resource examples.
Meet Wyatt
One connected workspace for docs, tasks, chat, and databases — with Wyatt answering from all of it.
Current statusPublic IDsAgent access
Hi, how can I help you?
“Ask a question, get an answer grounded in your team's actual work — then turn it into action.”
What you can do with Wyatt
Public IDs
Supported workspace workflows use public identifiers.
Agent access
Use the OAuth-scoped MCP server for external agents.
Documented
Developer availability is published without guessed endpoints.
Frequently asked questions
Is there a public Wyatt resource API?
The legacy public resource routes are retired and return 410 Gone. The docs publish the current status.
How should an external AI agent access Wyatt?
Use Wyatt’s OAuth-scoped remote MCP server and approve the workspaces and access level the client needs.
Do supported workflows expose internal database IDs?
No. Supported workspace URLs and client contracts use public IDs.
Where is the current source of truth?
Use the Wyatt API status page and MCP documentation before building an integration.