Machine-readable access with explicit boundaries.

RemoteHands exposes a no-authentication API for discovering published hospitality and entertainment gigs in Bangkok. The canonical OpenAPI specification describes every operation, parameter, request body, response schema, and error response. Use searchPublicGigs to search, getPublicGig to read one sanitized listing, and createPublicGigLead only after the person has confirmed the exact submission and consented to contact. A lead is not an account, job application, confirmed booking, or guarantee of work.

The API health and discovery endpoint provides a small JSON response that identifies the public service and its canonical contract.

Read llms.txt for the product-level boundary and when an assistant should use RemoteHands. The worker agent guide explains public gig discovery and consented interest leads. The venue-manager agent guide explains authenticated setup, safe defaults, and consequential actions. HTML trust and developer pages also support Accept: text/markdown with cache-safe content negotiation.

The production MCP endpoint is /mcp. Its server card declares Streamable HTTP transport, tool names, and the existing RemoteHands bearer scopes: read, write, and confirm. These product-issued grants are not OAuth tokens. They are venue-scoped, revocable, environment-specific, and subject to RemoteHands ownership, verification, confirmation, and business-rule checks.

Public API and discovery endpoints return JSON errors with a stable code, a human-readable message or detail, and a recovery hint where it is useful. Clients should branch on HTTP status and error code rather than matching prose. A missing public API resource returns JSON 404; an unsupported method returns JSON 405 with an Allowheader; an unsupported negotiated representation returns JSON 406.