local-places

Resolve vague location queries and search nearby places via a local Google Places API proxy.

Updated Mar 13, 2026

Search Tags:#fastapi #google-places #local-proxy #location-search #geosearch #place-resolution

Ready to run

npx skills add https://github.com/Yogi-076/Vajrascan.on --skill local-places-yogi-076

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: local-places
Source: https://github.com/Yogi-076/Vajrascan.on/tree/main/moltbot/skills/local-places
Command: npx skills add https://github.com/Yogi-076/Vajrascan.on --skill local-places-yogi-076

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly convert vague, natural-language location queries into structured place results without exposing the agent directly to the external Google Places API, simplifying integration for assistants and automation workflows.

Core Features & Use Cases

Location resolution: Turn ambiguous location text (e.g., "Soho, London" or "near me") into candidate places with coordinates and addresses.
Filtered place search: Search by free-text query plus filters for type, open_now, min_rating, and price_levels with pagination support.
Details retrieval: Fetch full place details (phone, website, hours) for a selected result.
Use Case: An assistant can resolve a user's vague request, present a ranked list of cafes within a radius, and then return details for the chosen cafe.

Quick Start

Start the local Places API server with GOOGLE_PLACES_API_KEY set, resolve a location, and run a filtered search to retrieve nearby results.

Frequently Asked Questions about local-places

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

FAQPage Schema

How do I resolve vague location queries into structured place results for an AI assistant?▼

Location resolution converts ambiguous natural-language text like "near me" into candidate places with coordinates and addresses. This proxy returns structured place results without exposing your agent directly to the Google Places API, simplifying integration.

Can I filter Google Places search results by rating, open status, and price levels?▼

Filtered place search supports type, open_now, min_rating, and price_levels filters with pagination support. You submit a free-text query plus these parameters to the local proxy, which returns ranked nearby places matching your specified criteria.

What do I need to set up before using a local Google Places API proxy?▼

You need a running local server exposing /places/search, /places/{place_id}, and /locations/resolve endpoints, plus the GOOGLE_PLACES_API_KEY environment variable. Input validation handles limits, filters, and location bias automatically.

How do I retrieve full details like phone and hours for a selected place?▼

Details retrieval fetches full place information including phone, website, and hours for a selected result. You query the /places/{place_id} endpoint using the identifier returned from your initial location search or filtered place query.

Does FastAPI work with a local Google Places proxy for location-aware agents?▼

FastAPI is supported as the framework for running the local Places API server. The proxy intercepts location queries and place searches, allowing FastAPI-based assistants to resolve vague locations and apply filters seamlessly.

Why use a local proxy for Google Places instead of calling the API directly from my agent?▼

A local proxy simplifies integration by handling input validation for limits, filters, and location bias centrally. It abstracts the external Google Places API, keeping your agent clean while providing consistent paginated results for places.