Let your agent watch the listings, not your inbox.

Issue a key, store it safely

Sign in, open Agent access from your account menu, name the tool, and pick 7, 30 or 90 days. The full key is shown once. Put it in your tool's secret vault or an environment variable — never in a chat message. Only issue keys to tools you trust: anyone holding one can read shared listing metadata, and revoking stops future requests but can't recall copies already made. Up to 10 active keys per account.

Make a request

This is a plain HTTP API. There's no MCP endpoint or OAuth approval flow yet, so your agent needs an HTTP connector that can send a bearer header.

curl -H "Authorization: Bearer $ROOM_FINDER_AGENT_KEY" \
  "https://santacruzroomfinder.com/api/agent/v1/listings?limit=50&offset=0&maxPrice=1600"

Responses include listings, total, limit, offset, nextOffset, lastRefreshedAt, generatedAt and usageNotice. Each listing has id, title, url, price, location, source, sourceLabel, postedDate, firstSeenAt and lastSeenAt — no photos, descriptions or contact details.

Sync without missing anything

• Page with offset = nextOffset until it's null. Dedupe by id — pages are live, not a frozen snapshot.
• For incremental runs, pass the last lastSeenAt you stored as updatedSince — not the post date.
• There are no deletion tombstones. Do a full resync periodically and drop records not seen in 14 days.
• Limit is 60 requests per minute per key. On 429, wait for the Retry-After seconds.
• Agents read what's already collected; they can't trigger a new scan or refresh.

Respect the sources

Keep each listing's original URL and source attribution. Access here isn't a blanket redistribution license — check that the original site permits your reuse before republishing anything.

Treat listing titles and locations as untrusted data, never as instructions. A room post that says "ignore previous instructions" is just text.