Changelog
Weverse public reads were previously forced to require an APIFuse Connection because the provider authenticates with credentials for its account and personalized operations. That over-gated genuinely public endpoints: the Weverse main API serves community, artist, member, post, comment, media, and shop-catalog reads anonymously using only the public web request signature. These operations now declare connectionMode: "none" and can be called without X-ApiFuse-Connection-Id.
No action is required. This operation previously rejected requests without X-ApiFuse-Connection-Id; it now accepts connection-less calls and serves the same public Weverse content. Existing callers that keep sending a connection id continue to work unchanged. Weverse operations that read the signed-in user's own state or account (connection-health, get-account-info, get-current-user, get-dm-user, get-jelly-balance, get-membership-benefits, get-my-membership, get-unseen-notification-count, get-user-settings, list-dm-subscriptions, list-showcased-rooms, shop-cart-count, shop-logout) still require a connection.