Create a self-service reader token for persistent saves, collections, and watchlists.

Returns a one-time reader bearer token. Hugging Bay stores only the token hash. Reader tokens cannot publish artifacts or approve mirrors.

Inputs. No path or query fields are required. The request body schema lists accepted fields and required values.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Token creation has separate visitor and IP budgets: 3 requests per 3600 seconds. Reuse an existing token; on 429 read Retry-After. A missing trusted client address can return 503 without creating a token.

Example setup. This example is not executed by documentation checks. Review the operation and obtain any required user consent before sending it.