Fluso API
Give Fluso work from your own script or application, then read the result.
Use the API to send a message, attach a document, or run a saved Agent. Your integration uses the same workspace as the Fluso app.
Start with one conversation. Add schedules, connections, or live updates when your application needs them.
Send your first request
Get access, submit a short task, and read the saved answer.
Choose your workspace
Cloud and Fluso Local share the conversation, Agent, file, and schedule APIs. Their credentials and administration differ. Data stays in the workspace you address.
| Cloud API | Daemon API | |
|---|---|---|
| Where work runs | Your Fluso Cloud workspace | Your own machine's Fluso Local workspace |
| Access for scripts | Developer token | Paired device token |
| Example base URL | https://api.fluso.ai/v1 | http://127.0.0.1:4111/v1 |
| Connected apps | Managed apps and custom MCP servers | Custom MCP servers |
| Public sharing | Agents, conversations, and files | Unavailable |
| Machine settings | Managed by the service | Provider, sandbox, and devices |
Fluso Dev uses https://api.dev.khichdi.cc/v1. Use credentials from the same environment as the URL.
For a remote daemon, use its HTTPS address or an SSH tunnel. A Cloud token cannot access a daemon.
Find the exact fields
Open Settings → Developer tokens → API reference in Cloud. On a daemon's host, open http://127.0.0.1:4111/docs.
Releases with this API serve the endpoint reference at /docs and the OpenAPI schema at /v1/openapi.json. These describe the fields and operations available in that deployment. The reference also supplies runnable examples under /v1/examples/. The daemon serves its schema and examples locally. Its interactive reference needs internet access to load the viewer.
The guides below explain how to combine those operations. Endpoint tables sit inside each guide, after the main workflow.
Cloud access
Create a developer token and choose its access.
Daemon access
Pair a client with your own workspace.
Send messages
Continue work and read the complete answer.
Runs and retries
Handle a timeout without starting the same work twice.
If your app lacks Developer tokens or its API reference returns 404, contact support about availability for your release.