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
$0.003 asked in its payment challenge on 18 Nov 2026
curl -i -X POST 'https://ort.halowerk.com/v1/departures-planned' \
-H 'Content-Type: application/json' \
-d '{"stop":{"name":"Köln Hbf"},"time":"08:00","limit":10,"duration_min":15}'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/broadband-check$0.005Reads the 100 m grid layers of the Breitbandatlas of the Bundesnetzagentur (Gigabit-Grundbuch WMS, data status 12/2025 per service documentation v3.0) at the point. The WMS offers no feature info, so each layer is rendered as a 21 × 21 m map window (1 m per pixel) in ETRS89/UTM32 and the colour of the centre pixel is mapped with the service legend to the availability class (0–10 %, >10–50 %, >50–75 %, >75–95 %, >95 % of households or businesses in the cell).
Example
curl -i -X POST 'https://ort.halowerk.com/v1/broadband-check' \ -H 'Content-Type: application/json' \ -d '{"lat":52.493,"lon":13.295}' - POST/building-footprint$0.005Queries the ALKIS building layer (GebaeudeBauwerk of the open "ALKIS vereinfacht" WFS; covered: Brandenburg, Mecklenburg-Vorpommern, Sachsen, Sachsen-Anhalt, Thüringen, Hamburg, Niedersachsen, Nordrhein-Westfalen, Hessen, Rheinland-Pfalz) in ETRS89/UTM, returns buildings containing the point or within the radius with footprint area and perimeter (scale-corrected), building function, name, number of storeys above ground where recorded and the address text.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/building-footprint' \ -H 'Content-Type: application/json' \ -d '{"lat":50.94128,"lon":6.95826}' - POST/deutschlandticket-fit$0.008Runs the own RAPTOR router twice over the national planned timetable: once with all services and once restricted to services covered by the Deutschlandticket. Classification by the Deutschlandticket tariff rules (deutschlandticket.de, 2026): local and regional transport inside Germany is included; DB long-distance (ICE/IC/EC), FlixTrain/FlixBus, night and other long-distance trains and coaches are excluded; ferries, cable cars, funiculars, heritage/tourist railways and unclear foreign train…
Example
curl -i -X POST 'https://ort.halowerk.com/v1/deutschlandticket-fit' \ -H 'Content-Type: application/json' \ -d '{"to":{"name":"Bonn Hbf"},"from":{"name":"Köln Hbf"},"time":"08:00","max_transfers":1}' - POST/facade-sun-hours$0.005Computes the sun position every 5 minutes over a whole year with the NOAA solar position equations (Spencer 1971 Fourier series for declination and equation of time, accuracy about 0.1°) plus Bennett refraction, and counts the time in which the sun is above the horizon (or a given obstruction / horizon profile) and in front of the vertical facade (angle between sun azimuth and facade normal below 90°).
Example
curl -i -X POST 'https://ort.halowerk.com/v1/facade-sun-hours' \ -H 'Content-Type: application/json' \ -d '{"lat":52.52,"lon":13.405,"facade_azimuth_deg":180}' - POST/gtfs-validate$0.005Static validation against the GTFS Schedule reference (gtfs.org): required files (agency, stops, routes, trips, stop_times, calendar or calendar_dates) and columns, empty required fields, duplicate keys, foreign keys (agency, route, service, trip, stop, parent_station), location_type rules, route_type values (base and extended), colours, URLs, IANA time zones, YYYYMMDD dates and ranges, HH:MM:SS times, stop_time order and arrival/departure consistency, implausible speeds between consecutive…
Example
curl -i -X POST 'https://ort.halowerk.com/v1/gtfs-validate' \ -H 'Content-Type: application/json' \ -d '{"files":{"stops.txt":"stop_id,stop_name,stop_lat,stop_lon\nS1,Markt,50.9413,6.9583\nS2,Bahnhof,50.9430,6.9589\n","trips.txt":"route_id,service_id,trip_id\nR1,WK,T1\n","agency.txt":"agency_id,agency_name,agency_url,agency_timezone\nA,Demo Bus,https://example.org,Europe/Berlin\n","routes.txt":"route_id,agency_id,route_short_name,route_type\nR1,A,1,3\n","calendar.txt":"service_id,monday,tuesday,wednesday,thursday,friday,saturday,sunday,start_date,end_date\nWK,1,1,1,1,1,0,0,20260101,20301231\n","stop_times.txt":"trip_id,arrival_time,departure_time,stop_id,stop_sequence\nT1,08:00:00,08:00:00,S1,1\nT1,08:04:00,08:04:00,S2,2\n"}}' - POST/heavy-rain-hazard$0.005Queries the BKG Hinweiskarte Starkregengefahren (HWK_SRG, product status 2024, 1 m raster, dl-de/by-2-0) for the Land of the point: 2D hydrodynamic simulation on DGM1 without sewer system and infiltration for an exceptional event (100-year, KOSTRA-DWD 2020; Rhineland-Palatinate SRI 7) and an extreme event (100 mm/h, NRW 90 mm/h; Rhineland-Palatinate SRI 10; Saarland only exceptional).
Example
curl -i -X POST 'https://ort.halowerk.com/v1/heavy-rain-hazard' \ -H 'Content-Type: application/json' \ -d '{"lat":51.2562,"lon":7.1508}' - POST/heritage-check$0.005Queries the open monument WFS services where they exist with an open licence: Berlin (Denkmalkarte, Landesdenkmalamt, all monument types incl. Bodendenkmale, dl-de/zero-2-0), Hamburg (Denkmalkartierung of the Denkmalschutzamt incl. ensembles and UNESCO world heritage zones, dl-de/by-2-0) and Cologne (Denkmalliste of the Stadtkonservator, dl-de/zero-2-0).
Example
curl -i -X POST 'https://ort.halowerk.com/v1/heritage-check' \ -H 'Content-Type: application/json' \ -d '{"lat":53.5503,"lon":9.9925,"radius_m":0}' - POST/isochrone$0.008Travel time map: return the reachable area on the local road graph. Use it when an agent needs a bounded location accessibility estimate.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/isochrone' \ -H 'Content-Type: application/json' \ -d '{"lat":52.52,"lon":13.405,"mode":"foot","minutes":[5,10],"max_points":1000}' - POST/journey-plan$0.008Public transport route: return planned journeys from the available timetable. Use it when an agent needs a transit connection.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/journey-plan' \ -H 'Content-Type: application/json' \ -d '{"to":{"name":"Bonn Hbf"},"from":{"name":"Köln Hbf"},"time":"08:00","results":1}' - POST/land-value-boris$0.005Looks up the Bodenrichtwert zone containing the point in the open BORIS services of the Länder: Berlin (WFS Bodenrichtwerte 01.01.2026, dl-de/zero-2-0), Lower Saxony (BORIS.NI WFS, VBORIS/BRM model, dl-de/by-2-0; only the most recent reference date is returned) and North Rhine-Westphalia (BORIS-NRW WMS GetFeatureInfo on all zone layers, current reference date, dl-de/zero-2-0).
Example
curl -i -X POST 'https://ort.halowerk.com/v1/land-value-boris' \ -H 'Content-Type: application/json' \ -d '{"lat":52.3745,"lon":9.7386}' - POST/last-departure$0.004Evaluates the service date from 12:00 on: all trips of that service day (GTFS times beyond 24:00 included) plus trips of the following service day leaving before 04:00. Per line and headsign the last departure, plus all departures after midnight (night service). With a destination, finds the last direct trips (no transfer) that call at the destination after the origin, with arrival time. 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/last-departure' \ -H 'Content-Type: application/json' \ -d '{"to":{"name":"Köln Hbf"},"stop":{"name":"Bonn Hbf"},"limit":5,"modes":["rail"]}' - POST/mobile-coverage$0.005Reads the 100 m grid coverage layers of the Mobilfunk-Monitoring in the Breitbandatlas of the Bundesnetzagentur (WMS, data status 12/2025 per service documentation v3.0) for every operator and technology plus "all operators". The WMS offers no feature info, so each layer is rendered as a 21 × 21 m window (1 m per pixel) around the point in ETRS89/UTM32; a coloured centre pixel means the operator reports coverage in that cell, transparent means no reported coverage.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/mobile-coverage' \ -H 'Content-Type: application/json' \ -d '{"lat":50.94128,"lon":6.95826}' - POST/municipality-name-to-coordinates$0.002Geocoding municipality names: return official German municipality reference coordinates. Use it when an agent needs mapped data. Germany municipality reference points only.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/municipality-name-to-coordinates' \ -H 'Content-Type: application/json' \ -d '{"query":"Berlin"}' - POST/osm-category-nearby$0.002Nearby places: return German OSM objects by type. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-category-nearby' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"category":"amenity=atm","radius_m":500}' - POST/osm-place-category-facets$0.002Place category counts: return the mapped category distribution around a German location. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-category-facets' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"radius_m":500}' - POST/osm-place-contact-coverage$0.002Place data completeness: return address, website and opening-hours coverage for a local category. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-contact-coverage' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"category":"amenity=cafe","radius_m":500}' - POST/osm-place-hours-text-search$0.002Opening hours search: return OSM schedule matches. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-hours-text-search' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"query":"24/7","radius_m":500}' - POST/osm-place-identifier-facts$0.002Place details by OSM ID: return mapped object facts within a supplied local area. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-identifier-facts' \ -H 'Content-Type: application/json' \ -d '{"osm_id":"way/75472593"}' - POST/osm-place-nearest-per-category$0.002Nearest places: return the closest German OSM object per type. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-nearest-per-category' \ -H 'Content-Type: application/json' \ -d '{"lat":52.517,"lon":13.4,"radius_m":500,"categories":["amenity=atm"]}' - POST/osm-place-search$0.002Places search: return German OSM business matches. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-search' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"query":"atm","radius_m":500}' - POST/osm-place-shared-website-groups$0.002Place identity evidence: return mapped objects sharing an exact normalized website in a local area. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-shared-website-groups' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"radius_m":500}' - POST/osm-place-website-directory$0.002Business website directory: return mapped business websites grouped by their public host. Use it when an agent needs mapped data.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/osm-place-website-directory' \ -H 'Content-Type: application/json' \ -d '{"area":"Berlin","limit":1,"query":"cafe","radius_m":500}' - POST/parcel-geometry$0.005Queries the open "ALKIS vereinfacht" WFS of the Land (AdV product specification 2.0; Thuringia 1.0) or the Berlin ALKIS parcel WFS with a 1 m box around the point in ETRS89/UTM, selects the parcel that contains the point (even-odd rule over all rings) and returns the Flurstückskennzeichen, Gemarkung with key, Flur, parcel number (Zähler/Nenner), the official area (amtliche Fläche), the area and perimeter computed from the delivered boundary (corrected for the UTM scale factor), the address…
Example
curl -i -X POST 'https://ort.halowerk.com/v1/parcel-geometry' \ -H 'Content-Type: application/json' \ -d '{"lat":50.94128,"lon":6.95826,"include_geometry":false}' - POST/planar-grid-cell-occupancy$0.005Return half-open grid cell assignments, occupancy and boundary-point witnesses. Cartesian coordinates only; no map fetch or CRS conversion.
Example
curl -i -X POST 'https://ort.halowerk.com/v1/planar-grid-cell-occupancy' \ -H 'Content-Type: application/json' \ -d '{"origin":[0,0],"points":[[0,0],[1,1],[9.9,0],[-0.1,0]],"cell_size":10}'
A dash means the listing gives no price or method. {Braces} mark a value you fill in. Copy buttons copy an example URL.
Showing 25 of 44 endpoints. Next 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.