Powerly App Powerly API
★ Only Publicly Available OpenAPI DocumentIOTDevice ManagementapiKey3 EndpointsREST
For Agents
Access and manage EV charging station network resources. Authenticate with client credentials, list available charging resources, and retrieve individual station details.
Use for: I need to list all available EV charging stations, I want to get details about a specific charging station, Retrieve an access token for the Powerly API, Find charging resources with pagination
Not supported: Does not handle charging session initiation, payment processing, or real-time availability updates — use for charging station inventory and details only.
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.
Install Jentic One Beta
Connect the Powerly API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Powerly 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Powerly API.
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
Patterns agents use Powerly API for, with concrete tasks.
★ 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.
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.
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.
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.
Search Jentic for 'list EV charging stations', load the Powerly resource listing schema, and execute to retrieve available charging infrastructure data
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for powerly api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Powerly client credentials (client_id and client_secret) are stored encrypted in the Jentic vault (MAXsystem). Token acquisition via POST /auth/token is handled automatically — agents never see raw secrets.
Intent-based discovery
Agents search by intent (e.g., 'list EV charging stations') and Jentic returns matching Powerly operations with their input schemas, so the agent can access charging data without navigating API documentation.
Time to first call
Direct Powerly integration: 2-4 hours for auth flow and pagination handling. Through Jentic: under 15 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Powerly API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED