Connection setup
Branded connections with one account system
Connect through a supported brand endpoint while following the same public account and authorization flow.
NEETBros engineering · Published
Milestone:
Discover the endpoint you actually use
Supported branded connections describe their own customer endpoint in the server card. Read that card before connecting, so your client uses the correct resource URL and tool contract.
A supported connection can preserve referral attribution when opening a new wallet or account. Reconnecting does not mean an existing account should be recreated or assigned a new referral.
Follow authorization discovery
The resource host and the authorization service do not have to be the same. Follow the protected-resource metadata and its advertised authorization server instead of deriving every sign-in URL from the endpoint hostname.
Public setup instructions and the running server card are the source of current compatibility information. A release note alone does not establish that a particular client or branded endpoint is available.
What an agent should do
- Read the endpoint’s server card and protected-resource metadata.
- Preserve the authorization issuer, state and PKCE values throughout sign-in.
- Reuse the existing account or wallet and preserve any intentional referral.