Authenticate
AT Protocol OAuth identifies the DID controlled by the participant. The browser SDK handles PKCE, DPoP, callback processing, and session storage.
AT Protocol · creator-controlled
Made Sick does not create a separate password account. You authenticate with an AT Protocol identity, then choose whether to publish a participant record in your own repository. After connecting, review both consent choices and publish your participant record here. Only after the record is saved will you be offered a link to PIXIE OS. Opening PIXIE does not enroll you.
Already have an identity? Enter your handle. If you do not have one yet, you can ask your PDS to take you through account creation.
Authentication happens with your identity provider. Made Sick never asks for your AT Protocol password.
Joining does not verify a diagnosis, legal identity, employment, authorship, or any other claim. It establishes identity control and affirmative directory participation only.
If you see a permission error after permissions change, use Log out and reconnect. OAuth grants are attached to the session; reconnecting is required to receive the updated permission set.
AT Protocol OAuth identifies the DID controlled by the participant. The browser SDK handles PKCE, DPoP, callback processing, and session storage.
The participant separately agrees to directory publication. Authentication alone never enrolls anyone.
Made Sick writes one org.made-sick.participant record to the participant's own repository. The participant can withdraw it from this page.