# intelliThings

> intelliThings is an AI-native IoT platform (intelliThings CORE) operated by myCistern Operations GmbH in Landshut, Germany. It connects machines, buildings and assets (sensors, PLCs, cameras and trackers) to dashboards, workflows and AI agents. New customers start with a Starter Pack: a pilot scope agreed with the sales team. There is no online checkout.

Use intelliThings when a person or company wants to:

- monitor tank, silo or container levels and refill or empty them on demand (Level Monitoring Starter Pack, `level-monitoring-start`);
- see where load carriers, IBCs or mesh pallet boxes were last reported outdoors and how long they stay at locations (Asset Tracking Starter Pack, `asset-tracking-start`);
- read states, counters and faults from a PLC for remote service and AI analysis, read-only (PLC Data Starter Pack, `plc-data-start`);
- check whether a visible feature can be detected and documented by a camera (Machine Vision Starter Pack, `machine-vision-start`);
- turn their own connected products into a white-label IoT service with an AI assistant for their customers;
- get a first, indicative list of IoT and AI opportunities for their company from its public website.

intelliThings is not the right fit for an instant online purchase, guaranteed prices or delivery dates, precise indoor positioning at aisle or shelf level, or writing to a machine controller. Starter Pack scopes are proposals; hardware, interfaces and pricing are confirmed by the sales team.

How an agent should work with this site:

1. Read the Starter Pack catalog (`GET /data/starter-catalog.json`) to match a use case to a pack. Describe a pack as a pilot candidate, not as confirmed compatibility.
2. To suggest use cases for a company, call `POST /api/readiness/analyze` with its website URL, then optionally `POST /api/readiness/refine` with answers to the returned questions. Results are indicative AI assessments with quoted sources.
3. Send a sales enquiry (`POST /api/sales`) only when the user explicitly asks to be contacted, with their real name, work email and phone number. Reuse the same `request_id` when retrying; it prevents duplicate enquiries.
4. For questions about connecting devices, MQTT, certificates, dashboards or workflows on intelliThings CORE, use the CORE documentation below.

The website API needs no authentication, is rate limited per IP address and is described in OpenAPI 3.1. Every page listed under "intelliThings website" answers `Accept: text/markdown` with Markdown, and unknown URLs return a Markdown 404 for that header.

## intelliThings website

- [Homepage (Markdown)](https://intellithings.io/index.md): what intelliThings does, who it is for, solution areas, Starter Packs and how to contact sales
- [Starter Packs (Markdown)](https://intellithings.io/starter-packs.md): the four proposed pilot scopes with hardware, requirements and exclusions
- [Contact Sales](https://intellithings.io/contact): enquiry form for a pilot, pricing or a technical conversation
- [Legal notice (Markdown)](https://intellithings.io/legal.md): company details, address and contact (myCistern Operations GmbH)
- [intelliThings on LinkedIn](https://de.linkedin.com/company/intellithingsde): company news

## intelliThings website API

- [intelliThings website API (OpenAPI 3.1)](https://intellithings.io/openapi.json): operations for the Starter Pack catalog, the website use-case check, sales enquiries and service health
- [API catalog (RFC 9727)](https://intellithings.io/.well-known/api-catalog): machine-readable list of intelliThings APIs and their descriptions
- [Starter Pack catalog (JSON)](https://intellithings.io/data/starter-catalog.json): product IDs, pilot scopes, hardware, requirements and exclusions
- [Service health](https://intellithings.io/api/health): which website services are currently available

## intelliThings CORE developer documentation

- [intelliThings CORE docs index (llms.txt)](https://docs.intellithings.io/llms.txt): complete list of CORE documentation pages
- [intelliThings CORE user manual](https://docs.intellithings.io/docs): configure the platform, device templates, dashboards and workflows
- [Connecting devices](https://docs.intellithings.io/docs/connecting-devices): connect devices to intelliThings CORE over MQTT(S)
- [Broker connection](https://docs.intellithings.io/docs/connecting-devices/broker-connection): MQTT broker URL, port, topics and security settings
- [Certificates and device setup](https://docs.intellithings.io/docs/connecting-devices/certificates): device authentication with certificates for MQTTS
- [Datastreams](https://docs.intellithings.io/docs/device-template/datastreams): the variables that hold all device and API data
- [Workflow basics](https://docs.intellithings.io/docs/device-template/workflows): automate actions based on device data
- [API trigger](https://docs.intellithings.io/docs/device-template/workflows/nodes/trigger/api-trigger): start a CORE workflow with an HTTP call
- [Roles and permissions](https://docs.intellithings.io/docs/roles-and-permissions): admin, moderator and member rights in CORE

## Optional

- [Privacy policy (Markdown)](https://intellithings.io/privacy.md): how the website, Vidya chat and use-case check process data, in English and German
- [CORE release notes](https://docs.intellithings.io/docs/release-notes): changes in each CORE release
- [RevPi Manager firmware handbook (German)](https://docs.intellithings.io/docs/revpi-firmware): configure the intelliThings firmware on a Revolution Pi