# Auth.md — Kusi Travel

## Human accounts and agent access

Human travellers can [sign in](/sign-in) or [sign up](/sign-up) through Kusi's Clerk account flow; availability follows the configured account access policy. Agent registration is unavailable. Kusi does not offer agent API keys or delegated OAuth registration. Its public-document MCP endpoint grants no private account access. Public reading requires no authentication and does not authorize access to a human account.

## Public content

The Peru guides, the About, How Kusi chooses and Developers pages, the Markdown overview, media credits and the discovery files under `/.well-known/` can be read without an account. Reading them does not create an account or grant access to anything else.

## Private content

Trips, saved places, profiles, documents and bookings belong to each traveller. A guest can search and start a plan without an account; that guest trip is tied to the browser it was made in. Everything kept on an account is only available to that traveller, and to the people they choose to share a trip with, after signing in to Kusi. Public pages never grant access to them.

## Consent

Booking, payment, cancellation and changes to sharing always need the traveller's explicit confirmation in Kusi. A public document, a partner link or a request from an AI assistant is never that confirmation. Never send passwords, tokens or personal information to these public documents.

## Contact

To work with Kusi as a partner, see [Kusi for partners and developers](/developers/).

## Agent registration and authentication

Audience: agents reading public Kusi information or helping a traveller use the website.
Public documents and the public-document MCP service require no registration or credentials.
They do not grant access to private traveller data.

For the application, the traveller opens Kusi and signs in using the existing Clerk interface.
An agent must not create an account, copy browser session tokens or request personal credentials
from the traveller. Kusi currently verifies Clerk browser session tokens for its private API;
OAuth access tokens, autonomous agent registration, agent API keys and delegated API scopes are
not supported by that API. No anonymous registration, verified-email assertion or ID-JAG
registration endpoint is offered. Agent credential claim and revocation endpoints are unavailable.
The traveller can manage their own browser sessions through the existing account interface.

The website's OAuth/OIDC discovery links refer to its existing Clerk identity provider. Staging
uses a separate test issuer from production. Identity-provider metadata does not grant a client
permission to access Kusi's private API. Do not exchange tokens or request OAuth scopes on the
assumption that private Kusi API access has been enabled. Kusi does not publish an `agent_auth`
registration block or OAuth Protected Resource Metadata until a supported delegated access
flow can be verified end to end.

Browser WebMCP tools are optional and read-only, in supporting browsers. On the planning pages,
editorial catalogue queries use the page's existing API and session boundary. On the guide, place
and planning pages, `listPeruGuides` and `readPeruGuide` list the published Peru guides and return
a guide's Markdown from content already published with the page, without any session. None of
these tools can edit plans, book, pay, cancel or publish. The remote MCP service is limited to the three public documents `/index.md`,
`/auth.md` and `/llms.txt`; it does not expose those browser tools or private application data.
