AreaMetrics

Busy areas

Know how busy an area is before you take the booking

Go measures demand and supply across a fine geographic grid — H3 hexagons at about 460 m — and learns each area's capacity from your own trip history. Busy-area scores feed booking gates and operator dashboards, so a saturated area is handled before it disappoints a passenger.

• Per-cell demand density

  Every trip's pickup is indexed to an H3 cell (resolution 8, ~0.74 km²). A live busy-score compares current demand against the area's expected capacity.

• Capacity-aware booking gates

  When an area crosses its limits a booking is flagged (default 70%) or blocked (default 90%) — set per fleet, with a warn-only mode that audits what would have been refused.

• Learned, not assumed

  Capacity is learned from a 90-day history and adjusted for how well trips actually went, so limits reflect reality rather than a flat guess. Refreshed every 5 minutes.

Region-scoped demand density (H3)

One region's cells — H3 resolution 8 (~460 m). Illustrative.

Live busy-area metrics, refreshed every 5 minutes. Booking gates warn at 70% and block at 90% utilisation, per fleet. Demand-based surge pricing is on the roadmap — not yet live.

API reference 16 operations · interactive — try them against the sandbox

→

2 features in AreaMetrics

Area Busyness

Single source of truth for "is this area busy?" — consumed by trip gating, per-trip health checks, and operator dashboar

H3 Area Metrics

HTTP API exposing the learned H3-cell metrics: supply density per cell, demand heatmap, capacity-per-hour estimates by z