Leap Energy API

Name: Leap Energy API
Brand: Leap Energy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbearer26 EndpointsREST

For Agents

Onboard meters, manage CAISO bidding and dispatches, search interval and revenue data, and configure webhooks for distributed energy resource (DER) operations on Leap.

Install Jentic One Beta

Connect the Leap Energy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Leap 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%2Fleap.energy%2Fleap-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%2Fleap.energy%2Fleap-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 Leap Energy API.

Submit batch jobs to onboard new meters and poll batch job status for enrollment completion

Manage meter enrollment, idle periods, and tags to control which assets are dispatchable

Submit, modify, and cancel CAISO market bids and search bid history by meter or window

GET STARTED

Start building with Leap Energy API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Automated Meter Onboarding for an Aggregator

A virtual power plant operator onboards thousands of new residential meters into Leap. The agent submits the batch via POST /meters/batch with the meter list, polls /meters/batch/jobs/{jobId} until completion, and then verifies enrollment status per meter via GET /meters/{meterId}/enrollment. Replaces a multi-week manual onboarding workflow.

POST /meters/batch with the meter list, poll GET /meters/batch/jobs/{jobId} every 30 seconds until status is 'completed', and report the count of successfully enrolled meters.

CAISO Bidding Automation

An energy operator submits bids into the CAISO market each evening for the next operating day. The agent reads forecast availability, submits bids via POST /bids with price and quantity per resource, then verifies via POST /bids/search that the bids cleared. Cancellations and modifications use the same /bids endpoint so the agent can rebalance close to the close time.

POST /bids with the next-day bid set, then POST /bids/search filtered by the same window and confirm every bid was accepted.

Dispatch Settlement Reconciliation

An asset owner reconciles what Leap actually dispatched against their billing system. The agent runs POST /dispatches/meters/search for the settlement period, pulls POST /intervals/meter-level for the same meters, and joins the two against GET /revenue/reports to confirm the revenue line. Replaces manual CSV exports during monthly close.

Search dispatches and meter-level intervals for the prior month, pull GET /revenue/reports, and surface any meters where dispatch energy and revenue differ by more than 5 percent.

Idle-Period Maintenance Coordination

A site manager schedules maintenance windows so meters are not dispatched during downtime. The agent posts the planned window via POST /meters/{meterId}/idle-periods, lists existing windows for verification with GET /meters/{meterId}/idle-periods, and removes them with DELETE when work completes. Prevents missed-dispatch penalties.

POST /meters/{meterId}/idle-periods with the maintenance window, then DELETE the same window when the technician marks the work complete.

AI Agent Energy Operator via Jentic

An AI agent built on Jentic acts as a junior operator: it watches dispatch webhooks, summarises the day's CAISO performance, flags meters that under-delivered, and drafts the bid set for the next day. Jentic isolates the bearer token so the agent can run unattended without exposing market credentials.

Through Jentic, search 'submit caiso bid', load the schema for POST /bids, and execute the next-day bid set after a human approves the draft.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for leap energy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/meters/batch

Submit a batch meter onboarding job

GET

/meters/{meterId}/enrollment

Get enrollment state for a meter

POST

/bids

Submit, modify, or cancel a CAISO bid

POST

/bids/search

Search bid history with filters

POST

/dispatches/meters/search

Search dispatches by meter

POST

/intervals/meter-level

List meter-level interval energy data

GET

/revenue/reports

Get monthly revenue reports

POST

/webhooks

Create a webhook subscription

POST

/meters/batch

Submit a batch meter onboarding job

GET

/meters/{meterId}/enrollment

Get enrollment state for a meter

POST

/bids

Submit, modify, or cancel a CAISO bid

POST

/bids/search

Search bid history with filters

POST

/dispatches/meters/search

Search dispatches by meter

Why Jentic?

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

Setup

Wiring the Leap Energy API by hand means setting the bearer token in the Authorization header, targeting the api.leap.energy host, and coordinating the meter, bid, and dispatch endpoints yourself. Through Jentic you install once, import the Leap Energy API from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

You choose which Leap operations the agent may call, so you can limit it to the ones it needs, such as reading revenue reports and searching dispatches. Because submitting a market bid carries financial weight, you can leave the bid operation out of the allowed set and grant only read and reporting access.

Credential isolation

Your Leap bearer token, which carries the rights to submit market bids, 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 'submit a CAISO bid' or 'onboard meters in a batch', and Jentic returns the matching Leap operation with its input schema so the agent calls the right endpoint without parsing the paths by hand.

FAQs

Specific to using Leap Energy API through Jentic.

Why is there no official OpenAPI spec for Leap Energy API?

Leap Energy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Leap Energy API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Leap Energy API use?

The Leap Energy API uses bearer token authentication: each request includes an `Authorization: Bearer <token>` header. Through Jentic, the bearer token is held in the credential vault and applied at execution time so it never enters the agent's context.

Can I submit and cancel CAISO market bids through the Leap API?

Yes. POST /bids handles submit, modify, and cancel actions on the same endpoint with different payloads, and POST /bids/search returns the resulting state filtered by meter, group, or time window.

What are the rate limits for the Leap Energy API?

Rate limits are not published in the spec. Bidding is window-bound by CAISO market deadlines, so the practical constraint is timing rather than request volume - submit bids well ahead of the gate-close time and use webhooks rather than polling for dispatch updates.

How do I onboard a batch of meters through Jentic?

Run `pip install jentic`, search 'onboard meters batch', and execute POST /meters/batch with the meter list. Then poll GET /meters/batch/jobs/{jobId} via the same Jentic flow until the job reports completion.

Are webhooks available for dispatches and enrollment events?

Yes. POST /webhooks creates a webhook subscription, PUT /webhooks/{webhookId} updates it, and POST /webhooks/{webhookId}/test sends a test payload. Subscribe rather than polling /dispatches and /connections for production workloads.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Leap operations the agent may call and which credentials it may use. You can allow only read and reporting operations such as GET /revenue/reports and POST /dispatches/meters/search while leaving the financially weighty POST /bids submission out of the allowed set. That way the agent can reconcile dispatches and pull revenue without ever being able to submit or cancel a CAISO market bid.

Leap Energy API

Connect the Leap Energy API to your agent

Capabilities

Start building with Leap Energy API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs