Skip to content

Token handling for agents ​

Keeping credentials out of prompts, skills and logs when an agent works with Salaxy.

This section is being written

The headings show what each page will cover. MCP sign-in is described on MCP authentication, REST sign-in on REST authentication.

Tokens never go into prompts or skills ​

Credentials are handled by the client or the partner's backend, never by the model.

Test and live credentials ​

Kept apart: the MCP demo servers use a demo account, production your own Salaxy account.

Lifetime and revocation ​

How long tokens live and how access is withdrawn. Known today: a REST access token lasts 48 hours and cannot be refreshed — see Tokens. A certificate that signs your JWTs is withdrawn by revoking it — see Impersonation.

Logs ​

What must not be written to conversation or application logs.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.