Returns information about the currently authenticated user. Use this to verify the connection and see user's identity (active Ory Kratos session).

Read messages from a Connhex IoT channel by its channel ID.

Use this when you already have a channel ID. To go from a device's business identifier (serial, etc.) to messages, prefer read_thing_messages, which resolves the channel ID for you from a thing ID.

Read messages for a Connhex thing (device/edge), identified by its thing ID. Resolves the thing's event_channel_id from its metadata and reads messages from it.

Resolving a user-facing identifier: If you only have a serial number or another business identifier, first use list_resources / list_manufacturing_resources to find the record, then look for a field named connhexId (or similar) — that value is the thing_id to pass here, not the record's own id.

Get a single device model by ID.

List device models with optional filtering and pagination.

List all things assigned to a specific device model.

Schema of every resource type exposed by this Connhex JSON:API service for the current deployment.

Shape:

• Top-level keys are resource type names. Use them as the resource_type argument to the corresponding *_resource tools.

• Each value is a dict of fields:

  • Entries with a type key are attributes (e.g. String, Date, Object). isArray: true indicates a list-valued attribute.

  • Entries with a link key are relationships. The link value is the related resource type — pass it (or a comma-separated list) as the include argument to fetch related records inline. isArray: true means a to-many relationship; inverse is the field name on the other side.

Internal/system fields present on every type:

• tenants, createdAt, updatedAt are managed by the platform. Do NOT include them in create/update payloads and do not surface them as user-facing data unless explicitly asked.

Read this resource before constructing filters, includes, or create/update payloads — it is the source of truth for valid types and field names.

List resources of a given type from a JSON:API service.

Supports filtering, sorting, relationship includes, and pagination. Argument details are provided in the parameter schema.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Get a specific resource by its ID from a JSON:API service.

Use include when related resources should be returned inline.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Create a new resource on a Connhex JSON:API service.

Use schema fields for attributes and relationships.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Update an existing resource's attributes (partial update).

Use schema fields for attributes. Only provided attributes are changed.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Delete a resource. This action is irreversible.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

List resources of a given type from a JSON:API service.

Supports filtering, sorting, relationship includes, and pagination. Argument details are provided in the parameter schema.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Get a specific resource by its ID from a JSON:API service.

Use include when related resources should be returned inline.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Create a new resource on a Connhex JSON:API service.

Use schema fields for attributes and relationships.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Update an existing resource's attributes (partial update).

Use schema fields for attributes. Only provided attributes are changed.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

Delete a resource. This action is irreversible.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

List rules from the Connhex Rules Engine.

Get a single rule by ID from the Connhex Rules Engine.

Create a new rule in the Connhex Rules Engine.

Partially update a rule. Only the fields provided are changed.

Delete a rule. This action is irreversible.

List rule events (triggered rule occurrences).

Get a single thing by ID.

List things with optional filtering and pagination.

Get current connectivity status for a batch of things by their IDs. Things that have never connected are omitted from the response.

Get a fleet-wide connectivity summary: online, offline, never connected, active last hour.

List devices with an excessive number of reconnections (flapping) within a time window.

Get the connect/disconnect timeline and total uptime for a single thing within a time range.

List the channels connected to a specific thing.