https://<name>.cycls.ai. This page lists
its endpoints. For the Cycls Cloud control plane, see the
API reference tab.
Authentication: routes marked authenticated require
Authorization: Bearer <token>, where the token comes from the configured
identity provider. Without Web().auth(...), the state routers are
not installed and only the public routes exist.
Workspace selection: in multi-workspace mode, send
X-Workspace: <id> to act inside a team workspace. No header means the personal
one.
Chat
?id=<chat_id> to continue an existing chat. Without it, a new chat id is
generated.
/chat/completions endpoint flattens components to text, so existing OpenAI
clients work unchanged. Use POST / when you want the component stream.
Configuration and metadata
Chats (authenticated)
Files (authenticated)
Rendering variants for office files:
?as=slides returns per-slide images and
?as=pdf returns a converted PDF. Both require the office render service to be
configured. See Files and the canvas.
Trash (authenticated)
Sharing
Workspaces (authenticated)
Installed only whenWeb().workspaces() is enabled.
Connectors (authenticated)
Installed when connectors are declared.Tool settings (authenticated)
App data (authenticated)
Used by apps the agent builds. See theApps tool in
Tools.
Your own routes
Add routes with.server, which is replayed onto the real router inside the
container:
Storage layout
Sessions and files live under/workspace/<scope>/, where the scope is the user
or the active workspace. Path traversal is rejected.
Next
Environment variables
Every variable the SDK and runtime read.