> ## Documentation Index
> Fetch the complete documentation index at: https://docs.altss.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Console authentication and credentials

> Separate human sign-in, organization authority, API keys and MCP authorization.

[Open Altss Console](https://console.altss.com/login?next=%2Fconsole%2Fbilling%2Fadd-funds) and confirm the intended organization. Human authentication and machine authorization are separate: an App cookie or Auth0 human-login token is not a Console API key.

## Create a credential

After confirmed funding and eligibility, use [Console credentials](https://console.altss.com/console/credentials). Grant `company.read`, the needed API or MCP channel, and explicit per-request, daily and rate limits. Store the key privately; never embed it in an example URL or commit it with a project.

An API-channel credential can use the documented REST routes. A key restricted to MCP cannot be used for REST. A credential does not authorize spending outside its approved limits or grant another organization's records.

## Discover the authority

Fetch [REST protected-resource metadata](https://console.altss.com/.well-known/oauth-protected-resource/v1/console), [MCP protected-resource metadata](https://console.altss.com/.well-known/oauth-protected-resource/v1/console/mcp) and [authorization-server metadata](https://console.altss.com/.well-known/oauth-authorization-server). Match the resource exactly and follow the advertised issuer.

## Human-approved agent registration

The [authoritative agent authentication guide](https://console.altss.com/auth.md) documents service\_auth registration, a human claim, token exchange and revocation. The human must approve the correct client, organization, scope, channels and spending limits. Email verification, current terms, billing authority and fresh-login checks still apply. Never automate approval or interpret a pending claim as access.

## MCP authorization-code flow

Compatible clients can use a public Client ID Metadata Document, S256 PKCE, state and exact MCP resource binding. Validate the redirect issuer and state. This method returns an MCP-only opaque token lasting at most one hour, with no refresh token; renewed access requires fresh authorization. It does not issue REST access. A client's generic OAuth support does not prove compatibility with this exact profile.

## Revocation and uncertain issuance

Revoke credentials through the supported Console screen or advertised revocation endpoint. Logging out does not revoke an approved machine credential. If a token response is lost, have the authorized human inspect and revoke any issued key before approving a replacement; do not blindly repeat issuance.

## Common access failures

A 401 means the credential is absent, expired, invalid or revoked. A 403 may reflect scope, channel, organization authority, terms or eligibility. Follow the response and authentication guide rather than changing to a less protected endpoint. For email\_verification\_required, verify that account's email and sign in again; repeating login alone does not verify it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.