canonical: https://jentic.com/apis/powerly.app/powerly

# Powerly App Powerly API

Jentic publishes the only available OpenAPI specification for Powerly API, keeping it validated and agent-ready. The Powerly API provides access to an EV charging station network, offering authentication via client credentials and resource management for charging infrastructure. It exposes endpoints for obtaining access tokens, listing available resources with pagination, and retrieving individual resource details by ID.

## For AI agents

Access and manage EV charging station network resources. Authenticate with client credentials, list available charging resources, and retrieve individual station details.

## Scope

Does not handle charging session initiation, payment processing, or real-time availability updates - use for charging station inventory and details only.

## Capabilities

- Authenticate using client credentials to obtain time-limited access tokens
- List EV charging resources with configurable pagination via limit and offset
- Retrieve detailed information about a specific charging resource by its identifier
- Support paginated browsing of the full charging station inventory

## Use cases

### EV Charging Station Discovery

Browse and query available EV charging stations in the Powerly network. The API supports paginated listing of resources with configurable limit and offset parameters, returning resource data along with a total count. This enables building station finder applications, fleet management dashboards, or integration into navigation systems that need to display available charging infrastructure.

Example prompt: Authenticate with client credentials via POST `/auth/token`, then list the first 10 charging resources using GET /resources with limit=10 and offset=0

### Charging Resource Detail Lookup

Retrieve detailed information about a specific EV charging station by its unique identifier. This enables applications to display station-specific data such as charger type, availability status, or location details when a user selects a particular station from a list or map view.

Example prompt: Retrieve details for charging resource with ID 'station-123' using GET `/resources/{id}` and confirm the resource exists (200 response)

### Fleet EV Infrastructure Monitoring

Monitor the available EV charging infrastructure for fleet management purposes. The paginated resource listing enables periodic inventory scans to track total station count, identify new additions, and detect removed stations. Combined with scheduled polling, agents can maintain an up-to-date view of the charging network for fleet routing and capacity planning.

Example prompt: List all resources with GET /resources (paginating through all results) and compare the total count against the previous known count to detect network changes

### AI Agent EV Charging Access

Enable AI agents to discover and access EV charging station data through Jentic. Agents search for charging-related operations, receive the authentication and resource schemas, and execute queries without manual API documentation review. Jentic handles credential management for the OAuth client credentials flow, enabling agents to focus on station data retrieval and analysis.

Example prompt: Search Jentic for 'list EV charging stations', load the Powerly resource listing schema, and execute to retrieve available charging infrastructure data

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Get access token via client credentials |
| GET | `/resources` | List charging resources with pagination |
| GET | `/resources/{id}` | Get a specific charging resource by ID |

## Key resources

- **Authentication** — Obtain access tokens using client credentials grant
- **Resources** — List and retrieve EV charging station resources

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 68 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/powerly.app/powerly/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Powerly API by hand means calling its `/auth/token` endpoint to trade client credentials for a token, refreshing that token, and pointing at api.powerly.app yourself. Through Jentic you install once, import the Powerly API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Powerly puts the charging-station id in the URL path (`/resources/{id}`), so a rule can pin your agent to reading station inventory and one station's details and nothing else. You choose the operations it may call, and this spec exposes only read lookups, so no write action is included.
- **Credential handling:** Your Powerly client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list EV charging stations' or 'get details for a charging station', and Jentic returns the matching Powerly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Open Charge Map API** — Open-source global EV charging station directory with community-contributed data
- **DigitalOcean API** — Cloud infrastructure for hosting applications that consume EV charging data
- **Linode API** — Cloud infrastructure for hosting IoT applications that process charging station data

## FAQ

### Why is there no official OpenAPI spec for Powerly API?

Powerly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Powerly 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 Powerly API use?

The Powerly API uses a client credentials flow via POST `/auth/token.` Provide grant_type, client_id, and client_secret in the request body to receive a time-limited access_token. Through Jentic, these credentials are stored encrypted and token acquisition is handled automatically.

### Can I paginate through all charging resources with the Powerly API?

Yes. The GET /resources endpoint accepts limit and offset query parameters. The response includes a total field indicating the full resource count, enabling you to paginate through all available charging stations by incrementing the offset in subsequent requests.

### What are the rate limits for the Powerly API?

Specific rate limits are not documented in the spec. Access tokens obtained from POST `/auth/token` have an expires_in field indicating their validity period. Implement token caching and refresh logic to minimize authentication requests.

### How do I list EV charging stations through the Powerly API using Jentic?

Install the SDK with pip install jentic, then search for 'list EV charging stations'. Jentic returns the GET /resources operation schema with optional limit and offset parameters. Jentic handles authentication automatically, so you can execute directly to receive paginated charging resource data.

### Can I limit what my agent is allowed to do with the Powerly API?

Yes. Because you run Jentic One yourself, your own rules decide which Powerly operations and credentials the agent may use. This spec exposes only read lookups, so you can allow listing charging resources with GET /resources and fetching a single station with GET `/resources/{id}` while blocking everything else. You can also pin the agent to one station id in the path, and no write action exists to grant.