Sunshine Bay Rentals API & agent documentation

Discover Ontario cottages and Florida vacation rentals using the same public information shown to guests. This is a free, read-only catalogue. No account, API key, subscription or payment is required. You can try the live examples immediately; they have no booking side effects, so no separate sandbox is needed.

This catalogue does not provide live availability, prices, quotes or reservations. Check the linked Airbnb listing for current dates and terms, or use /book to select dates and prepare an email enquiry to the owner. An enquiry is not a confirmed booking.

REST API

• OpenAPI 3.1.1 specification: typed schemas, descriptions and unique operation IDs.
• GET /api/v1/properties: list all four properties.
• GET /api/v1/properties?region=Ontario&minGuests=7: filter by exact region and minimum guest capacity.
• GET /api/v1/properties/{slug}: retrieve a property from the list by slug.
• GET /api/v1/site: brand, owner contact information and booking limitations.

The optional region filter accepts Ontario or Florida, case-sensitive. minGuests must be an integer from 1 to 100. Unknown, repeated or invalid query parameters return HTTP 400. An unknown property returns HTTP 404. Data routes support GET and HEAD; writes return HTTP 405. Responses use application/json. Cross-origin reads are allowed. Cache catalogue responses for five minutes; no fixed application-level rate quota is configured, and hosting-level limits may apply. Use modest concurrency and back off on HTTP 429 or transient failures.

curl -sS 'https://sunshinebayrentals.com/api/v1/properties?region=Florida&minGuests=6'
curl -sS 'https://sunshinebayrentals.com/api/v1/properties/casa-pina-bonita'

Errors

REST errors follow RFC 9457 with Content-Type: application/problem+json. Fields include type, title, status, detail and instance, plus code, hint and docs. A missing resource uses code NOT_FOUND; invalid filters use INVALID_PARAMETER. Follow the hint to fix a request. Error responses are not cached.

curl -i 'https://sunshinebayrentals.com/api/v1/properties/not-a-property'

Markdown and discovery

The homepage and About, Contact, Privacy and Docs pages support Accept: text/markdown. HTML remains available with Accept: text/html. Negotiated responses include Vary: Accept and respect quality values. Unknown pages return real HTTP 404 responses; request Markdown for an agent-readable explanation and discovery links.

• llms.txt: agent orientation and resource links.
• Sitemap: canonical, indexable pages with modification dates.
• robots.txt: crawling and sitemap discovery.

curl -i -H 'Accept: text/markdown' 'https://sunshinebayrentals.com/'

MCP tools

Connect to https://sunshinebayrentals.com/api/mcp using MCP Streamable HTTP. The server is stateless, uses JSON responses, and negotiates protocol version 2025-11-25 (also supporting the SDK's 2025-06-18 and 2025-03-26 clients). It exposes list_properties, get_property and get_site_info. All three tools are read-only and require no credentials for this public catalogue. No guest or account information is accessible. The hosting platform reserves /mcp for its authenticated app connection. Public clients use /api/mcp, which serves only this same public catalogue.

Send initialization as a POST with Content-Type: application/json and Accept: application/json, text/event-stream. Send the negotiated MCP-Protocol-Version header on subsequent requests. Notifications receive an empty HTTP 202 response. Standalone GET streams and DELETE are not supported and return HTTP 405. Browser-origin requests must originate from the same site; ordinary server-to-server clients can omit Origin.

curl -sS 'https://sunshinebayrentals.com/api/mcp' -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"catalogue-example","version":"1.0.0"}}}'
curl -sS 'https://sunshinebayrentals.com/api/mcp' -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -H 'MCP-Protocol-Version: 2025-11-25' --data '{"jsonrpc":"2.0","method":"notifications/initialized"}'
curl -sS 'https://sunshinebayrentals.com/api/mcp' -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -H 'MCP-Protocol-Version: 2025-11-25' --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_properties","arguments":{"region":"Ontario"}}}'

The discovery descriptor is site-specific JSON linking to the actual MCP endpoint; it is not itself an MCP transport or an official MCP manifest standard. The protocol endpoint is /api/mcp. For an integration question, email hello@sunshinebayrentals.com.