Skip to main content

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 through CALL AGENT in LoT.
What you gainExample (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 scriptsA timer or topic wakes an agent; LoT publishes the result — no babysitting a workflow
Reports while you sleepHourly or daily digest on MQTT for supervisors, facility managers, or NOC staff
Specialists, not one overloaded chatbotA guide for people, a reporter on a schedule, an analyst when alarms fire — each with its own job
You define agents once in LoT (alongside your Actions and Routes). Below are ready-to-use use cases you can paste and deploy — pick one to prove value in minutes, or combine several on the same broker. Full options — multi-agent teams, MCP tools, safety rails — are in AI Routes.
Like a supervisor on the floor and a analyst on the line. People get answers when they ask; your automations get judgment when something changes — all on the broker you already run.

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 caseWho benefitsHow it runs
Talk with your dataOperators, support, NOCAsk on agents/site/ask, read agents/site/reply
Automatic reportSupervisors, managersScheduled summary on reports/operations/hourly
Alert triageOn-call, maintenanceEach alert gets a short AI explanation
Shift handoverShift leads, crewsPlain-language brief before the next rotation
Some examples of use-cases for your industry:
VerticalTypical data topicsAutomatic report might cover
Manufacturingproduction/, lines/, quality/Throughput, downtime, batch issues
Solar & energysolar/, inverters/, grid/Generation, underperformance, curtailment
Smart buildingsbuildings/, hvac/, occupancy/Comfort, energy, fault patterns
Fleet & logisticsfleet/, vehicles/, routes/Utilisation, delays, asset health

Before you start

  • A running brokerInstallation 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:
KEEP SECRET "OPENAI_KEY" WITH "sk-..."
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.
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:
DEFINE ROUTE SiteGuide WITH TYPE AGENT
    ADD AGENT_CONFIG
        WITH PROVIDER "openai"
        WITH MODEL "gpt-5.5"
        WITH API_KEY GET SECRET "OPENAI_KEY"
        WITH BROKER_TOOLS "true"
        WITH INTERACTION_MODE "interactive"
        WITH INTERACTION_TOPIC "agents/site/interact"
        WITH SYSTEM_PROMPT "You are a site operations guide. Use broker tools to answer from live MQTT data for this deployment. Be concise."

DEFINE ACTION AskSiteGuide
ON TOPIC "agents/site/ask" DO
    CALL AGENT "SiteGuide.execute"
        WITH (task = PAYLOAD)
        RETURN AS {reply}

    PUBLISH TOPIC "agents/site/reply" WITH {reply}
1

Deploy and confirm

In HUB Routes, check SiteGuide (AGENT). In Actions, check AskSiteGuide. Both should show healthy.
2

Ask a real question

In MQTT Explorer or HUB Data Viewer, publish to agents/site/ask and subscribe to agents/site/reply. Try a question that fits your data, for example:
Which sensors have been updated in the last few minutes?
What is the latest data on telemetry/zone1/status?
(Rename telemetry/ to production/, solar/, buildings/, or your own tree.)
3

Read the answer on reply

The reply topic carries the agent’s answer — grounded in what your broker actually sees.
You just talked with your data. No extra AI server — the agent runs where your MQTT already lives.
Starter pack: SiteGuide + HourlyOperationsReport + AlertAnalyst — ask your deployment, get scheduled insight, enrich every alarm. Rename topics to production/, solar/, or buildings/ when you copy the prompts.

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

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.
Always use GET SECRET "OPENAI_KEY" — never paste keys into Route definitions that get saved or shared.
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.
Last modified on May 28, 2026