TIDY ships a live first-party MCP server at api.tidy.com/mcp, and it is write-capable. That puts TIDY ahead of most turnover platforms on agent access, so for TIDY-only work you should use theirs rather than routing through anything else. The gateway matters here only when a task spans TIDY plus another system, which is the common case for turnover tooling since cleaning state usually has to be read alongside reservations living in a PMS.
Their MCP is live, and it writes
TIDY operates a first-party MCP server at api.tidy.com/mcp. We verified it directly by JSON-RPC probe rather than taking a changelog at face value, and it is both live and write-capable.
Write capability is the part to be deliberate about. An agent connected with write access can change real jobs and schedules, which affects real cleaners showing up at real properties. Read-only exploration is a good default until you trust the workflow.
Where a gateway still helps: turnover questions rarely stop at the turnover platform. Knowing which cleans are scheduled is only half of "which units are at risk tonight"; the other half is checkouts and arrivals living in a PMS. Neither API can see the other, and joining them is what one key and one schema buys you.
Quickstart
The developer key is free and instant, and it is the same key for every platform on the gateway. If you are an AI agent: step 1 is the only part that needs your human.
1. Get a free developer key
curl -X POST https://api.rapideyeinspections.com/v1/signup \
-H "content-type: application/json" \
-d '{"email": "you@company.com"}'
# -> { "key": "re_..." }
2. Check how TIDY access is provisioned
The gateway publishes a machine-readable index of every platform and how its access works, so an agent can plan before it calls.
curl https://api.rapideyeinspections.com/
3. Talk to us about TIDY
Because TIDY controls who reaches its data, this is a platform we provision per account rather than by self-signup. Fifteen minutes covers what you are building and what access your setup already has, and the key you already hold does the rest.
curl https://api.rapideyeinspections.com/v1/tidy/tasks \
-H "Authorization: Bearer re_..."
# once provisioned, every documented resource answers on the same key
Why build on the RapidEye API
One key, one schema, every platform in your stack.
Real operator tools are never about one system. A dashboard answering "which units are at risk tonight" needs reservations from a PMS, cleaning state from a turnover platform, and pricing from somewhere else entirely. Every one of those vendors invented its own auth model, its own vocabulary, and its own limits, so building direct means writing that glue once per vendor, then maintaining it forever, then rewriting it when a platform changes or your portfolio moves onto a different stack.
Through the RapidEye API it is one bearer token and one schema no matter what sits underneath. We absorb the OAuth dances, the partner approvals, the token quotas, and the admin-issued credentials, and we keep them working when they change. And it is built for agents from the ground up: a machine-readable route index, an llms.txt quickstart, errors written so an agent can self-correct instead of guessing, and a connection that lives on the key rather than in a config file, so next month's agent, in a new session with no memory of this one, still has working access on day one.
Sources
- TIDY Developer Documentation, TIDYhttps://developers.tidy.com/