openydt-evcharge — EV Charging Domain (evcharge)

CRITICAL：MUST use the Read tool to read
../openydt-shared/SKILL.md
before starting (Authentication / Profile / Signature / Status Code / Rate Limiting / Security Rules). Do not execute any commands without reading the shared base.

When to Use This Skill

Use this skill when users need to perform read-only queries/statistics on the EV charging platform, such as listing charging stations under an operator (agent), viewing details of a charging station, checking real-time status of charging piles and gun ports, statistics on operation data of stations/piles (order count, charging electricity, electricity fee/service fee), and querying charging order lists or single order details.

Intent Routing:

For stations: List stations by operator account/mobile number →
```
station-list
```
; View single station details (including operatorName, pileCount) by station code →
```
station-detail
```
.
For charging piles/gun ports →
```
pile-list
```
(returns
```
guns[]
```
gun port status).
For operation data/revenue/electricity →
```
station-statistics
```
(aggregated to each pile by station).
For orders: Use
```
order-list
```
for lists (filtered by time period, optional plotCodes/pileId/useraccount); Use
```
order-detail
```
for single orders (by orderNo).
For parking (non-charging) fee inquiry/payment, parking records/presence, monthly tickets/coupons/devices/blacklists, etc., please use the corresponding parking domain skills [[openydt-billing]] / [[openydt-record]] / [[openydt-park]] / [[openydt-monthticket]] / [[openydt-coupon]] / [[openydt-device]] / [[openydt-list]].
If the charging platform has commands not covered by this skill, use [[openydt-api-explorer]] with
```
openydt api <cmd>
```
as a fallback.

Available Commands

Chinese Name	Command	Read/Write	Key Parameters
Get Charging Station List	`openydt evcharge station-list`	Read	useraccount / mobile (choose one), pageNum, pageSize
Get Charging Station Details	`openydt evcharge station-detail`	Read	plotCode (required)
Get Charging Pile Device List	`openydt evcharge pile-list`	Read	useraccount (required), plotCodes (array, only via --body), pageNum, pageSize
Get Station Operation Data	`openydt evcharge station-statistics`	Read	useraccount (required), plotCodes (array), startDate, endDate (required, ≤30 days), pagination
Get Charging Order List	`openydt evcharge order-list`	Read	startDate, endDate (required, ≤30 days), optional filters: useraccount/plotCodes/pileId, pagination
Get Order Details	`openydt evcharge order-detail`	Read	orderNo (required)

All commands are read-only, no need for
--yes
. The command names have removed redundant domain prefixes (
station-list
instead of
evcharge-station-list
); Original business codes like
evchargeStationList
can still be used as aliases.

Parameter Constraints (from Platform Rules)

```
station-list
```
: At least one of
useraccount
and
mobile
must be passed.
```
plotCodes
```
is an array of station codes: Can only be passed via
```
--body
```
(not a single-value flag); Not passing or passing an empty array means no filtering by stations, default maximum 50.
```
startDate
```
/
```
endDate
```
: Format
```
yyyy-MM-dd HH:mm:ss
```
, interval cannot exceed 30 days (exceeding returns status=2 / resultCode=909 "Query time range cannot exceed 30 days").
Pagination:
```
pageSize
```
maximum 50 (exceeding returns business failure "pageSize cannot be greater than 50"); The command will inject default values
```
pageNum=1
```
/
```
pageSize=10
```
from the catalog document when missing.

Business Process

All operations in the charging domain are read-only queries. The typical link is first locate the operator/station, then drill down to piles and orders, emphasizing using response fields from previous steps as parameters for subsequent steps:

Locate Station: Use
```
station-list
```
(pass
```
--useraccount
```
or
```
--mobile
```
) to get
```
plotCode
```
/
```
plotName
```
of stations; Or directly use
```
station-detail
```
to view details if
```
plotCode
```
is known (returns
```
operatorName
```
,
```
pileCount
```
, longitude/latitude, running status).
Drill Down to Charging Piles: Put the
```
plotCode
```
from Step 1 into the
```
plotCodes
```
array in
```
--body
```
of
```
pile-list
```
(with
```
--useraccount
```
) to get
```
pileId
```
,
```
enabled
```
,
```
runningStatus
```
of each pile and
```
guns[]
```
gun port status.
Operation Statistics:
```
station-statistics
```
(useraccount + plotCodes + time period) aggregates data to each pile by station, providing
```
orderCount
```
/
```
chargeTotalTimes
```
/
```
totalPower
```
/
```
totalAmount
```
/
```
totalElectricFee
```
/
```
totalServiceFee
```
.
Order Analysis:
```
order-list
```
(time period required, can be filtered by
```
plotCodes
```
,
```
pileId
```
,
```
useraccount
```
from Step 1/2) lists orders and gets
```
orderNo
```
; Use
```
order-detail --order-no <orderNo>
```
for single order details.

