Introduction

Nexalware is AIoT infrastructure that lets your software communicate with and control your physical devices, machines, and agents through a single API.

If your application needs to turn on a pump, read a sensor, open a gate, move a vehicle, monitor a machine, or coordinate physical systems, Nexalware provides the infrastructure that connects your software to those systems.

Instead of building device connectivity, authentication, command handling, telemetry, and automation yourself, you connect your application to Nexalware and work with your physical systems through a consistent API.

   YOUR SOFTWARE
   AI Agent · Backend · App
            │
            │  Nexalware API
            ↓
       ┌───────────┐
       │ NEXALWARE │
       └─────┬─────┘
             │
             ↓
     YOUR PHYSICAL DEVICES
   ┌─────────┬─────────┬─────────┐
   ↓         ↓         ↓         ↓
 Device    Machine   Vehicle   Sensor

What you can do with Nexalware

Nexalware gives your software a simple way to work with your physical systems.

The platform in one picture

Think of Nexalware as the layer between your software and the physical systems it needs to interact with.

                 YOUR SOFTWARE
      ┌─────────────────────────┐
      │                         │
      │  AI Agents              │
      │  Backend Services       │
      │  Web & Mobile Apps      │
      │  Automation             │
      │                         │
      └────────────┬────────────┘
                    │
                    ↓
             ┌───────────────┐
             │   NEXALWARE   │
             │               │
             │ Connectivity  │
             │ Identity      │
             │ Permissions   │
             │ Commands      │
             │ Telemetry     │
             │ Events        │
             │ Automation    │
             └───────┬───────┘
                     │
                     ↓
              YOUR PHYSICAL DEVICES
      ┌─────────┬─────────┬─────────┐
      ↓         ↓         ↓         ↓
    Devices   Machines  Vehicles  Sensors

Devices today, physical agents tomorrow

Today, the Nexalware API is centered around devices.

A device can represent a smart socket, pump, sensor, motor, gateway, or another connected physical system.

As the platform evolves, Nexalware is expanding this model toward physical agents. A physical agent can have its own identity, capabilities, state, permissions, sensors, actions, and relationships with other agents.

That creates a broader model:

             AI Agent
                 │
                 ↓
             Nexalware
                 │
        ┌────────┼────────┐
        ↓        ↓        ↓
     Vehicle   Security   Gate
      Agent     Agent     Agent
        │        │        │
        ↓        ↓        ↓
     Physical systems and machines

How the API fits in

The Nexalware API is the interface between your application and the Nexalware platform. Your application uses the API to:

• discover devices
• read device state
• read telemetry
• send commands
• receive events
• create automations
• manage authorized access

Physical devices connect to Nexalware's infrastructure through supported device communication protocols. For the current platform, devices connect through MQTT. Your application does not need to manage that MQTT connection when using the HTTP API - but if you're writing the firmware for the device itself, see the MicroPython Reference or Arduino IDE / C Language Reference.

Your Application
       │
       │ HTTP API
       ↓
   Nexalware
       │
       │ Device connectivity
       ↓
      MQTT
       │
       ↓
    Device

The protocol used underneath can change without requiring your application to change how it works with Nexalware.

Authentication and access

Nexalware separates human access from application access.

API keys

API keys are used by applications, backend services, scripts, and integrations. An API key must have a DeviceGrant that defines which devices and commands it can access.

X-Api-Key: your_api_key

Dashboard sessions

Dashboard sessions are used by people logged into the Nexalware dashboard. Dashboard-only actions include:

• creating devices
• creating API keys
• managing DeviceGrants
• creating schedules
• creating rules

The API Reference shows which authentication mode each endpoint requires.

Start building

The easiest way to understand Nexalware is to connect a device and make your first API request. Start with the Quickstart to connect a device, authenticate your application, read its state, and send your first command.

Then explore:

Build software that can interact with your physical world.