Skip to main content

Platform Documentation

Guides for running work in Floxar, authoring good flows, and connecting your own AI clients and agents.

Start here

How-toGetting started: from a new account to your first flowThis walkthrough takes you from nothing to a working flow that you have run once. It has one shared start, then two paths: building your first flow with an AI client you already use, or building it yourself in the Floxar website.ConceptsWhat is Floxar?Floxar turns the way your team works into processes that people and AI agents can actually run, step by step, with a complete record of every run.Floxar in an AI stackWhere Floxar fits in an AI stackAn organization that puts AI agents to work on real tasks ends up with several layers of technology, each answering a different question. Floxar is one of those layers: the one that holds how your organization expects the work to be done, and records what actually happened when it was done.IntegrationsConnecting an AI client to FloxarFloxar has a Model Context Protocol (MCP) server, so you can work in Floxar from your own AI client: find and read your flows, steps, references and trails, run trails, and create or edit flows.

Browse the documentation

Concepts

What Floxar is, how the app and accounts are organized, and the Secrets Vault.

How-to

Sign in, build bits and flows, run trails, and manage people and settings.

All 15 articles

Authoring craft

How to write flows, bits and references that people can follow and trust.

AI features

Ask with the AI Assistant, draft with the Flow Designer, run with the Operator.

Floxar in an AI stack

Where Floxar fits among models, agents, knowledge and your own systems.

Integrations

Connect your AI client over MCP, or register an agent that works on its own.

All 19 articles

FAQ and troubleshooting

Short answers to common questions, and fixes for common problems.

These docs are also available to AI tools: llms.txt (an index) and llms-full.txt (every article in one file). Every article also has a markdown version at its address with .md in place of the trailing slash, for example /how-to/getting-started.md.