Platform UI access (SSO)
Caylex uses SSO for platform access. When you sign up or log in to the Caylex Platform UI, you authenticate through the platform’s identity provider. This gives you access to manage your organization’s projects, servers, navigators, and analytics.Programmatic access with a platform access token
The Caylex platform exposes a REST API for managing your workspace without clicking through the Caylex Platform UI. It covers projects, skills, usage, analytics, tool security, and more. Authenticate with a platform access token and call the API from a script, a CI pipeline, or your own backend. This is the control plane for your workspace. It is separate from the runtime connection your agents use to call tools, which uses a Navigator API key instead (see Connecting your agent).Create a platform access token
1
Open the Administration page
In the Caylex Platform UI, go to the Administration page.
2
Create a token
Create a new platform access token and give it a descriptive name (for example,
ci-skill-sync). Optionally set an expiry date.3
Copy the token
Copy the token value and store it in a secret manager or CI secret. The raw token is shown only once. If you lose it, revoke it and create a new one.
Authenticate
Send the token in theAuthorization header as a Bearer token against the https://api.caylex.ai/api/v1 base URL. To verify your token works, list your projects:
- cURL
- Python
- TypeScript
What you can manage
A platform access token works across the workspace management endpoints. Some of the most common:Worked examples
For complete, copy-pasteable workflows built on the Platform API — syncing skills from CI, provisioning a project per customer, and replicating tool permissions across projects — see the Cookbooks.Security best practices
- Keep tokens server-side. Call the Platform API from your backend or CI only, never from a browser or mobile client.
- Use a secret manager. Store tokens in your CI provider’s secrets or a secret manager, not in code or
.envfiles committed to git. - Set an expiry. Give tokens an expiry date where possible, and create separate tokens for separate systems so you can revoke one without disrupting others.
- Rotate and revoke. Rotate tokens periodically, and revoke any token immediately from the Administration page if it may be compromised.
Next steps
Cookbooks
End-to-end recipes for automating common workflows with the Platform API.
REST API Reference
Browse the full REST API: every endpoint, parameter, and response schema.
Server Authentication
See how your end users authenticate with external MCP servers.
Agent Widget
Mint widget session tokens with your platform access token to embed a chat agent.
Connecting your agent
Connect an agent to the MCP runtime with a Navigator API key.