Fluos developer resources
Fluos OpenAPI spec, authentication, webhooks, markdown negotiation, and llms.txt for agents and integrators.
This is the Fluos developer index. Fluos is an AI motion agent — a Clerk-authenticated web product. The public HTTP surface for agents is discovery, documentation, docs search, and inbound webhooks. Creating videos happens in the dashboard, not through a general-purpose generation REST API.
Start here
| Resource | URL | What it is |
|---|---|---|
| Fluos developer hub | /developers | Human-readable index of every developer URL |
| Fluos OpenAPI specification | /openapi.json | OpenAPI 3.1 with unique operationIds for function calling |
| Fluos API reference | /docs/api | Endpoint list and schemas |
| Fluos authentication | /docs/authentication | Clerk sessions and webhook signatures |
| Fluos webhooks | /docs/webhooks | Inbound Clerk, Stripe, and Resend endpoints |
| llms.txt | /llms.txt | Curated site index for language models |
| Docs search | /api/search?q= | Public full-text search over these docs |
Markdown content negotiation
Public Fluos pages implement acceptmarkdown.com. Send Accept: text/markdown to the same URL a browser uses and you receive CommonMark with Content-Type: text/markdown; charset=utf-8 and Vary: Accept.
curl -sI -H "Accept: text/markdown" https://www.fluos.io/docs/developersDocs also have Markdown siblings at /docs/{slug}.md and /docs/{slug}.mdx.
If Accept rejects both HTML and Markdown, Fluos returns 406 Not Acceptable.
What is not a public API
Authenticated product routes (/api/chat, /api/exports, /dashboard) require a Clerk session. They are not published for third-party function calling. Fluos does not currently host a public MCP server — workspace connectors use Composio OAuth from inside the product.
Contact
- Support: ask@fluos.io
- Sales: sales@fluos.ai