Notable changes to the public API. The version is surfaced as info.version in the OpenRPC and OpenAPI documents.

1.1.0 — Public albums and independent photo access

• Existing photos and API uploads remain public by default. Upload metadata accepts visibility: "private" or "public"; the cabinet explicitly sends private for new uploads.
• image.setVisibility manages independent access. image.getPublic keeps its flat response, existing field names and generated render URLs. Private photos are accessible through an explicitly published album; public API photos remain accessible when an album is hidden or its share link is reset.
• Public metadata follows both photo and album settings. Album pages omit owner identifiers, original URLs and raw EXIF. The legacy standalone API retains its dimensions, file sizes, upload date and RFC3339 capture date for compatibility.
• Owner sharing, covers and previews require an interactive session. PATs can continue uploading, moving photos and setting photo access or EXIF visibility. Public read routes share hit and miss budgets (4002 rate_limited).
• Album publication remains behind its server switch until release gates pass. This switch does not revoke independent access to public photos.

1.0.0

• Initial documented surface: auth.*, image.*, account.*, token.*, and the rpc.discover service-discovery method.
• Machine-readable documents published: OpenRPC (/openrpc.json, also returned by rpc.discover), an OpenAPI 3.1 wrapper (/openapi.json) with a POST /rpc/{method} alias per method, and a Postman collection.
• Cursor pagination on image.list; personal access tokens scoped to image.*; per-image EXIF visibility toggles; up to five custom crops per image.