Add Navigation API support: Directions, Matrix, and Isochrone
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 66/100
Research direction
Start with the command-generation flow and the vendored specs in openapi/ and custom-openapi/, then compare the linked Mapbox Directions, Matrix, and Isochrone API documentation. Done means the three Navigation API command groups are represented by vendored specs and generated CLI commands can expose their route, matrix, and reachability operations.
Written by the indexing model from the issue text.
Description
Request
Add command groups for the Mapbox Navigation APIs — Directions, Matrix, and Isochrone — so an agent can compute routes, travel-time matrices, and reachability from the terminal.
Why
These answer questions a frontier model fundamentally can't, because they depend on the live road network and traffic:
- Directions — route, distance, and traffic-aware travel time between points. "How long to drive from A to B right now, and which way."
- Matrix — travel times/distances across many origins and destinations at once. "Of these 10 candidates, which is fastest to reach from the office." This is the real "travel time between places" primitive.
- Isochrone — the area reachable within N minutes. "What's within a 15-minute walk." Natural pair with search-along-route and site-selection workflows.
Each produces concrete, checkable output an agent can act on, and none of it is memorizable.
Context
The CLI generates commands from the OpenAPI specs vendored in openapi/ and custom-openapi/. None of the Navigation APIs are vendored today, so the commands don't exist. The README notes upcoming releases will extend coverage to most public APIs — this is a request to prioritize the Navigation three.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapbox/mapbox-cli
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
mapbox/mapbox-cli#30 ·
Maintainers usually reply within 1 day
All issues in mapbox/mapbox-cli
Similar issues
-
A-UI C-Bug S-Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bevyengine/bevy#26330 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
chipsalliance/caliptra-sw#4335 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
aaif-goose/goose#13158 ·
Maintainers usually reply within 1 day
-
agent enhancement provider:anthropic providers triaged
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
can1357/oh-my-pi#17148 · 1 comment ·
Maintainers usually reply within 1 day
-
A-documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
rust-lang/rust-clippy#17926 · 1 comment ·
Maintainers usually reply within 1 day