GM

Google Maps data for agents

sh.fetcher.google-maps/mcp

4 Google Maps endpoints. Pay per call in USDC via x402.

Yes, your AI can use this right now.Answered a live MCP handshake in 323 ms with no sign-in needed and exposes 6 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://google-maps.fetcher.sh/mcp

6 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
google_maps_place_search

Paid ($0.005). Place search — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

google_maps_place

Paid ($0.005). Place — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

google_maps_place_reviews

Paid ($0.005). Place reviews — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

google_maps_review

Paid ($0.005). Review — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

check_balance

Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.

topup_credits

Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.

Alternatives in Crypto & Web3

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”