Command-line tool and TypeScript library

`ladesaeulen`

A dependency-light TypeScript client + CLI for the Ladesäulenregister — the Bundesnetzagentur’s register of public EV charging stations in Germany (about 116,000 Ladeeinrichtungen as of September 2026). Backed by a public ArcGIS FeatureServer. A bund.dev API.

Version 0.0.5 npm GitHub API reference

Install

Needs Node.js 20 or newer. Installs the ladesaeulen command:

npm i -g @maschinenlesbar.org/ladesaeulenregister-cli

Access

No account, no API key, no configuration — install and query.

Quick start

# (counts as of 2026-09-15)
ladesaeulen stations --count                                   # total public stations → 116343
ladesaeulen stations --where "Ort='Berlin' AND Typ='Schnellladeeinrichtung'" --count   # → 695
ladesaeulen stations --near 52.52,13.405 --radius 1 --count    # within 1 km of a point → 127
ladesaeulen stations --where "state='Bayern'" --limit 20       # a page of stations
ladesaeulen stations --geojson --limit 200 > stations.geojson  # GeoJSON for a map
ladesaeulen count-by state                                     # stations per Bundesland
ladesaeulen fields                                             # the queryable columns

Commands

stations

Search charging stations (Ladeeinrichtungen)
count-by

Count stations grouped by a field, e.g. `count-by state` (per Bundesland)
fields

List the queryable field names (for --where / --fields / count-by)

All commands, arguments and options →

Claude Code skills

The ladesaeulen plugin teaches Claude to use ladesaeulen. Install it from the maschinenlesbar.org marketplace:

/plugin marketplace add maschinenlesbar-org/plugins
/plugin install ladesaeulen@maschinenlesbar

/ladesaeulen:ladesaeulen-near
/ladesaeulen:ladesaeulen-search
/ladesaeulen:ladesaeulen-stats

What the skills answer, with real examples → Skill descriptions and requirements →

TypeScript library

@maschinenlesbar.org/ladesaeulenregister-cli is also a typed API client you can import in your own code, with no runtime HTTP dependencies.

API reference → Library usage and architecture →

The tool, not the data

The data comes from the provider behind the API, under its own terms — see DATA_LICENSE.md. The code is dual-licensed AGPL-3.0-or-later or commercial — see LICENSING.md.