Field Transfer Points:
plotCode
from
station-list
/
station-detail
→
plotCodes
array in
pile-list
/
station-statistics
/
order-list
(via --body);
pileId
from
pile-list
→
--pile-id
filter in
order-list
;
orderNo
from
order-list
→
--order-no
in
order-detail
.

Quick Reference for Response Fields/Enumerations (prod actual measurement, inconsistent with docking document)

⚠️ The following are actual measurement results from the production environment; The single
orderStatus
English enumeration (PAID/CHARGING…) written in the docking document does not appear in prod. Follow the actual platform measurement; If the platform clarifies later, follow the platform's instructions.

Orders(
```
order-list
```
/
```
order-detail
```
) have two status dimensions:
- ```
chargeStatus
```
  /
```
chargeStatusName
```
  —— Charging status:
```
9002
```
  =Charging,
```
9003
```
  =Completed.
- ```
orderState
```
  /
```
orderStatusName
```
  —— Order status:
```
1
```
  =Ordered,
```
3
```
  =Paid.
- Amount fields(
```
totalAmount
```
  /
```
electricFee
```
  /
```
serviceFee
```
  ) are in "Yuan", electricity
```
chargingPower
```
  is in "kWh",
```
chargingDuration
```
  is in the format like "12min" "1min12sec".
Charging Piles(
```
pile-list
```
):
```
enabled
```
0=Disabled/1=Enabled; Pile
```
runningStatus
```
(original value)0=Running/1=Offline;
```
plotCode
```
is the affiliated station;
```
guns[].status
```
actual measurement 0=Offline / 2=Idle / 4=Plugged in(docking document only provides 2=Idle).
Station Operation(
```
station-statistics
```
):
```
piles[]
```
includes
```
chargeTotalTimes
```
(charging count, not listed in document) and orderCount/totalDuration/totalPower/totalAmount/totalElectricFee/totalServiceFee; recordList items include
```
stationName
```
.

Stations(

station-list

station-detail

runningStatus

1=In Operation/0=Closed;

station-detail

additionally includes

operatorName

pileCount

lng

lat

region

Quick Reference for Error Self-Healing

Phenomenon	Meaning	Recovery Action
resultCode 909 "Query time range cannot exceed 30 days"	Time window of `order-list` / `station-statistics` >30 days	Narrow `startDate` / `endDate` to ≤30 days
Business failure "pageSize cannot be greater than 50"	Pagination exceeds limit	Set `--page-size` ≤ 50
`station-list` reports parameter error	Neither `useraccount` nor `mobile` is passed	Provide at least one
`plotCodes` does not take effect	Passed as a single-value flag	Use `--body '{"plotCodes":["C3CMHJX"]}'` (array can only be passed via body)
Returns empty / nodata	Mostly no business data in the time window, or querying charging in test environment(charging data is currently verified in prod)	Change time window, or add `--env prod` and verify with corresponding prod credentials, not an interface failure

General status/resultCode, exit code, rate limiting retry, signature version refer to [[openydt-shared]]. Charging reuses the same signature authentication(default v2).

Examples

Charging business data is currently verified in prod(test environment may have no charging data); To query prod, add
--env prod
and configure prod credentials. The following are read-only commands, safe. Sample station
C3CMHJX
, operator
DLS001
are actual measured values.

bash

# 1) List charging stations by operator account(choose one: --useraccount or --mobile)
openydt evcharge station-list --useraccount DLS001 --page-size 10

# 2) View single station details(including operator, pile count, running status)
openydt evcharge station-detail --plot-code C3CMHJX

# 3) List charging piles and gun ports in the station(plotCodes is array, must be passed via --body)
openydt evcharge pile-list --body '{"useraccount":"DLS001","plotCodes":["C3CMHJX"],"pageNum":1,"pageSize":10}'

# 4) Station operation data(time period ≤30 days)
openydt evcharge station-statistics --body '{"useraccount":"DLS001","plotCodes":["C3CMHJX"],"startDate":"2026-06-01 00:00:00","endDate":"2026-06-18 23:59:59","pageNum":1,"pageSize":10}'

# 5) Charging order list(time period required, can be filtered by station/pile/operator), get orderNo
openydt evcharge order-list --body '{"plotCodes":["C3CMHJX"],"startDate":"2026-06-01 00:00:00","endDate":"2026-06-18 23:59:59","pageNum":1,"pageSize":10}'

# 6) Single order detail(use orderNo from Step 5 response)
openydt evcharge order-detail --order-no 26061820675194016111704626880659

openydt-evcharge

NPX Install

Tags

SKILL.md Content (Chinese)