Install Jentic One Beta

Connect the Netzero Energy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Netzero Energy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetzero.energy%2Fnetzero-energy" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetzero.energy%2Fnetzero-energy" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Netzero Energy API.

Retrieve live status for a Tesla Powerwall site including solar generation, battery percentage, and grid import or export

Update Powerwall operating mode and reserve percentage by posting a new configuration for the site

Authenticate every request with a bearer token issued from the Netzero app Developer API screen

Address a specific Tesla energy site by its site identifier in the URL path

GET STARTED

Start building with Netzero Energy API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Netzero Energy API for, with concrete tasks.

★ Home Energy Dashboard

Solar installers and prosumers build dashboards that show live Tesla Powerwall battery state, instantaneous solar production, and grid flows by polling GET /{site_id}/config. Because Netzero brokers the connection, the dashboard avoids dealing with Tesla's official Fleet API approval process and OAuth dance.

Call GET /{site_id}/config every 30 seconds, extract battery_percentage, solar_power, and grid_power, and push the values into a time-series database for charting.

Time-of-Use Powerwall Optimization

An automation script flips the Powerwall between self-consumption and backup-only modes based on local electricity tariffs by calling POST /{site_id}/config with a new configuration body. This shifts battery discharge into expensive peak windows and reserves capacity during cheap off-peak hours.

At 16:00 local time, POST to /{site_id}/config with operating_mode 'self_consumption' and reserve_percentage 20 so the Powerwall discharges into peak-rate hours.

Demand Response Participation

Energy aggregators enrolling Tesla homes in demand response programs use the Netzero Energy API to read Powerwall reserve levels and adjust them on grid event signals. The single config POST changes battery dispatch behaviour for the duration of the event without requiring user intervention.

On a demand response trigger at 18:30, POST to /{site_id}/config with reserve_percentage 0 to allow full discharge for the two-hour event window.

AI Agent Energy Assistant

A home assistant agent uses Jentic to discover Netzero Energy operations, then answers natural questions like 'how much solar are we generating right now?' by reading the live config and translating the JSON response into a spoken or chat reply, without the developer hand-coding the integration.

Use Jentic to search 'get tesla powerwall live status', load the GET /{site_id}/config schema, execute it, and summarise solar_power, battery_percentage, and grid_power in a one-sentence reply.

Key Endpoints

2 endpoints — the netzero energy api gives developers programmatic access to tesla powerwall and tesla solar configuration through netzero's third-party platform.

METHOD

PATH

DESCRIPTION

GET

/{site_id}/config

Get site configuration and live status

POST

/{site_id}/config

Modify site configuration

GET

/{site_id}/config

Get site configuration and live status

POST

/{site_id}/config

Modify site configuration

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Netzero Energy API by hand means setting its bearer auth, targeting the api.netzero.energy/api/v1 host, and shaping Powerwall site config read and write calls yourself. Through Jentic you install once, import Netzero Energy from the API Directory, store the token once, and your agent calls it.

Permission scoping

Netzero Energy puts the site id in the URL path (/{site_id}/config), so a rule can pin your agent to one Powerwall site. You choose the operations it may call, so the config write is not included unless you add it, leaving the agent with read-only status.

Credential isolation

Your Netzero bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get Tesla Powerwall live status' or 'update a site config', and Jentic returns the matching Netzero Energy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Netzero Energy API through Jentic.

What authentication does the Netzero Energy API use?

Netzero Energy uses HTTP bearer token authentication. The token is generated inside the Netzero app under account settings > Developer API and is sent in the Authorization header as 'Bearer <token>'. Through Jentic, the bearer token is held in the encrypted Jentic One instance and never appears in the agent's context.

Can I read live Powerwall battery and solar data with the Netzero Energy API?

Yes. GET /{site_id}/config returns both the stored configuration and live telemetry - including battery percentage, instantaneous solar power, and grid import or export - for the Tesla site identified by site_id.

How do I change Powerwall operating mode through Jentic?

Search Jentic for 'set tesla powerwall operating mode', load the POST /{site_id}/config schema, and execute the call with the desired operating_mode and reserve_percentage values. Jentic handles the bearer token automatically.

What are the rate limits for the Netzero Energy API?

The spec does not declare explicit numeric rate limits. Polling intervals of 15-30 seconds for live status are typical for home dashboards; treat the API as soft-rate-limited and back off on 429 responses.

Does the Netzero Energy API replace the Tesla Fleet API?

Netzero Energy is a third-party broker that exposes a simpler interface to a subset of Tesla site data and controls. It avoids the Tesla Fleet API partner approval process but only supports site configuration and live status - not vehicle, charging, or full Fleet API operations.

Is the Netzero Energy API free?

API access is included with a Netzero account that is already linked to a Tesla energy site. Token generation happens inside the Netzero app once the linked site is verified.

Can I limit what my agent is allowed to do with the Netzero Energy API?

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials your agent may use. Because the site id sits in the URL path (/{site_id}/config), you can pin the agent to one Powerwall site, and you choose whether it gets the read-only GET /{site_id}/config for live status or also the POST /{site_id}/config that changes operating mode and reserve percentage. Leave the write operation out and the agent can read solar, battery, and grid telemetry but cannot alter the Powerwall configuration.

Netzero Energy API

Name: Netzero Energy API
Brand: Netzero Energy API
Availability: InStock

Official vendor OpenAPI document · agent-readyIOTDevice Managementbearer2 EndpointsREST

For Agents

Read live Tesla Powerwall solar and battery telemetry and update Powerwall operating modes for a specific Tesla energy site.

Use for: Get the current Powerwall battery percentage for my Tesla site, Retrieve live solar generation for a Tesla Powerwall site, Set the Powerwall reserve percentage to 50, Switch the Powerwall to self-consumption mode

Not supported: Does not handle Tesla vehicles, charging sessions, or solar installation orders - use for Tesla Powerwall site configuration and live status only.

The Netzero Energy API gives developers programmatic access to Tesla Powerwall and Tesla solar configuration through Netzero's third-party platform. It exposes site configuration retrieval and updates plus live telemetry covering solar generation, battery state, and grid power flows. Bearer tokens are minted in the Netzero app under Developer API settings and authorise calls scoped to the user's specific Tesla site.

Jentic One on Github View OpenAPI Document

Connect the Netzero Energy API to your agent

Capabilities

Start building with Netzero Energy API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Netzero Energy API