Guesty caps you at five access tokens per client ID per 24 hours, and each token lasts 24 hours. That one limit decides your architecture: anything that mints a token per process start, per agent session, or per serverless invocation exhausts the budget within hours. Guesty also ships an official MCP server in early beta, read-only during beta, so if you want conversational access rather than a built tool, start there.
The token limit that decides your architecture
Guesty authenticates with OAuth client credentials, and the constraint that matters is not the auth flow but the quota. Guesty allows only five access tokens per client ID per 24 hours, and each issued token remains valid for 24 hours.
This breaks the most natural way to write an integration. An MCP server starts fresh every time the assistant launches; a serverless function may cold-start dozens of times an hour; an agent that re-authenticates per session burns a token each time. Five of any of those and you are locked out until the window rolls. The fix is to mint once and cache the token for its full life, which is exactly what the gateway does centrally so nothing in your code has to.
Their official MCP server is in early beta and read-only during that period, available locally through the Guesty SDK or hosted. For asking questions in an assistant, use it. For a tool that runs unattended, you want the API and the token caching.
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 Guesty 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 Guesty
Because Guesty 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/guesty/reservations \
-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
- Guesty Open API Documentation, Guestyhttps://open-api-docs.guesty.com/