Address search
Geocodingエンドポイントを使えば、「Address search」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Normalize location search, coordinate lookup, and OSM identifier enrichment through API-key protected geocoding endpoints.
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
エンドポイントファミリー
3
ドキュメント化されたパラメータ
28
サンプル数
3
ライブカタログスナップショット
稼働エンドポイント
3
メソッド
GET
必須パラメータ
6
スキーマ参照
3
{
"platform": "Geocoding",
"endpoint": "geocoding-search",
"method": "GET",
"path": "/geocoding/search",
"auth": "apiKey"
}ユースケース
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
Geocodingエンドポイントを使えば、「Address search」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Geocodingエンドポイントを使えば、「Reverse geocoding」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Geocodingエンドポイントを使えば、「Location enrichment」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のGeocodingエンドポイントカタログから取得しています（エンドポイント3件、ドキュメント化されたリクエストパラメータ28個、公開レスポンススキーマ3件）。DocsとPlaygroundが参照しているカタログと同じものです。
Geocodingのエンドポイントは3件、3つのリクエストファミリーに分類されています（Lookup、Reverse、Search）。
これらのGeocodingエンドポイントには28個のリクエストパラメータがドキュメント化されており、うち6個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
3件のGeocodingエンドポイントのうち3件が実際のサンプルレスポンスを、3件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Geocodingのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、502、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Geocodingのエンドポイントは3個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/geocoding/lookup
/geocoding/reverse
/geocoding/search
エンドポイントカタログ
/geocoding/searchReturns typed Nominatim JSONv2 forward geocoding results. Use either q or structured fields, not both.
レスポンスに関する注記
Example response: ```json {"code":200,"msg":"OK","data":{"query":"Empire State Building","results":[{"place_id":358220252,"osm_type":"way","osm_id":34633854,"lat":"40.7484421","lon":"-73.9856589","category":"office","type":"yes","place_rank":30,"importance":0.5803438355141769,"addresstype":"office","name":"Empire State Building","display_name":"Empire State Building, 350, 5th Avenue, New York, United States","address":{"office":"Empire State Building","house_number":"350","road":"5th Avenue","city":"New York","state":"New York","postcode":"10118","country":"United States","country_code":"us"},"boundingbox":["40.7479255","40.7489585","-73.9865012","-73.9848166"]}]}} ```
MCPツール geocoding_search
/geocoding/reverseReturns the nearest typed Nominatim JSONv2 place for latitude and longitude.
レスポンスに関する注記
Example response: ```json {"code":200,"msg":"OK","data":{"place_id":359125914,"osm_type":"node","osm_id":13306330095,"lat":"40.7484257","lon":"-73.9856700","category":"tourism","type":"viewpoint","place_rank":30,"importance":0.00009175936522464359,"addresstype":"tourism","name":"","display_name":"350, 5th Avenue, Koreatown, Manhattan, New York, 10118, United States","address":{"house_number":"350","road":"5th Avenue","neighbourhood":"Koreatown","suburb":"Manhattan","city":"New York","state":"New York","postcode":"10118","country":"United States","country_code":"us"},"boundingbox":["40.7483757","40.7484757","-73.9857200","-73.9856200"]}} ```
MCPツール geocoding_reverse
/geocoding/lookupReturns typed Nominatim JSONv2 places for comma-separated OSM ids such as W34633854,N123,R456.
レスポンスに関する注記
Example response: ```json {"code":200,"msg":"OK","data":{"query":"W34633854","results":[{"place_id":358220252,"osm_type":"way","osm_id":34633854,"lat":"40.7484421","lon":"-73.9856589","category":"office","type":"yes","place_rank":30,"importance":0.5803438355141769,"addresstype":"office","name":"Empire State Building","display_name":"Empire State Building, 350, 5th Avenue, New York, United States","address":{"office":"Empire State Building","house_number":"350","road":"5th Avenue","city":"New York","state":"New York","postcode":"10118","country":"United States","country_code":"us"},"extratags":{"website":"https://www.esbnyc.com","wikidata":"Q9188"},"namedetails":{"name":"Empire State Building","name:en":"Empire State Building"}}]}} ```
MCPツール geocoding_lookup
関連API
Maps & Local Data
Collect local business and place data from Google Maps for location intelligence workflows.
Maps & Local Data
Search ready-made scraped datasets for local business research with filters, facets, geo queries, and repeatable API output.
Maps & Local Data
Compare cities and countries with normalized Numbeo cost-of-living and quality indices. Retrieve city or country detail and current or historical rankings for location research, relocation products, market analysis, and local-data enrichment.
Geocodingのスクレイピング方法
Geocoding turns an address into coordinates and coordinates back into an address. Crawlora's 3 geocoding endpoints wrap Nominatim's typed JSONv2 responses — forward search, reverse lookup, and OpenStreetMap identifier resolution — behind one API key.
Pass a free-text q, or the structured street, city, county, state, country, and postalcode fields — use one form or the other, not both in the same call.
Send lat and lon to get the nearest matching place, with zoom controlling how coarse or fine the returned address is.
Pass osm_ids to look up known nodes, ways, or relations directly instead of searching for them again.
addressdetails, extratags, and namedetails add the structured address breakdown, the extra OSM tags, and alternate-language names; countrycodes and accept_language narrow and localize the results.
FAQ
OpenStreetMap, via Nominatim. Responses are typed JSONv2, so you get the same place, address, and bounding-box structure Nominatim returns, normalized and behind a single Crawlora key.
No. Use either the free-text q parameter or the structured street, city, county, state, country, and postalcode fields in a single call. Mixing them is not supported and will not narrow the search the way you expect.
Set accept_language for the response language and namedetails to include the place's alternate names. extratags adds the extra OpenStreetMap tags that are not part of the default response.
Nominatim is a shared community service with its own usage policy, and upstream capacity problems surface as 5xx responses rather than bad data. Design for occasional upstream unavailability and retry rather than assuming every call succeeds.