Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add Places API (Details) support: photos, busyness, and stable place IDs

Closed
#74 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
api, cli

Research direction

Start by reading the existing mapbox search forward and search category command implementations, especially how they expose mapbox_id. Then review the Mapbox Places Details API material linked in the request and determine the response shape for the proposed command. Done means a mapbox places details <mapbox_id> command returns photos, busyness, business attributes, and stable place IDs.

Written by the indexing model from the issue text.

Description

enhancement

Request

Add a command group for the Mapbox Places API — specifically the Details endpoint — so the CLI can return the enriched per-POI data that a coding agent can't get anywhere else: photos, busyness/popularity, business attributes, and stable place IDs.

Why

The CLI's headline pitch is giving an agent knowledge it doesn't have. Today the richest thing search returns is open hours, phone, and website — good, but the data that's genuinely unique to Mapbox lives behind the Places API and isn't reachable:

  • Photos — high-quality photos via direct URLs (per the blog). An agent could render or link a place's photo.
  • Busyness — a 0–100 activity score by hour and day of week. An agent could answer "is it busy right now" or chart the week's curve. Nothing else in the CLI exposes this, and no frontier model has it.
  • Business attributes — cuisine, accessibility, seating, Wi-Fi, entrance vs. vehicle arrival points.
  • Stable place IDs — persistent UUID anchors that survive data updates, so saved references don't break.

These are the demos that actually show the CLI's value. Geocoding a known address doesn't — the models already have it.

How it fits what's already here

The loop is half-built. mapbox search forward / search category already return a mapbox_id on every feature. The Places Details endpoint (public preview) takes exactly that mapbox_id and returns the enriched record. So this is a natural next command, e.g.:

# today: Search Box returns the id
mapbox search forward --q "Blue Bottle Coffee" --proximity -122.4194,37.7749 --limit 1
# -> properties.mapbox_id = "dXJuOm1ieHBvaToxZTM5YzE5Ny0..."

# proposed: Places Details enriches it
mapbox places details dXJuOm1ieHBvaToxZTM5YzE5Ny0...
# -> photos[], busyness, attributes, stable id
Dominant language
Rust
Stars
15
Forks
2
Avg merge
1d 15h
Merged PRs (30d)
43

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/mapbox-cli

All issues in mapbox/mapbox-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.