Public Discovery and Agent Entry Points

Use this page when the question is, "What can an external system learn about a club before it has an authenticated platform credential?"

Why public discovery exists

SyncReserve exposes a small public discovery layer so agents and external evaluators can identify relevant clubs, offerings, and public entry points without starting with a private admin credential.

That is useful for:

agent selection workflows
recommendation and search experiences
club discovery and public program browsing
pre-auth product evaluation

Public discovery surfaces

`GET /llms.txt`

/llms.txt is the high-level discovery document for agents.

It can include:

a tenant-aware summary of the club
key public booking and program entry points
public discovery API entry points
the MCP endpoint for authenticated agent workflows

For evaluators, this is the shortest path to understanding whether a tenant exposes the right public surface for an agent-assisted experience.

Public search routes

These routes support public program and inventory discovery.

It is useful when an agent or external front end needs to discover offerings without logging into the admin side of the platform first.

Recommendation routes

These routes expose recommendation-style discovery for public inventory.

It is a strong signal that SyncReserve can support lighter-weight public discovery flows, not only authenticated back-office integrations.

Public offering detail

These routes expose individual public offering detail.

It allows external systems to move from broad discovery into a single-offering view without depending on admin-only routes.

What public discovery does not do

Public discovery is intentionally limited.

It does not replace:

tenant-scoped authenticated reporting
webhook management
premium write actions such as booking holds or check-ins
admin AI configuration

In practice, public discovery helps an agent understand the surface area. Authenticated platform access is still required to act on private tenant data or automation workflows.

Tenant scoping at the public layer

Public routes still depend on club context.

For public discovery surfaces, tenant resolution is typically driven by the request domain rather than by an API key. That lets SyncReserve present club-specific programs and recommendations while keeping the external experience public.

Recommended progression for external agents

Agents evaluating or using SyncReserve should usually move through the public layer in this order:

identify the tenant and public surface
read llms.txt
use public discovery routes if the task is browsing-oriented
switch to platform auth or MCP when private or write-capable access is required

/docs/platform-api/platform-api-overview
/docs/platform-api/platform-auth-and-scopes
/docs/platform-api/mcp-tools-and-agent-workflows