Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces SearchapiKey3 EndpointsREST
For Agents
Look up EV charging station locations, connector types, and user-contributed content across North American networks. Useful for trip-planning, fleet routing, and EV ownership agents.
Use for: Find all EV chargers within 5 miles of a given coordinate, List DC fast chargers along a planned highway route, Get user-submitted photos for a specific charging station, Check whether the ChargeHub API is currently operational
Not supported: Does not handle initiating a charging session, payments to charger operators, or vehicle telemetry - use for read-only EV charger discovery and community content only.
ChargeHub maintains one of the largest public databases of EV charging stations in North America, covering Level 2 and DC fast chargers across all major networks. The API exposes three read endpoints: a service status check, a points-of-interest lookup that returns charging stations and their connector details, and a user-content endpoint for community-supplied photos and check-ins. It is intended for trip planners, EV navigation apps, and fleet routing tools that need accurate, network-agnostic charger data without scraping individual operator sites.
Install Jentic One Beta
Connect the ChargeHub API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChargeHub 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchargehub.com%2Fchargehub" | sh2
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%2Fchargehub.com%2Fchargehub" | 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 ChargeHub API.
Check ChargeHub service health via GET /api/status before issuing larger queries
Search EV charging stations by geographic bounds with GET /api/poi to power map and list views
Filter points of interest by connector type, network operator, or charging speed parameters in the poi query
Pull user-contributed content (photos, station notes) for a specific point of interest with GET /api/user-content
Combine poi and user-content responses to build station detail pages in EV apps and dashboards
Use Cases
Patterns agents use ChargeHub API for, with concrete tasks.
★ EV Trip Planner Charger Lookup
EV trip planning apps query GET /api/poi with a bounding box that follows the user's route to surface every available charger along the way, including connector type and charging speed. Pairing the response with the planner's own routing logic gives drivers a network-agnostic view of charging options without integrating with each operator individually.
GET /api/poi with a bounding box covering the planned route and filter the response to DC fast chargers
EV Navigation App
In-car and mobile EV navigation apps render a live charger layer by polling /api/poi for the visible map area and overlaying ChargeHub's connector and network metadata. The /api/user-content endpoint adds qualitative context - recent photos, broken-station reports, and check-ins - that helps drivers pick a charger that will actually work when they arrive.
GET /api/poi for the current map bounding box and GET /api/user-content for the top three results to render station cards
Fleet Routing and Operations
Commercial EV fleet operators feed ChargeHub data into routing engines so vehicles are dispatched with reliable charging waypoints. The /api/poi endpoint returns connector counts and network operator metadata, which feeds into route-cost calculations and SLA-aware scheduling. Status checks via /api/status keep the integration's health-check loop honest.
GET /api/poi for waypoint candidates near each delivery stop and select chargers with at least 2 available DC fast connectors
Conversational EV Assistant via Jentic
An EV-focused AI assistant given a question like 'where can I charge my CCS car near Lake Tahoe' can resolve the lookup through Jentic. It searches Jentic for the charger search operation, runs /api/poi for the relevant bounding box, and surfaces the best results - without holding the ChargeHub API key directly.
Search Jentic for 'find ev charging stations near a location', call /api/poi for the area, and return the top CCS results
Key Endpoints
3 endpoints — chargehub maintains one of the largest public databases of ev charging stations in north america, covering level 2 and dc fast chargers across all major networks.
METHOD
PATH
DESCRIPTION
GET
/api/status
Check API service health
GET
/api/poi
Search EV charging stations by bounding box and filters
GET
/api/user-content
Retrieve user-contributed content for a charging station
GET
/api/status
Check API service health
GET
/api/poi
Search EV charging stations by bounding box and filters
GET
/api/user-content
Retrieve user-contributed content for a charging station
Jentic AI Readiness Score
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.
C
ChargeHub API
- Foundational (D+)49/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
52%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ChargeHub API by hand means passing the api_key in the query string on every request, where it can leak into browser logs and referrers, and building the POI query parameters yourself. Through Jentic you install once, import ChargeHub from the API Directory, store the key once, and your agent calls it.
Permission scoping
The ChargeHub API is read-only over charger discovery and community content, so limit the agent to the operations it needs, such as finding charging stations near a location. You choose which operations it may call, and the API exposes no session or payment operations to grant.
Credential isolation
Your ChargeHub api_key is stored once, encrypted, by your own Jentic One instance and appended to the request at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find EV charging stations near a location', and Jentic returns the matching ChargeHub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ChargeHub API through Jentic.
What authentication does the ChargeHub API use?
ChargeHub uses an API key passed as the api_key query parameter on every request. Through Jentic, the key is held in your Jentic One instance and only attached server-side at execution, so it never appears in agent-visible URLs.
Can I search for EV chargers within a bounding box with the ChargeHub API?
Yes. GET /api/poi accepts geographic bounds and returns a list of charging stations with their network operator, connector types (CCS, CHAdeMO, J1772, NACS), and charging speeds. You can filter the response client-side to narrow by connector or network.
How do I retrieve user-contributed photos and notes for a charging station?
Call GET /api/user-content with the station identifier returned from /api/poi. The response includes community-uploaded photos, check-in notes, and reported issues that supplement the structured charger metadata.
What are the rate limits for the ChargeHub API?
ChargeHub does not publish a fixed public rate limit; usage is tied to the partner key issued at sign-up. Cache /api/poi responses by bounding box and rely on /api/status for periodic health checks rather than per-request probes.
How do I look up EV chargers near a location through Jentic?
Install jentic with pip install jentic, search for 'find ev charging stations', load the schema for GET /api/poi, and execute with the bounding box. Run Jentic One, the self-hosted execution layer, to issue an agent API key.
Does the ChargeHub API include charger pricing and live availability?
The /api/poi endpoint returns station metadata such as connector type, network operator, and charging speed. Live in-use status and per-network pricing are limited and depend on what the operator shares with ChargeHub; expect reliable static data and partial real-time signals.
Can I limit what my agent is allowed to do with the ChargeHub API?
Yes. Because you run Jentic One self-hosted, your own rules decide which ChargeHub operations the agent may call, so you can allow only charger discovery through GET /api/poi and deny the rest. The API is read-only and exposes just three operations (service status, points-of-interest lookup, and user-contributed content), with no session or payment operations to grant, so the agent can never initiate a charge or move money. Your api_key stays stored on your instance and is attached only at execution, never in the agent's prompt or context.
GET STARTED