# auth.md — BrowserTones authentication and authority

The free browser player, public product facts, published sound catalog, MCP
sound tools and deterministic A2A interface currently support anonymous use.
No account registration, password, API key or OAuth token is required.

## Connecting

- MCP: POST JSON-RPC with `Content-Type: application/json` and the MCP client's
  required Accept header to `https://browsertones.com/api/mcp`. Initialize,
  list tools and use only the capabilities actually listed by that connection.
- A2A: read `/.well-known/agent-card.json`. The current binding is A2A 1.0
  JSON-RPC `SendMessage` at `/api/a2a`, with structured JSON operations as
  documented at `/developers` and `/openapi.json`. No retained tasks or model
  interpretation are provided by this adapter.
- Public reads: GET `/api/agent-facts` and `/guitar-sounds.json`.

## Existing private sound conversation

When MCP lists `start_tone_conversation`, its returned opaque conversation
reference is a temporary capability for that sound conversation only. It is
not a user identity, OAuth credential or permission to access owner data.
The conversation expires within 15 minutes. Follow the returned expiry and
version, keep its private reference out of URLs and public text, and do not
claim a conversation can be recovered after expiry. Follow the actual tool
schemas for refinement and exact-result feedback.

## Limits and decisions

Respect 429/503 responses and Retry-After; do not bypass a limit with new
identities or repeated uncertain calls. The optional model conversation has
its existing daily cost and session limits; deterministic compose/refine does
not invoke a model. Opening a trial link loads settings. The user starts
audio and microphone access. Public snapshot creation requires the user's
separate choice. No interface here grants purchases, account administration,
private history or remote device access.

BrowserTones does not currently operate an OAuth authorization server or an
OAuth protected-resource service. OAuth discovery endpoints are intentionally
not advertised. A future delegated private-resource flow needs a real
resource owner, explicit scoped consent, short token lifetime, single-use
authorization codes, PKCE, audience binding and revocation before activation.

Current canonical connection instructions: https://browsertones.com/developers
Publisher and privacy contact: hello@fukkaudio.com
