Authenticate a Compute client
Which credential to use to sign in or connect your Compute client, and how to confirm it points at the right account.
Choose the credential for the interface you are connecting. You sign in as yourself in the portal; your Compute client uses its assigned work key. Check the account before using data or approving work. Neither credential grants every permission.
Sign in to the portal as yourself
These steps are for customers with approved Compute access.
- Open Compute sign-in. Enter the email associated with your access, then select Email me a code.
- Enter the six-digit code from your email and select Verify & sign in. Keep the code private; do not paste it into an AI conversation.
- Follow the returned setup or account destination. Check the workspace and its status before using a team resource.
If the code is invalid or expired, use Resend code when the control becomes available. Choose Use a different email to correct the address. A message saying a code is on its way does not prove membership or access approval.
An existing team member uses their assigned access, not the owner's identity. When the portal asks you to choose an account, resolve it through the authenticated account flow. Do not substitute an account ID in a URL to bypass that choice.
Configure the client credential
| Interface | Credential boundary | Do not substitute |
|---|---|---|
| Portal | Your signed-in session and current account grant | Another person's session or a work key |
| Compute REST | Assigned Compute bearer key with the operation's required scope | A browser cookie, key prefix or key digest |
| MCP | The credential required by the client's supported connection profile | A session identifier alone or an assumed grant from the AI assistant |
REST requests use the Authorization header and Bearer scheme. Let the configured client supply them. Keep the secret in your approved credential store, not in command arguments, copied prompts, request examples or logs.
Check that the specific client actually reads that store. A saved secret does not prove the client can load it, and a successful API read does not establish a separately attributed human or service identity.
Start with a permitted read rather than a job submission. Compare the expected resource with the account associated with the assigned key. Keep the account owner and the actual person or service using the key distinct in your access records.
Recover an access refusal
If the credential is rejected, check its expiry, revocation status and configured source. If a valid credential lacks permission, compare the operation with its granted scope. Ask the administrator to correct the assignment instead of trying broader credentials.
An unavailable operation is not an authentication problem, and replacing a valid key cannot make it work. For support, retain the safe error code, operation and observation time; exclude codes, keys, cookies and signed access links.
Success means the intended portal session or client credential can perform the required authorized read. It does not approve paid work. Signing out of the browser does not revoke client keys or prove that every other session has ended.
If you do not have approved access, Apply for Compute API access. The application asks for review; it does not grant access, issue a key, start work or charge you.