Documentation Index
Fetch the complete documentation index at: https://docs.coreflux.org/llms.txt
Use this file to discover all available pages before exploring further.
Turn Your Broker Into a Teammate — and Your Automations Into Thinkers
Your devices, integrations, and databases already run on Coreflux — whether you monitor a factory, a solar site, a building portfolio, or a mobile fleet. AI agents live in LoT on that same broker: no separate AI platform, no copy-paste into another chat app. Talk with live data and automate with judgment. Teams ask in plain language and get answers from what the broker sees right now. Your Actions already react to MQTT and timers; with agents they can also reason on a schedule or when an event fires — a status digest, a plain-language take on an alarm, a handover brief — all throughCALL AGENT in LoT.
| What you gain | Example (any vertical) |
|---|---|
| Ask the system, don’t only chart it | ”Which zones are offline?” · “What’s output at site B?” · “Any inverters under target?” |
| Smarter automations, not more scripts | A timer or topic wakes an agent; LoT publishes the result — no babysitting a workflow |
| Reports while you sleep | Hourly or daily digest on MQTT for supervisors, facility managers, or NOC staff |
| Specialists, not one overloaded chatbot | A guide for people, a reporter on a schedule, an analyst when alarms fire — each with its own job |
Ready-to-Use Use Cases (Copy & Deploy)
Each tab is a full recipe: agent Route, LoT Action where needed, and MQTT topics to try. Adapt names to your vertical — examples in the table.| Use case | Who benefits | How it runs |
|---|---|---|
| Talk with your data | Operators, support, NOC | Ask on agents/site/ask, read agents/site/reply |
| Automatic report | Supervisors, managers | Scheduled summary on reports/operations/hourly |
| Alert triage | On-call, maintenance | Each alert gets a short AI explanation |
| Shift handover | Shift leads, crews | Plain-language brief before the next rotation |
| Vertical | Typical data topics | Automatic report might cover |
|---|---|---|
| Manufacturing | production/, lines/, quality/ | Throughput, downtime, batch issues |
| Solar & energy | solar/, inverters/, grid/ | Generation, underperformance, curtailment |
| Smart buildings | buildings/, hvac/, occupancy/ | Comfort, energy, fault patterns |
| Fleet & logistics | fleet/, vehicles/, routes/ | Utilisation, delays, asset health |
Before you start
- A running broker — Installation and Getting Started if you are new
-
A model provider — OpenAI, Anthropic, Mistral, or local Ollama on your network. Every recipe in the tabs below uses OpenAI; swap
PROVIDER,MODEL, and the secret name if you prefer another cloud provider or edge inference (see Picking a Provider). For these examples, store an OpenAI API key once on the broker:
The HUB AI Assistant (Coreflux icon in the dock) is a separate built-in helper for drafting LoT and dashboards. This guide is about your agents — the ones you own in LoT.
- Talk with your data
- Automatic report
- Alert triage
- Shift handover
Outcome: Anyone with MQTT access can ask questions; answers use live broker data (topics, Routes, recent payloads).Paste into the LoT Editor (Routes, then Actions) or your notebook:
Deploy and confirm
In HUB Routes, check SiteGuide (AGENT). In Actions, check AskSiteGuide. Both should show healthy.
Ask a real question
In MQTT Explorer or HUB Data Viewer, publish to (Rename
agents/site/ask and subscribe to agents/site/reply. Try a question that fits your data, for example:telemetry/ to production/, solar/, buildings/, or your own tree.)You just talked with your data. No extra AI server — the agent runs where your MQTT already lives.
When You’re Ready to Grow
You already have the building blocks: chat (ask/reply topics), schedules (ON EVERY), and event-driven (ON TOPIC) automations with CALL AGENT. Next level is tuning models per job, adding MCP Routes for Slack or databases, and naming agents by role so LoT stays readable.
For multi-agent patterns (operator, specialist, watchdog, reader), see Multi-Agent Deployments.
Stay Safe While You Experiment
Try read-only first
Try read-only first
Add
WITH AGENT_MODE "insight" on a Route so it can explore but not publish or trigger downstream equipment. Switch to full mode when you trust the prompt.Keep API keys off the clipboard in LoT files
Keep API keys off the clipboard in LoT files
Always use
GET SECRET "OPENAI_KEY" — never paste keys into Route definitions that get saved or shared.Match the agent to the audience
Match the agent to the audience
Chat for people; timed Actions for machines. Do not put a public chat line on agents that should only run in the background.
What to Explore Next
AI Routes (full reference)
Providers, MCP tools, multi-agent teams, and deployment settings when you outgrow this tutorial.
Using AI with Coreflux
Use MCP in your editor to write LoT faster — separate from agents running on the broker.

