01
Source and ownership
Official status, provider domains, and documentation ownership are checked together. Community and third-party services are labeled explicitly.
Filter, compare, and jump to docs quickly.
You can also use this catalog through MCP
Use the API Deposu MCP connection in Codex, Claude, or other MCP clients to search APIs and fetch details in chat.
OpenCage Geocoding API | |||||||||
Summary OpenCage is an API-key based service for global geocoding and reverse geocoding with quick integration. Use cases
| |||||||||
OpenPLZ API | |||||||||
Summary Avusturya, Almanya, İsviçre ve Lihtenştayn için posta kodu, şehir ve sokak bilgileri sunan açık veri API'si. Use cases
Tags posta-kodu adres coğrafya | |||||||||
GeoJS | |||||||||
Summary IP adresine göre coğrafi konum, ülke, şehir ve ASN bilgisi döndüren ücretsiz geolocation API'si. Use cases
Tags geocoding ip-geolocation ip | |||||||||
Country.is | |||||||||
Summary IP adresinden ziyaretçinin ülkesini tek bir endpoint ile döndüren minimalist ücretsiz API. Use cases
Tags geocoding ip-geolocation ip | |||||||||
Mapbox API | |||||||||
Summary Özelleştirilebilir haritalar, geocoding, yönlendirme ve coğrafi analiz için kapsamlı harita platformu. Use cases
| |||||||||
MapTiler Cloud API | |||||||||
Summary MapTiler Cloud provides key-based geocoding and map services suitable for real-estate products. Use cases
| |||||||||
LocationIQ API | |||||||||
Summary LocationIQ is an API-key based map service for quick address search and reverse geocoding. Use cases
| |||||||||
Geoapify API | |||||||||
Summary Geoapify is a map API suite with geocoding and places features under one key, suitable for real-estate products. Use cases
| |||||||||
Burulaş | |||||||||
Summary Burulaş Web API Use cases
| |||||||||
Şehir Haritası API (İBB) | |||||||||
Summary Provides panorama services from the IBB City Map stack for nearby location views. Use cases
| |||||||||
1-10 / 13
API Deposu is not intended to be a link list. Indexed detail pages should add verifiable context that helps developers make an integration decision beyond reading the provider's own documentation.
01
Official status, provider domains, and documentation ownership are checked together. Community and third-party services are labeled explicitly.
02
Authentication, free-tier terms, testable endpoints, and production constraints are presented with sources and verification dates whenever available.
03
Unverified details are not guessed. Incomplete records can remain discoverable in the catalog but are not indexed until they contain sufficient publisher-added value.