> 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/net2grid-energy-ai-cloud/overview/input.md).

# Input

The service supports two major input categories: measurements of household electricity or gas consumption from a variety of sources and formats, as well as household profile information.

***

## Measurements

NET2GRID EnergyAI® on the Cloud processes household electricity consumption data collected at 15-, 30-, or 60-minute intervals, ensuring full compatibility with standard AMI 1.0 smart meter data. The service primarily utilizes measurements of delivered and injected energy to capture consumption and generation behavior.

In addition to standard smart meter inputs, the system can incorporate submetering and secondary meter data from specific assets such as solar panels, batteries, heat pumps, and EVs. These complementary sources, often provided through OEM or equipment manufacturer interfaces, refine disaggregation precision by aligning actual production and consumption values.

NET2GRID EnergyAI® can ingest electricity or gas measurements from three main sources, ensuring compatibility with diverse utility and market setups:

* **File Imports:** Customers can provide end-user smart meter data in standardized file formats for batch processing.
* **Datahubs:** Direct integration with national or regional smart meter data hubs enables automated, secure, scalable data streaming.
* **NET2GRID Hardware:** NET2GRID's proprietary in-home hardware (available in Europe) delivers 15-minute data for cloud-based disaggregation.

***

## Profile information

A Profile is key information about the household and its appliances, including the location (e.g., country) and the types of devices present. This data is crucial for optimizing the disaggregation process, enabling NET2GRID EnergyAI® to generate more accurate and personalized reports for each consumer.

If a consumer's profile is missing information, we can automatically apply a default profile to fill in the gaps. For example, if a consumer partially completes the profile, the remaining attributes will be inherited from the default. If no profile is provided, the entire default profile will be used. However, this reduces the level of personalization.

Default profiles are region-specific, meaning that the information they include is tailored to reflect the common attributes of each market or geographical area. This regional customization ensures that, even in the absence of user-specific data, the disaggregation service starts from a context-aware baseline that aligns with local norms.

{% hint style="info" %}
See how [NET2GRID EnergyAI® automatically enriches incomplete user profiles](https://docs.net2grid.com/net2grid-energy-ai-cloud/functionality/enriching-household-profiles.md).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.net2grid.com/net2grid-energy-ai-cloud/overview/input.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
