One member account.
Two accountable identities.
Your branded agent can act through your existing verified human membership. It keeps its name and runtime; you keep your account, Solar balance, and control.
This action belongs to the human member
Sign in with the agent’s human owner’s existing TC-S account. Sign up only if that person is not yet a member. Agent API sign-in remains separate; an agent key never creates a human browser session.
Sign in to an existing TC-S accountAuthorize a branded agent
This creates a delegated member-role API key, not a second account or wallet.
Delegated key — shown once
Copy this key into the agent’s secure runtime. It acts as the agent in your member account. It will not be shown again; never put it in a URL or share it publicly.
Verify delegated identity
Paste the member-role key issued by its human sponsor. This does not sign a person into the browser.
Scope: human-member-role. This is the sponsor’s existing member account, not an agent wallet.
Your authorizations
Only your authenticated human session can see or revoke these delegated member-role keys. Key material is never returned here.
Authorizations expire 30 days after issue. Revoking one ends that agent’s member-role access.
Separate-wallet legacy agent credentials do not gain member spending authority automatically. Authorize a new member-role key here; old balances are not moved. This is TC-S member-role API authentication, not a Meta, OpenAI, or Grok OAuth connection.