Claude to map apartments and nearby amenities
A student preparing to move to Dallas for a first job built NestMap with Claude Code. The aim was to see apartments alongside the everyday surroundings that matter after a move: the office, grocery stores, restaurants and bars.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a relocation map with real rentals, my office address and toggles for groceries, restaurants and bars. Implement the map, listing details and amenities separately; show coverage gaps and API usage.
Reach people exploring AI agents
See placements →What happened
The author reports a working apartment-and-amenities map, with listing gaps and an API-call limit preventing public release.
Reported by truett31516How the agent did it
- Specify relocation filters and the office address before implementing the map.
- Build listings, a detail panel and amenity toggles in separate phases.
- Review data coverage and API usage before sharing the prototype.
Where a person stepped in
The author specified the architecture and tested data providers; no completed lease or automated housing decision is described.
A student preparing to move to Dallas for a first job built NestMap with Claude Code. The aim was to see apartments alongside the everyday surroundings that matter after a move: the office, grocery stores, restaurants and bars.
The build was divided into three phases. An onboarding form collected the target city, budget, room requirements, moving timeline and office address. Mapbox handled the map and geocoding, while RentCast supplied real rental listings. A second phase added the listing detail panel, followed by a third layer of nearby points of interest.
The author reports a working prototype, with an apartment sidebar and toggles for local amenities. The limitations are equally concrete. RentCast lacked the coverage of major property sites and did not consistently provide property names. Several location-data providers left gaps in the nightlife layer. The author also tried Yelp but could not complete its verification process.
API allowance constrained sharing: forty of fifty free RentCast calls had already been used, so the prototype was not made publicly available. The result is a built relocation-discovery tool, not a documented lease or proof of accurate commute savings. It shows why a map can make a housing search more understandable while still depending on the underlying listing and local-business data.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: busn4400.wordpress.com · truett31516
Frequently asked questions
Why collect the office address first?
The author wanted apartment browsing framed around the workplace rather than judging a listing only in isolation.
What data was missing?
RentCast coverage and property names were incomplete, and point-of-interest providers also had gaps.
Why was it not publicly released?
The author had used forty of the fifty free RentCast calls during development.
More details
About this account
Claude Code generated and debugged the prototype across the author's three planned implementation phases.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: truett31516
Source published 19 Apr 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Mapbox · RentCast · Vercel
Apartment discovery · Relocation map · Listing coverage
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.