> For the complete documentation index, see [llms.txt](https://docs.net2grid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.net2grid.com/integration-guide/integration-guide.md).

# Integration Guide Overview

NET2GRID EnergyAI® Edge on HAN port can be integrated with in a few different ways, depending on what you're building. This page gives a quick map of the available integration paths so you can jump straight to what's relevant.

## 1. Device Onboarding & Commissioning

Before any data can flow, the hardware needs to be installed and connected. This covers physically setting up the device, connecting it via Bluetooth for commissioning, and pairing it to the household's P1 meter and WiFi network.

{% hint style="success" %}
[See Device & Onboarding for hardware setup and commissioning details.](/integration-guide/device-and-onboarding.md)
{% endhint %}

## 2. Cloud Data Streaming

For those who want either a continuous, real-time feed of energy data or just asynchronous data retrieval across their full fleet of installed devices, NET2GRID EnergyAI® Edge on HAN port forwards measurements, device metadata, and connection status updates via Kinesis Data Streams, SQS queues, and S3 flat-files.

This is the integration path for backend systems, such as trading desks, analytics pipelines, or any service that needs to consume data at scale rather than device-by-device.

{% hint style="success" %}
[See Cloud Data Streaming for the full architecture, message specifications, and setup steps](/integration-guide/cloud-data-streaming.md)
{% endhint %}

## 3. Device Management API

For managing the device fleet itself, e.g., configuring reporting modes or checking device status, the Device Management API provides a REST interface protected by an API key.

{% hint style="success" %}
[See the Device Management API reference for available endpoints.](/integration-guide/device-management-api.md)
{% endhint %}

## 4. LAN API

For local, on-site access to a single device, e.g., retrieving live measurements, device status, or other data directly from the hardware over the home network, without going through the cloud at all.

This is the integration path for local integrations and asset management tools that need to talk to the device directly.

{% hint style="success" %}
[See the LAN API reference for available endpoints.](https://docs.net2grid.com/lan-api/)
{% endhint %}

## Choosing the right path

<table><thead><tr><th width="340.640625">I want to...</th><th>Use</th></tr></thead><tbody><tr><td>Install and commission a device</td><td><a href="/integration-guide/device-and-onboarding.md">Device &#x26; Onboarding</a></td></tr><tr><td>Receive a continuous stream of data across my fleet</td><td><a href="/integration-guide/cloud-data-streaming.md">Cloud Data Streaming</a></td></tr><tr><td>Configure or manage devices remotely</td><td><a href="/integration-guide/device-management-api.md">Device Management API</a></td></tr><tr><td>Read data directly from a device on the local network</td><td><a href="/integration-guide/lan-api.md">LAN API</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.net2grid.com/integration-guide/integration-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.