local-places

Search nearby places through a local Google Places API proxy.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/tamireslaeao-prog/ONI_V30 --skill local-places-tamireslaeao-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-places
Source: https://github.com/tamireslaeao-prog/ONI_V30/tree/main/moltbot-main/skills/local-places
Command: npx skills add https://github.com/tamireslaeao-prog/ONI_V30 --skill local-places-tamireslaeao-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local development teams often need to search for places (restaurants, cafes, etc.) without exposing their frontend to the public Google Places API. This skill provides a locally hosted proxy that forwards requests to Google Places, simplifying setup and testing on localhost.

Core Features & Use Cases

  • Proxies Google Places API calls through a local server to avoid client-side API exposure.
  • Two-step flow: resolve a user location first, then search for matching places with filters.
  • Endpoints: /places/search, /places/{place_id}, /locations/resolve; supports common search parameters and results.

Quick Start

Start the local server and issue a sample search against the proxy to retrieve nearby places.

Frequently Asked Questions about local-places

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I proxy Google Places API calls locally using FastAPI?

A local Google Places proxy forwards frontend search requests through a local server, preventing client-side API key exposure during localhost development and testing.

What's the best way to search nearby places without exposing my Google Places API key?

Using a local proxy server is the best way to search nearby places without exposing your Google Places API key, as it forwards requests server-side via endpoints like /places/search instead of direct client calls.

How does location resolution work before searching for nearby places?

Location resolution works via a two-step flow: the proxy first resolves the user location through a dedicated endpoint, then uses that resolved location to query and filter matching nearby places.

Do I need a GOOGLE_PLACES_API_KEY to run a local place search proxy?

Yes, you need a GOOGLE_PLACES_API_KEY to run a local place search proxy, as the local server requires this key to authenticate and forward requests to the Google Places API endpoints.

Can I retrieve specific place details locally after doing a place search?

Yes, you can retrieve specific place details locally by calling the /places/{place_id} endpoint with the identifier returned from your previous nearby place search results.

Why use a local proxy for Google Places instead of direct API integration?

You use a local proxy for Google Places to avoid exposing your API key on the client side, simplifying localhost testing by validating inputs against defined schemas through controlled REST endpoints.