The head-to-head page shows the category. This one shows the map underneath it: one row per panel point, each operator's live reading beside the others, and a plain call of who can actually serve this area right now — Snabbit, UC InstaHelp or Pronto.
The one thing to settle before reading the table.
Rashmeka's read is right in substance — Verified is the “professional shows up with a camera” add-on, bought and installed by the operator. But two corrections:
1. It is called “Verified”, not “Gold”. Gold is an Urban Company tier (our panel scrapes UC gold_start). Pronto's public price ladder has no Gold — only list-vs-effective, e.g. Hourly Service ₹125 list → ₹30 effective. Pronto Verified is a separate add-on listing (id 75, ₹199 / 90 min, undiscounted).
2. The ₹10–20 premium is unverified. The customer price we can see is the ₹199 add-on SKU, not a per-visit uplift. The admin app runs a full ProntoVerifiedPage that validates camera devices, uploads recordings tagged cameraId + bookingId, warns when a file “was recorded on a different camera”, and flags hubs as “Includes Pronto Verified” — so the camera story is solid; the exact pricing uplift is not something the data shows.
Our panel can't count Verified adoption per area — it's booking-scoped and needs auth, and we store aggregates only. So it stays a catalogue fact, not a column below.
One row per panel point. Busy% is Snabbit's live fleet tied up; sold% is Pronto's published slot grid already sold out — different measures, never averaged. unknown means the probe got no answer, not that the area is closed.
The same 31 fixed panel points, one facet per operator. Filled = a same-day signal (free runner / serving today / a slot dated today); hollow = present but no same-day slot; grey = not serviceable; a ring = this operator is one of the area's same-day leads. Bubble size is depth where published (Snabbit fleet, Pronto slots); UC publishes no depth, so its dots are a fixed size.
Leads today uses only each operator's own same-day signal — no blended score, because the three publish different units (runners vs slots vs a tier price) and a single number across them would be invented, not measured. Presence, depth and price are shown side by side instead. A point where an operator is live but publishes no same-day signal reads “—” here; that is a flag, not a verdict — the raw columns are beside it. Pronto is SCHEDULED-only, so when it is bookable only from tomorrow it is shown as a dated hint, never a lead. Full method in docs/area-view.md; raw rows in area_view.csv.