Back to Details

google-maps

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Google Maps API

Google Maps API

Place search, place details, and reviews as clean JSON — one plain HTTP GET per call, paid as you go. No Google Cloud project, no API key restriction rules, no per-request Places API billing.
Base URL: 
https://google-maps.fetcher.sh
地点搜索、地点详情及评论以简洁JSON格式返回——每次调用仅需一次简单的HTTP GET请求，按需付费。无需Google Cloud项目、无API密钥限制规则、无按请求计费的Places API费用。
基础URL：
https://google-maps.fetcher.sh

Authentication

认证

Two ways to pay, same data — full mechanics in the 
fetcher
skill:
bash
undefined
两种付费方式，数据一致——完整机制请查看
fetcher
技能：
bash
undefined

1. Prepaid credits (recommended — get a key at https://fetcher.sh/topup

1. 预付费积分（推荐——通过 https://fetcher.sh/topup 获取密钥

or via POST /api/credits/topup, see the fetcher skill)

或通过POST /api/credits/topup，详见fetcher技能）

export FETCHER_API_KEY="bby_live_xxxxxxxxxxxx" curl -H "Authorization: Bearer $FETCHER_API_KEY"
"https://google-maps.fetcher.sh/api/place/search?query=coffee"
export FETCHER_API_KEY="bby_live_xxxxxxxxxxxx" curl -H "Authorization: Bearer $FETCHER_API_KEY"
"https://google-maps.fetcher.sh/api/place/search?query=coffee"

2. x402 pay-per-call — omit the header; a GET with no payment returns 402

2. x402按调用付费——省略请求头；未支付的GET请求会返回402状态码

with machine-readable payment requirements (USDC on Base, Polygon,

并附带机器可读的支付要求（支持Base、Polygon、Arbitrum、Monad或Solana链上的USDC）。@x402/fetch会自动签名并重试请求。

Arbitrum, Monad, or Solana). @x402/fetch signs and retries automatically.

—

Every response is `{ "status": number, "message": string, "data": ... }`; the
HTTP status mirrors `status`.

每个响应格式均为`{ "status": number, "message": string, "data": ... }`；HTTP状态码与`status`字段值一致。

Endpoints (4 — all GET, $0.005/call)

端点（共4个——均为GET请求，每次调用$0.005）

EndpointWhat it returns
/api/place/search
Places matching a text query, optionally anchored to a coordinate
/api/place/{fid}
A place's full details by feature ID
/api/place/{fid}/reviews
A place's reviews
/api/review/{id}
A single review by ID
Required on search: 
query
. Optional: 
languageCode
, 
countryCode
, 
latitude
, 
longitude
, 
offset
, 
zoom
(search radius/precision). Reviews support 
sort
(
relevant
, 
newest
, 
highest
, 
lowest
) and 
cursor
.
端点返回内容
/api/place/search
匹配文本查询的地点，可选择锚定到指定坐标
/api/place/{fid}
通过特征ID（fid）获取地点的完整详情
/api/place/{fid}/reviews
地点的评论
/api/review/{id}
通过ID获取单条评论
搜索请求必填参数：
query
。可选参数：
languageCode
、
countryCode
、
latitude
、
longitude
、
offset
、
zoom
（搜索半径/精度）。评论请求支持
sort
（
relevant
、
newest
、
highest
、
lowest
）和
cursor
参数。

Scenarios

使用场景

Plain text search:
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=ramen in brooklyn" -G \
  "https://google-maps.fetcher.sh/api/place/search"
Anchor the search to a coordinate (for "near me" style queries):
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=coffee" -G \
  --data-urlencode "latitude=40.7128" \
  --data-urlencode "longitude=-74.0060" \
  "https://google-maps.fetcher.sh/api/place/search"
A place's details, then its reviews sorted by newest:
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://google-maps.fetcher.sh/api/place/0x89c259af336b3341%3A0x8c584d6dfe89aa89"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "sort=newest" -G \
  "https://google-maps.fetcher.sh/api/place/0x89c259af336b3341%3A0x8c584d6dfe89aa89/reviews"
A single review by ID:
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://google-maps.fetcher.sh/api/review/ChdDSUhNMG9nS0VJQ0FnSURDeGRXQnl3RRAB"
Localized results (French language, Canadian region):
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=boulangerie" -G \
  --data-urlencode "languageCode=fr" \
  --data-urlencode "countryCode=CA" \
  "https://google-maps.fetcher.sh/api/place/search"
纯文本搜索：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=ramen in brooklyn" -G \
  "https://google-maps.fetcher.sh/api/place/search"
将搜索锚定到坐标（适用于"附近"类查询）：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=coffee" -G \
  --data-urlencode "latitude=40.7128" \
  --data-urlencode "longitude=-74.0060" \
  "https://google-maps.fetcher.sh/api/place/search"
获取地点详情，然后按最新排序获取其评论：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://google-maps.fetcher.sh/api/place/0x89c259af336b3341%3A0x8c584d6dfe89aa89"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "sort=newest" -G \
  "https://google-maps.fetcher.sh/api/place/0x89c259af336b3341%3A0x8c584d6dfe89aa89/reviews"
通过ID获取单条评论：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://google-maps.fetcher.sh/api/review/ChdDSUhNMG9nS0VJQ0FnSURDeGRXQnl3RRAB"
本地化结果（法语，加拿大地区）：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=boulangerie" -G \
  --data-urlencode "languageCode=fr" \
  --data-urlencode "countryCode=CA" \
  "https://google-maps.fetcher.sh/api/place/search"

MCP

MCP

json
{
  "mcpServers": {
    "google-maps": {
      "url": "https://google-maps.fetcher.sh/mcp",
      "headers": { "Authorization": "Bearer bby_live_..." }
    }
  }
}
Free: 
search_endpoints
, 
describe_endpoint
, 
check_balance
. Paid: 
fetch_data
(any endpoint above), 
topup_credits
, plus the named shortcut 
google_maps_place_search
. Drop the 
headers
block to pay per call with x402 instead — see the 
fetcher
skill for the full flow.
json
{
  "mcpServers": {
    "google-maps": {
      "url": "https://google-maps.fetcher.sh/mcp",
      "headers": { "Authorization": "Bearer bby_live_..." }
    }
  }
}
免费接口：
search_endpoints
、
describe_endpoint
、
check_balance
。付费接口：
fetch_data
（上述任意端点）、
topup_credits
，以及命名快捷方式
google_maps_place_search
。若要改用x402按调用付费，请移除
headers
块——完整流程请查看
fetcher
技能。

Errors

错误说明

  • 400
    — missing/invalid parameter (message names it)
  • 401
    — unknown or rotated key
  • 402
    — payment required (x402 challenge) or 
    topup_required
    (credits exhausted)
  • 404
    — not a priced path
  • No rate limits; no refunds on upstream failures (settlement precedes delivery)
  • 400
    —— 参数缺失/无效（消息中会指明具体参数）
  • 401
    —— 密钥未知或已过期
  • 402
    —— 需要支付（x402挑战）或
    topup_required
    （积分耗尽）
  • 404
    —— 非付费路径
  • 无速率限制；上游故障不退款（结算先于交付）

Reference

参考链接