← Back to What we build
18 · URBAN MOBILITY

GridPulse

Concept detail · target pilot

An open-data routing API for local transit and delivery teams that predicts construction and seasonal micro-congestion without commercial mapping trackers.

Why it exists

Local operators often know where bottlenecks form before commercial maps do, but lack a lightweight way to publish that signal.

Pilot workflow

  • Ingest open roadworks and local observations, score route segments, expose a documented API, and measure prediction accuracy by corridor.
  • A local-first, human-readable record of what the system saw and decided.
  • An exportable artifact that a pilot partner can review before wider use.

Prototype boundary

Routing decisions affect safety and service access. Data freshness, accessibility, liability, and incident fallback need operational ownership.

Planned service shape

Target pilot pricing for validation—not a live subscription or promise of availability.

$39/moLocal team · 3 routes
$149/moOperations · 25 routes
$399/moAPI pilot
Discuss a pilot →Bring a use case, a test group, or a data sample. We’ll define the safest first experiment.