Skip to main content
Client tokens are short-lived credentials with the titan_ct_ prefix. They are designed for browser and mobile use, but they are not JWTs and do not carry unrestricted API-key authority.

Mint

Call POST /api/client-tokens with a service credential that has sessions:manage:
The response uses the standard success envelope:
ttlSeconds must be within the bounds documented for the endpoint. The token is limited to its organization, session, ephemeral ID, and expiry.

Session rules

Rules are managed independently:
recipientMode is one of conversation, any, or none. Unknown modes fail closed. allowedActions is a comma-separated list containing only these values:
The mcp action permits the protocol handshake. Each MCP tool still passes through its ordinary session, recipient, action, origin, and rate rules.

Security behavior

  • Client tokens cannot mint other tokens.
  • Rules, recipient/conversation state, origin constraints, and rate limits are checked after the token authenticates.
  • Delete or disable the session rules to stop permitted effects before all issued tokens expire.
Use the generated Messaging API endpoint pages for the exact ClientToken and ClientRules component fields.