Germany station departure board
● Livehalowerk.com
Departure board from the planned national timetable: all platforms of the station (GTFS parent_station) are combined, trips are filtered by their service calendar for the requested date (including trips of the previous service day after midnight), stops without boarding (pickup_type 1) and the terminus of a trip are excluded. Planned timetable from the gtfs.de Germany feed (free edition, CC BY 4.0, based on DELFI e.V.
- Price
- $0.003
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 4 of 4 checks
Endpoints
43 more endpoints · on x402 Bazaar
Checks and payment terms on this page refer to the first endpoint's example. Other endpoints have not been checked individually.
Base URLhttps:
- POST/planar-linear-reference-slice$0.005Return a polyline subsection between two supplied cumulative planar stations. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-linear-reference-slice' \ -H 'Content-Type: application/json' \ -d '{"end":15,"line":[[0,0],[10,0],[10,10]],"start":5}' - POST/planar-lines-endpoint-stitch$0.005Return maximal endpoint-connected line chains with branch-vertex witnesses. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-lines-endpoint-stitch' \ -H 'Content-Type: application/json' \ -d '{"lines":[[[0,0],[1,0]],[[2,0],[1,0]],[[2,0],[3,1]]]}' - POST/planar-polygon-hole-membership$0.005Return inside, outside, hole or boundary membership for points against supplied planar rings. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-polygon-hole-membership' \ -H 'Content-Type: application/json' \ -d '{"holes":[[[3,3],[7,3],[7,7],[3,7],[3,3]]],"outer":[[0,0],[10,0],[10,10],[0,10],[0,0]],"points":[[1,1],[5,5],[3,5],[12,5]]}' - POST/planar-polygon-signed-moments$0.005Return signed area, centroid and planar second area moments of a closed polygon ring. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-polygon-signed-moments' \ -H 'Content-Type: application/json' \ -d '{"ring":[[0,0],[4,0],[4,2],[0,2],[0,0]]}' - POST/planar-polyline-offset-miter-joins$0.005Return left-offset line joins with miter-limit bevel witnesses for an open planar chain. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-polyline-offset-miter-joins' \ -H 'Content-Type: application/json' \ -d '{"line":[[0,0],[10,0],[10,10]],"offset":1,"miter_limit":4}' - POST/planar-polyline-station-projection$0.005Return nearest segment, projected coordinate, station and offset for each supplied point. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-polyline-station-projection' \ -H 'Content-Type: application/json' \ -d '{"line":[[0,0],[10,0],[10,10]],"points":[[3,4],[12,5]]}' - POST/planar-ring-self-intersections$0.005Return nonadjacent ring-edge intersections and collinear overlap witnesses. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-ring-self-intersections' \ -H 'Content-Type: application/json' \ -d '{"ring":[[0,0],[4,4],[0,4],[4,0],[0,0]]}' - POST/planar-shared-boundary-length$0.005Return shared collinear line portions and total common boundary length between two supplied chains. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-shared-boundary-length' \ -H 'Content-Type: application/json' \ -d '{"left":[[0,0],[10,0]],"right":[[3,0],[7,0],[7,2]]}' - POST/planar-snap-topology-collisions$0.005Return distinct vertices merged by grid snapping and edges collapsed to zero length. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-snap-topology-collisions' \ -H 'Content-Type: application/json' \ -d '{"grid":1,"edges":[[0,1],[1,2]],"vertices":[[0.1,0.1],[0.2,0.2],[1.2,0]]}' - POST/protected-areas$0.005Queries the WFS of the Bundesamt für Naturschutz (BfN Schutzgebiete, compiled from the Länder nature conservation authorities, used under GeoNutzV) with a bounding box around the point in ETRS89/UTM32 and computes for every returned area whether the point lies inside (even-odd rule over all rings) and the planar distance to its boundary in metres.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/protected-areas' \ -H 'Content-Type: application/json' \ -d '{"lat":50.69,"lon":7.21,"radius_m":500,"categories":["nature_reserve","natura2000_habitats"]}' - POST/radon-area$0.003Offline lookup of the municipalities designated as Radon-Vorsorgegebiete by the Länder under § 121 StrlSchG / § 153 StrlSchV, as compiled by the Bundesamt für Strahlenschutz (BfS overview, status 15 June 2021, based on the Länder official gazettes; designations are reviewed at least every ten years). Listed names were matched to AGS keys of BKG VG250 01.01.2026; Verbandsgemeinden listed as a whole (Sachsen-Anhalt) are expanded to their member municipalities, the whole Landkreis Wunsiedel i.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/radon-area' \ -H 'Content-Type: application/json' \ -d '{"lat":50.5946,"lon":12.6413}' - POST/reverse-geocode-batch$0.002Reverse geocoding: return nearest official Berlin address points for supplied coordinates. Use it when an agent needs bounded address candidates.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/reverse-geocode-batch' \ -H 'Content-Type: application/json' \ -d '{"points":[{"lat":52.52,"lon":13.405}],"max_candidates":3,"max_distance_m":100}' - POST/route-shape$0.004Public transport route geometry: return the line shape from the available timetable. Use it when an agent needs a transit route on a map.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/route-shape' \ -H 'Content-Type: application/json' \ -d '{"line":"S11","stop":{"name":"Köln Hbf"},"max_variants":2}' - POST/service-frequency$0.004Counts all scheduled departures of the station (all platforms) on the service date by hour (00–27 incl. after-midnight trips of that service day) and by time band (early 04–06, morning peak 06–09, day 09–16, afternoon peak 16–19, evening 19–22, night 22–04). Per line and headsign: trips, first/last departure, median and maximum headway in minutes between 06:00 and 20:00. Planned timetable from the gtfs.de Germany feed (free edition, CC BY 4.0, based on DELFI e.V.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/service-frequency' \ -H 'Content-Type: application/json' \ -d '{"stop":{"name":"Bonn Hbf"},"modes":["rail"]}' - POST/stops-nearby$0.003Radius search over all served stops in the national German timetable with an R-tree index; platforms are grouped into their parent station (GTFS parent_station). For each station: GTFS stop_id, name, position, distance to the nearest served platform, number of platforms, modes and line names with operator. Planned timetable from the gtfs.de Germany feed (free edition, CC BY 4.0, based on DELFI e.V.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/stops-nearby' \ -H 'Content-Type: application/json' \ -d '{"lat":50.943,"lon":6.9589,"radius_m":300}' - POST/surroundings-profile$0.005Searches a dated OpenStreetMap extract for Germany (Geofabrik germany-latest.osm.pbf, data until 2026-11-12, filtered with osmium and stored locally; ODbL 1.0) for 17 everyday categories around the point. Areas (e.g. school grounds, parks) are represented by their area-weighted centroid; objects mapped twice (point and area with the same name less than 150 m apart) are counted once.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/surroundings-profile' \ -H 'Content-Type: application/json' \ -d '{"lat":50.94128,"lon":6.95826,"radius_m":500,"categories":["school","supermarket","pharmacy"]}' - POST/transfer-risk$0.004Finds the arriving trip (line, planned arrival) and the departing trip (line, planned departure) at the station in the national planned timetable, measures the straight-line distance between the two platform positions, estimates the walking time (×1.3 detour, 1.2 m/s) plus a generic minimum transfer of 2 minutes, and classifies the remaining margin: below 0 min infeasible, 0–2 min high, 2–5 min medium, over 5 min low; rail-to-rail transfers under 5 minutes buffer are raised one class because…
Example
curl -i -X POST 'https://ort.halowerk.com/v1/transfer-risk' \ -H 'Content-Type: application/json' \ -d '{"arrival":{"line":"RB48","time":"12:22"},"station":{"name":"Köln Hbf"},"departure":{"line":"S12","time":"12:30"}}' - POST/walkability-de$0.008Runs a 20-minute walking search (4.8 km/h) on HALOWERK's own OpenStreetMap foot network (data until 2026-11-12, ODbL) and computes the network walking time to every point of interest of 17 categories (HALOWERK OSM extract, same date), each snapped to the nearest walkable way within 150 m with the straight access walk added.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/walkability-de' \ -H 'Content-Type: application/json' \ -d '{"lat":53.5511,"lon":9.9937}' - POST/zoning-plans$0.005Queries the open plan registers of Berlin (WFS bplan of the Senatsverwaltung für Stadtentwicklung: plans in force, in procedure and repealed, dl-de/zero-2-0) and Hamburg (WFS Bebauungspläne: adopted plans incl. Baustufenpläne and plans in procedure from PROSIN, dl-de/by-2-0) with a box around the point in ETRS89/UTM32 and computes for each plan area whether the point lies inside and its distance.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/zoning-plans' \ -H 'Content-Type: application/json' \ -d '{"lat":52.5096,"lon":13.376}'
A dash means the listing gives no price or method. {Braces} mark a value you fill in. Copy buttons copy an example URL.
Showing 19 of 44 endpoints. First endpoints
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/ort.halowerk.com
Recent checks
- Median response
- 472 ms
- Last checked
- 18 Nov, 09:25 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 4 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 18 Nov, 09:25 UTC | Live | 402 | 378ms |
| 16 Nov, 21:23 UTC | Live | 402 | 507ms |
| 15 Nov, 09:22 UTC | Live | 402 | 817ms |
| 13 Nov, 18:26 UTC | Live | 402 | 436ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 18 Nov, 09:25 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does ort.halowerk.com advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.