canonical: https://jentic.com/apis/greenlake.hpe.com/greenlake-hpe

# Greenlake Hpe HPE GreenLake Sustainability API

Jentic publishes the only available OpenAPI specification for HPE GreenLake Sustainability API, keeping it validated and agent-ready. The HPE GreenLake Sustainability Insight Center API exposes environmental metrics, devices, and reports for IT estates managed under HPE GreenLake. Three endpoints - /devices, /metrics, and /reports - let teams pull energy use, carbon, and other sustainability data programmatically with an API key passed in the Authorization header.

## For AI agents

Pull HPE GreenLake sustainability metrics, device inventory, and environmental reports for an IT estate.

## Scope

Does not provision compute, manage workloads, or run financial reporting - use for reading sustainability metrics, device inventory, and reports from HPE GreenLake only.

## Capabilities

- List the devices inventoried by HPE GreenLake Sustainability Insight Center via /devices
- Retrieve current and historical sustainability metrics from /metrics
- List or download generated sustainability reports from /reports
- Feed energy and carbon metrics into a corporate ESG dashboard
- Track device-level energy consumption trends over time
- Export sustainability reports for environmental disclosure filings

## Use cases

### ESG Dashboard for IT Estate

Sustainability and finance teams pull /metrics on a daily schedule to feed corporate ESG dashboards with energy consumption and carbon emissions for the GreenLake-managed IT estate. The metrics feed sits alongside facilities and travel data to produce a unified scope 2 view.

Example prompt: GET /metrics for the last 30 days and write energy_kwh and carbon_kg fields into the ESG warehouse table

### Disclosure-Ready Report Export

Compliance teams use /reports to retrieve the sustainability reports generated by the GreenLake Sustainability Insight Center and store them with the rest of the company's environmental disclosure evidence pack. Each report record exposes the report id, period, and download artifacts.

Example prompt: GET /reports, filter to the most recent quarterly report, and store the artifact in the compliance evidence drive

### Device-Level Energy Trend Analysis

Platform engineering teams join /devices with /metrics to find the highest-consuming devices in the estate and prioritise modernisation or relocation. The combined view shows per-device energy use over time so changes can be measured against baseline.

Example prompt: List /devices and for each one fetch /metrics filtered by device id over the last 90 days, then return the top 10 by energy use

### Agent-Driven Sustainability Reporting via Jentic

An AI sustainability assistant uses Jentic to discover the right GreenLake operation when a sustainability lead asks 'what was our IT energy last month?' or 'fetch the latest report'. Jentic injects the API key from the vault and the agent works against structured GreenLake data.

Example prompt: Search Jentic for 'fetch greenlake sustainability metrics', load the schema, and execute /metrics for the requested time window

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/devices` | List devices in the IT estate |
| GET | `/metrics` | Retrieve sustainability metrics |
| GET | `/reports` | List and download sustainability reports |

## Key resources

- **Devices** — List devices covered by GreenLake Sustainability Insight Center
- **Metrics** — Retrieve sustainability metrics such as energy use and emissions
- **Reports** — List and download generated sustainability reports

## Why Jentic

- **Setup:** Wiring the HPE GreenLake Sustainability API by hand means carrying its API key in the Authorization header and wiring the metrics, reports, and devices endpoints yourself. Through Jentic you install once, import the HPE GreenLake Sustainability API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** HPE GreenLake Sustainability exposes flat read endpoints and carries its targets in the request, so limit the agent to the operations it needs, such as reading sustainability metrics or listing devices. Every operation you allow is one you have chosen, and you leave out any you do not want the agent to call.
- **Credential handling:** Your HPE GreenLake API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'get sustainability metrics' or 'list device inventory', and Jentic returns the matching HPE GreenLake operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Graylog** — Centralized log search to investigate device anomalies discovered via metrics
- **New Relic** — Application performance metrics that pair with infrastructure sustainability data
- **Splunk** — Operational analytics that can ingest GreenLake sustainability metrics for joint dashboards

## FAQ

### Why is there no official OpenAPI spec for HPE GreenLake Sustainability API?

HPE GreenLake documents the Sustainability Insight Center API in its developer portal but does not publish a maintained OpenAPI 3 file for tooling. Jentic generates and maintains this spec so that AI agents and developers can call HPE GreenLake Sustainability 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 HPE GreenLake Sustainability API use?

The API expects an API key in the Authorization header. Through Jentic the API key is stored encrypted in the vault and added to each request, so the agent's prompt and memory never contain the raw secret.

### Can I retrieve energy consumption per device?

Yes. List /devices to get the inventory and then call /metrics with a device-id filter to retrieve per-device energy and emissions data over the chosen time range. Aggregations across the estate are also available directly from /metrics without specifying a device.

### What are the rate limits for the HPE GreenLake Sustainability API?

HPE does not publish a fixed numerical rate limit for the Sustainability Insight Center API. The three endpoints in this spec are designed for periodic reporting workloads rather than high-frequency polling, so a daily or hourly cadence is typically sufficient. HTTP 429 responses propagate through Jentic so the agent can back off.

### How do I download the latest sustainability report through Jentic?

Search Jentic for 'fetch greenlake sustainability report', load the operation that maps to GET /reports, and execute it. Filter the response to the latest period and use the returned artifact link to retrieve the report file for storage in the company's compliance evidence drive.

### Does this API include scope 1 or scope 3 emissions?

The Sustainability Insight Center focuses on the IT estate covered by HPE GreenLake, which contributes to scope 2 (purchased electricity) and indirectly to scope 3 emissions for hardware lifecycle. For full corporate scope 1 and scope 3 reporting, combine these metrics with facilities, travel, and supply-chain data sources.

### Can I limit what my agent is allowed to do with the HPE GreenLake Sustainability API?

Yes. Jentic One is self-hosted, so your own rules decide which of the flat read operations the agent may call: reading sustainability metrics from /metrics, listing devices from /devices, or listing and downloading reports from /reports. Because each operation you allow is one you have explicitly chosen, you can grant only /metrics for an ESG dashboard while leaving out /reports and /devices entirely. The API key is stored by your own instance and injected at execution time, so the agent only ever reaches the endpoints you permit.