Skip to main content
https://api.cycls.ai is the control plane. The CLI is a client for it, so anything cycls can do, your own tooling can do too.
This is the platform API. For the endpoints a deployed agent serves, such as chat, files and share links, see the Agent HTTP API.

Authentication

Every endpoint accepts either header.
Get an API key from Cycls Cloud. Requests are scoped to the account that owns the key, so listings return only your resources.

What the API covers

Deploying

POST /v1/deploy takes a multipart form with the source archive and streams NDJSON progress events back.
Events arrive in order: BUILDING, then DEPLOYING, then DONE or ERROR. Two fields behave as complete declarations rather than patches:
  • volumes maps mount paths to volumes. {} declares no storage. Unknown volumes are created and the stream announces it.
  • schedule sets the cron. Omitting it or sending an empty value removes any existing schedule.
The archive is capped at 100 MiB. Ship large files through a volume instead.

Moving volume data

Uploads and downloads do not pass through the API. Request a signed URL, then transfer directly to storage.
The response carries a URL you PUT the bytes to. cycls volume put and cycls volume get do exactly this, which is why file size is effectively unlimited.

Rate limits and errors

Endpoint reference

Every endpoint, with parameters, schemas and a request builder, is in the pages under Endpoints in the sidebar. The specification is generated from the live service and mirrored at api.cycls.ai/openapi.json.