---
name: citusio-website
description: Find CitusIO product requirements, operating skills and public SDK guidance, then work through the installed product's versioned contracts with customer-selected tools.
---

# Use CitusIO with the customer's chosen agent and tools

Start with the user's actual installation, migration, diagnosis or development
task. The website serves both human readers and agents. Skills are ordinary
Markdown; the [machine catalog](index.json) lists their scope, minimum tier and
content hashes. No proprietary client, agent framework or host script runtime
is required to use the product's existing HTTP API.

## Select the relevant skill

- New node: [container setup](container-setup/SKILL.md), then
  [panel operation](panel-operations/SKILL.md) or
  [direct API operation](admin-api-operations/SKILL.md).
- Existing broker replacement: [Mosquitto](migrate-mosquitto/SKILL.md) or
  [EMQX](migrate-emqx/SKILL.md), then [cutover/rollback](migration-cutover/SKILL.md).
- Existing node: [operations](container-operations/SKILL.md),
  [durable recovery](durable-recovery/SKILL.md) or
  [Enterprise ownership](enterprise-operations/SKILL.md), as applicable.
- Custom sink: [bridge development](bridge-development/SKILL.md); use
  [integration bridges](integration-bridges/SKILL.md) for a selected provider.

Read only the relevant skill and its dependencies. Preserve a private task
record and the first unfinished action. Skills explain workflows; they do not
grant permission to deploy, purchase, change providers or submit commands.

## Bind to the installed product

The website publishes current source guidance. An installed image contains its
own tier-filtered skills, manifest and deployment kit; prefer those for the
actual running version. Read the image's requirements, panel build metadata,
live API identity and backend availability before choosing an operation.

Free, Pro, Max and Enterprise map to internal image lanes `evaluation-demo`,
`core-broker`, `integration-edge` and `enterprise-operations`. Legacy Evaluation
identifiers describe configuration compatibility. Every tier permits production
use; memory/durability and paid service boundaries remain explicit.

Use the [task contract](contracts/agent-tasks.json) and
[OpenAPI schema](contracts/openapi.json) for method/path, bounded
inputs, role, side effects and completion. The catalog lists possible operations;
the live daemon owns actual scope and admission. Before writing, bind node,
routing generation, writer term, ring generation and config digest to a fresh
matching dashboard. Preserve unsigned 64-bit versions as decimal strings.

Submit one authorized exact intent. HTTP acceptance is pending. Observe the
original command ID and require matching audit/reconciliation evidence. Recover
a lost response through bounded GETs of existing events/status without a new
submission. Withdraw write permission on stale scope or session loss; retain
diagnostic evidence as stale. Use private credential storage and redact handoffs.

## Product and purchasing references

Use [Get Start](https://citusio.com/get-started),
[Tiers](https://citusio.com/products), [Build](https://citusio.com/build) and
[product facts](https://citusio.com/product.json). Performance facts bind exact
images and workload conditions; do not convert sampled rates into a sizing or
durability promise.

Pricing and Paddle checkout live at [checkout.citusio.com](https://checkout.citusio.com).
Reading this site never authorizes a purchase or production billing change.
Follow the customer's existing authority and confirm the exact tier/period,
entitlement and image before making a paid action.