[{"data":1,"prerenderedAt":289},["ShallowReactive",2],{"blog-\u002Fblog\u002Fnew-sdks-and-maplibre-plugin\u002F":3,"related-blog-\u002Fblog\u002Fnew-sdks-and-maplibre-plugin\u002F":256},{"id":4,"title":5,"abstract":6,"author":6,"body":7,"description":241,"excerpt":6,"extension":242,"head":6,"image":6,"keywords":243,"meta":248,"modified":6,"navigation":249,"path":250,"proficiencyLevel":6,"published":251,"rawbody":252,"schemaOrg":6,"schemaType":6,"seo":253,"stem":254,"__hash__":255},"blog\u002Fblog\u002Fnew-sdks-and-maplibre-plugin.md","Three New SDKs and MapLibre GL JS Search Plugin Are Now Available",null,{"type":8,"value":9,"toc":230},"minimark",[10,14,45,50,53,57,60,76,80,83,86,89,103,107,110,114,117,168,172],[11,12,5],"h1",{"id":13},"three-new-sdks-and-maplibre-gl-js-search-plugin-are-now-available",[15,16,17,18,26,27,32,33,38,39,44],"p",{},"Today we are excited to announce the initial release of three SDKs (",[19,20,25],"a",{"href":21,"rel":22,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjavascript-typescript\u002F",[23],"external","_blank","JavaScript\u002FTypeScript",",\n",[19,28,31],{"href":29,"rel":30,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fpython\u002F",[23],"Python",", and ",[19,34,37],{"href":35,"rel":36,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fkotlin-jvm\u002F",[23],"Kotlin","), along\nwith a ",[19,40,43],{"href":41,"rel":42,"target":24},"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@stadiamaps\u002Fmaplibre-search-box",[23],"MapLibre GL JS search box plugin"," for Stadia\nMaps services.",[46,47,49],"h2",{"id":48},"weve-listened-and-delivered","We've Listened and Delivered",[15,51,52],{},"These four projects round out our support for a large portion of our existing user base, including all browser-based\napps and many popular backend use cases too.",[46,54,56],{"id":55},"why-use-the-sdks","Why Use the SDKs?",[15,58,59],{},"Of course you could write your code to directly interface with our APIs, but there are several benefits to taking\nadvantage of our SDKs:",[61,62,63,67,70,73],"ul",{},[64,65,66],"li",{},"Save time; no need to write your own API code since you have access to the full range of Stadia Maps geospatial APIs",[64,68,69],{},"Easily install via your favorite package manager",[64,71,72],{},"Faster access to documentation in your IDE with autocomplete",[64,74,75],{},"Always utilize the latest features because when we release a new API, we'll release an updated SDK",[46,77,79],{"id":78},"maplibre-gl-js-search-box-plugin","MapLibre GL JS Search Box Plugin",[15,81,82],{},"Our MapLibre GL JS plugin builds off of our JavaScript SDK and this plugin makes it easy and straightforward to add an\nautocomplete search box to your maps with just a few lines of code, all while leveraging best practices (debouncing of\nrequests, caching of previous results, and navigating to the chosen result) for the autocomplete search API!",[15,84,85],{},"Now you can easily implement an address auto-fill form for your e-Commerce application, saving your customers time and\nheadaches on the backend due to bad input data.",[15,87,88],{},"You can also use autocomplete to find:",[61,90,91,94,97,100],{},[64,92,93],{},"Points of interest such as major landmarks, airports, campuses, etc.",[64,95,96],{},"Administrative areas (e.g. neighborhoods, cities, states, countries, etc.)",[64,98,99],{},"Postal codes",[64,101,102],{},"And more...",[46,104,106],{"id":105},"we-want-your-feedback","We Want Your Feedback",[15,108,109],{},"Since these are the initial versions of each SDK and plugin, we are looking for feedback from the community on updates,\nfeatures, and improvements that we can incorporate into upcoming releases.",[46,111,113],{"id":112},"where-to-find","Where to Find",[15,115,116],{},"You can find the releases, and their source code, in the usual places:",[61,118,119,133,146,158],{},[64,120,121,122,127,128],{},"JavaScript SDK: ",[19,123,126],{"href":124,"rel":125,"target":24},"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@stadiamaps\u002Fapi",[23],"npm"," |\n",[19,129,132],{"href":130,"rel":131,"target":24},"https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-ts",[23],"GitHub",[64,134,135,136,141,142],{},"Python SDK: ",[19,137,140],{"href":138,"rel":139,"target":24},"https:\u002F\u002Fpypi.org\u002Fproject\u002Fstadiamaps\u002F",[23],"PyPi"," | ",[19,143,132],{"href":144,"rel":145,"target":24},"https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-py",[23],[64,147,148,149,127,154],{},"Kotlin SDK: ",[19,150,153],{"href":151,"rel":152,"target":24},"https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-kotlin\u002Fpackages\u002F1887775",[23],"GitHub Packages",[19,155,132],{"href":156,"rel":157,"target":24},"https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-kotlin",[23],[64,159,160,161,127,164],{},"MapLibre GL JS Plugin: ",[19,162,126],{"href":41,"rel":163,"target":24},[23],[19,165,132],{"href":166,"rel":167,"target":24},"https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fmaplibre-search-box",[23],[46,169,171],{"id":170},"learn-more-next-steps","Learn More & Next Steps",[61,173,174,183,191],{},[64,175,176,177,182],{},"Read documentation about our ",[19,178,181],{"href":179,"rel":180,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F",[23],"SDKs"," and Plugins on our docs site.",[64,184,185,190],{},[19,186,189],{"href":187,"rel":188,"target":24},"https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=sdk_launch&utm_content=maplibre_plugin_announcement",[23],"Create an account"," to start building today!",[64,192,193,194,199,200,205,206,211,212,217,218,223,224,229],{},"Join our community on ",[19,195,198],{"href":196,"rel":197,"target":24},"https:\u002F\u002Fslack.openstreetmap.us\u002F",[23],"Slack"," or ",[19,201,204],{"href":202,"rel":203,"target":24},"https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT",[23],"Discord",", follow us\non ",[19,207,210],{"href":208,"rel":209,"target":24},"https:\u002F\u002Fen.osm.town\u002F@stadiamaps",[23],"Mastodon",", ",[19,213,216],{"href":214,"rel":215,"target":24},"https:\u002F\u002Ftwitter.com\u002F@stadiamaps",[23],"Twitter",", or\n",[19,219,222],{"href":220,"rel":221,"target":24},"https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F",[23],"LinkedIn",", or sign-up for our ",[19,225,228],{"href":226,"rel":227,"target":24},"https:\u002F\u002Feepurl.com\u002Fgs51fD",[23],"mailing list","!",{"title":231,"searchDepth":232,"depth":232,"links":233},"",4,[234,236,237,238,239,240],{"id":48,"depth":235,"text":49},2,{"id":55,"depth":235,"text":56},{"id":78,"depth":235,"text":79},{"id":105,"depth":235,"text":106},{"id":112,"depth":235,"text":113},{"id":170,"depth":235,"text":171},"New JavaScript, Python, and Kotlin SDKs, along with a MapLibre GL JS Search Plugin, are now available.","md",[244,245,31,37,246,247],"SDK","JavaScript","MapLibre","Search Plugin",{},true,"\u002Fblog\u002Fnew-sdks-and-maplibre-plugin","2023-07-04","---\ndescription: \"New JavaScript, Python, and Kotlin SDKs, along with a MapLibre GL JS Search Plugin, are now available.\"\npublished: \"2023-07-04\"\nkeywords:\n  - SDK\n  - JavaScript\n  - Python\n  - Kotlin\n  - MapLibre\n  - Search Plugin\n---\n\n# Three New SDKs and MapLibre GL JS Search Plugin Are Now Available\n\nToday we are excited to announce the initial release of three SDKs ([JavaScript\u002FTypeScript](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjavascript-typescript\u002F),\n[Python](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fpython\u002F), and [Kotlin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fkotlin-jvm\u002F)), along\nwith a [MapLibre GL JS search box plugin](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@stadiamaps\u002Fmaplibre-search-box) for Stadia\nMaps services.\n\n## We've Listened and Delivered\n\nThese four projects round out our support for a large portion of our existing user base, including all browser-based\napps and many popular backend use cases too.\n\n## Why Use the SDKs?\n\nOf course you could write your code to directly interface with our APIs, but there are several benefits to taking\nadvantage of our SDKs:\n\n* Save time; no need to write your own API code since you have access to the full range of Stadia Maps geospatial APIs\n* Easily install via your favorite package manager\n* Faster access to documentation in your IDE with autocomplete\n* Always utilize the latest features because when we release a new API, we'll release an updated SDK\n\n## MapLibre GL JS Search Box Plugin\n\nOur MapLibre GL JS plugin builds off of our JavaScript SDK and this plugin makes it easy and straightforward to add an\nautocomplete search box to your maps with just a few lines of code, all while leveraging best practices (debouncing of\nrequests, caching of previous results, and navigating to the chosen result) for the autocomplete search API!\n\nNow you can easily implement an address auto-fill form for your e-Commerce application, saving your customers time and\nheadaches on the backend due to bad input data.\n\nYou can also use autocomplete to find:\n\n* Points of interest such as major landmarks, airports, campuses, etc.\n* Administrative areas (e.g. neighborhoods, cities, states, countries, etc.)\n* Postal codes\n* And more...\n\n## We Want Your Feedback\n\nSince these are the initial versions of each SDK and plugin, we are looking for feedback from the community on updates,\nfeatures, and improvements that we can incorporate into upcoming releases.\n\n## Where to Find\n\nYou can find the releases, and their source code, in the usual places:\n\n* JavaScript SDK: [npm](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@stadiamaps\u002Fapi) |\n[GitHub](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-ts)\n* Python SDK: [PyPi](https:\u002F\u002Fpypi.org\u002Fproject\u002Fstadiamaps\u002F) | [GitHub](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-py)\n* Kotlin SDK: [GitHub Packages](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-kotlin\u002Fpackages\u002F1887775) |\n[GitHub](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-kotlin)\n* MapLibre GL JS Plugin: [npm](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@stadiamaps\u002Fmaplibre-search-box) |\n[GitHub](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fmaplibre-search-box)\n\n## Learn More & Next Steps\n\n- Read documentation about our [SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F) and Plugins on our docs site.\n- [Create an account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=sdk_launch&utm_content=maplibre_plugin_announcement) to start building today!\n- Join our community on [Slack](https:\u002F\u002Fslack.openstreetmap.us\u002F) or [Discord](https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT), follow us\non [Mastodon](https:\u002F\u002Fen.osm.town\u002F@stadiamaps), [Twitter](https:\u002F\u002Ftwitter.com\u002F@stadiamaps), or\n[LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F), or sign-up for our [mailing list](https:\u002F\u002Feepurl.com\u002Fgs51fD)!",{"title":5,"description":241},"blog\u002Fnew-sdks-and-maplibre-plugin","j9zyrUxAxpaPhuKkQNZl6oBP264LC7IkuopuVtOaOAc",[257,268,279],{"title":258,"description":259,"path":260,"published":261,"keywords":262,"rawbody":267},"Our SwiftUI DSL Is Joining the MapLibre Family","Our SwiftUI DSL makes it easier than ever to build apps with maps. And now it's an official MapLibre project!","\u002Fblog\u002Fmaplibre-swiftui-dsl","2024-10-07",[263,246,264,265,266],"SwiftUI","iOS Development","Maps SDK","DSL","---\ndescription: \"Our SwiftUI DSL makes it easier than ever to build apps with maps. And now it's an official MapLibre project!\"\npublished: 2024-10-07\nkeywords:\n  - SwiftUI\n  - MapLibre\n  - iOS Development\n  - Maps SDK\n  - DSL\nschemaType: TechArticle\nproficiencyLevel: Beginner\n---\n\n# Our SwiftUI DSL Is Joining the MapLibre Family\n\nWe're thrilled to announce [MapLibre SwiftUI DSL](https:\u002F\u002Fgithub.com\u002Fmaplibre\u002Fswiftui-dsl)\nhas graduated from the Stadia Maps labs to become a [MapLibre](https:\u002F\u002Fmaplibre.org\u002F)-hosted project.\nThe project makes MapLibre a first-class citizen in SwiftUI apps,\nand fills an important gap in the iOS developer experience for MapLibre.\n\nThe project began when our co-founder Ian Wagner wanted MapLibre to have a developer experience that rivaled MapKit for SwiftUI.\n[Jacob Fielding](https:\u002F\u002Fgithub.com\u002Farchdoog){ target=\"_blank\" } ([Rallista](https:\u002F\u002Frallista.app\u002F){ target=\"_blank\" }),\n[Patrick Wolowicz](https:\u002F\u002Fsubzero.eu\u002F){ target=\"_blank\" } and [Patrick Kladek](https:\u002F\u002Fgithub.com\u002FPatrick-Kladek){ target=\"_blank\" }\n([HudHud](https:\u002F\u002Fhudhud.sa\u002Fen){ target=\"_blank\" }) shared the vision\nand joined the project, contributing significantly to the development and success of the project.\nWe're grateful for their ongoing contributions,\nand for the support from their respective companies.\n\nBy transitioning to a MapLibre hosted project,\nthe SwiftUI DSL will have more visibility,\nand will unify ongoing initiatives to make MapLibre work better with SwiftUI.\n\n## Modernizing the Map Developer Experience\n\nBefore the SwiftUI DSL, developers had to build their own wrapper views\nto use MapLibre in a SwiftUI app.\nThis was a lot of work—often duplicating what others had already done—and required a deep understanding of MapLibre Native's Objective-C API.\nThe SwiftUI DSL makes this largely a thing of the past.\nWith just a few lines of code, developers can overlay custom layers, bind the camera to reactive state, and set up custom gestures.\n\nFor library authors, the DSL unlocks a whole new level of composability.\nIt's now easy to offer a \"default\" experience that users can customize.\nOur own [Ferrostar navigation SDK](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fferrostar\u002F?utm_source=marketing_site&utm_campaign=swiftui_dsl_maplibre)\nleverages this pattern,\ngiving developers the power to add custom map layers, overlays, and controls\non top of a map during turn-by-turn navigation.\nThis sort of behavior is extremely difficult and error-prone in UIKit,\nbut is a breeze in SwiftUI.\nWe're excited to see more library authors adopting this approach too.\n\n## Learn More & Next Steps\n\n- Check out our [quickstart](https:\u002F\u002Fdocs.stadiamaps.com\u002Fnative-multiplatform\u002Fmaplibre-gl-native\u002F?utm_source=marketing_site&utm_campaign=swiftui_dsl_maplibre#ios){ target=\"_blank\" }\n  to build your first map with SwiftUI.\n- Find the source code on [GitHub](https:\u002F\u002Fgithub.com\u002Fmaplibre\u002Fswiftui-dsl){ target=\"_blank\" } (and give it a star!).\n- Join the `#maplibre-swiftui-compose-playground` channel in the [OpenStreetMap US Slack](https:\u002F\u002Fslack.openstreetmap.us\u002F) to get help or join the development effort.\n- Follow Stadia Maps on [Mastodon](https:\u002F\u002Fen.osm.town\u002F@stadiamaps), [Twitter](https:\u002F\u002Ftwitter.com\u002F@stadiamaps),\n  or [LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F), or sign-up for\n  our [newsletter](https:\u002F\u002Feepurl.com\u002Fgs51fD) to hear about exciting developments first.\n",{"title":269,"description":270,"path":271,"published":272,"keywords":273,"rawbody":278},"Announcing Version 2 of our Official SDKs","We've added new routing and elevation API features in our latest SDK releases.","\u002Fblog\u002Fannouncing-version-2-of-official-sdks","2024-03-20",[244,274,275,276,277],"API Client","Routing","Elevation","Release","---\ndescription: \"We've added new routing and elevation API features in our latest SDK releases.\"\npublished: 2024-03-20\nkeywords:\n  - SDK\n  - API Client\n  - Routing\n  - Elevation\n  - Release\n---\n\n# Announcing Version 2 of our Official SDKs\n\nToday marks a new milestone in the lifecycle of the Stadia Maps official SDKs.\nWe have just released version 2.0.0 of our API client libraries\nfor the web, mobile and backend.\nWith official clients in TypeScript, Swift, Kotlin, and Python,\nwe've already helped thousands of developers get started in just a few lines of code.\n\nThis release includes a number of improvements:\n\n* A factor for adjusting the cost of alleys when doing automobile routing\n* A resample distance parameter for elevation requests, which makes it even easier to get elevation profiles; just give us a simple set of points and we'll interpolate the rest!\n* Support for requesting one or more alternate routes (great for [navigation applications](\u002Fproducts\u002Frouting-navigation))\n* Additional options to ignore restrictions (particularly useful during map matching when you just want to know which roads a vehicle traversed)\n\nIf you're using one of our existing libraries already,\nit will generally keep on working as-is.\nHowever, in order to make a few of the improvements,\nwe had to introduce backwards-incompatible changes,\nwhich is why it gets a major version bump.\nFor migration instructions, refer to the release notes lined below:\n\n* [TypeScript](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-ts\u002Freleases\u002Ftag\u002Fv2.0.0)\n* [Swift](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-swift\u002Freleases\u002Ftag\u002F2.0.0)\n* [Kotlin](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-kotlin\u002Freleases\u002Ftag\u002Fv2.0.0)\n* [Python](https:\u002F\u002Fgithub.com\u002Fstadiamaps\u002Fstadiamaps-api-py\u002Freleases\u002Ftag\u002Fv2.0.0)\n",{"title":280,"description":281,"path":282,"published":283,"keywords":284,"rawbody":288},"Generally Available: Geocoding & Autocomplete Search with SDKs","Build modern mapping experiences with autocomplete search and efficient operations with flexible geocoding APIs.","\u002Fblog\u002Fgeocoding-and-autocomplete-search-generally-available","2023-06-15",[285,286,287,244],"Geocoding","Autocomplete Search","Product Launch","---\ndescription: \"Build modern mapping experiences with autocomplete search and efficient operations with flexible geocoding APIs.\"\npublished: \"2023-06-15\"\nkeywords:\n  - Geocoding\n  - Autocomplete Search\n  - Product Launch\n  - SDK\n---\n\n# Generally Available: Geocoding & Autocomplete Search with SDKs\n\nWe are excited to announce the immediate general availability of Stadia Maps Geocoding & Autocomplete Search APIs, the\nnext step as we build the Alternative Location Platform. With these APIs, developers can create all-new user\nexperiences critical for many products. Starting today, it is easier to solve key back-office problems such as finding\nthe geographic location of an address, converting between natural-language input and geographic coordinates, and adding\nautocomplete search for even better and more immersive map experiences. As with all our APIs, these solutions combine\nthe power of open data and open-source software and run on the same infrastructure platform as our existing reliable,\naffordable, and private location services.\n\nTo create the best available library of global places, we combined multiple open data sets, including OpenStreetMap,\nOpenAddresses, and more into one coherent API. Developers can rely on flexible filtering options to limit searches by\ncountry, bounding box, and more. When integrating, the rich API responses provide all the required data, with no extra\nwork.\n\nContinuing our tradition of building on open source, we started by building on the excellent work of\nthe [Pelias](https:\u002F\u002Fwww.pelias.io\u002F) project and its team. We then connected it with our existing services—with many\nmore integrations planned, and we added our own Stadia twist. We will contribute improvements and bug fixes back to\nPelias and other projects so that everyone can benefit.\n\n### Forward & Reverse Geocoding\n\nDevelopers around the world use forward and reverse geocoding to help users and computers work with geospatial data.\nGeocoding provides conversion between places described by natural language, such as addresses, points of interest, or\ncity names, and geographic coordinates, such as `35.6895, 139.69171`.\n\nFor the developer adventuring into the unknown, our address search is complemented by intelligent approximation. This\nallows for a high-probability result, even for addresses that aren’t on the map. Using this, last-mile delivery and\nother services are able to ensure deliver of a package to even the newest apartment building.\n\nIf your data is already structured, such as input from an address form, the Structured Geocoding API provides the same\ngeocoding capabilities as the standard endpoint. This API enables easy lookups based on labeled fields such as\ncity, street, and country, and improves the quality of results when there are only a few inputs available.\n\n### Autocomplete Search\n\n![Autocomplete Search Example](\u002Fimages\u002Fcontent\u002Fautocomplete-search-example.gif){}\n\nDevelopers and users are familiar with the ubiquitous autocomplete search box on maps. By\nadding support for search-as-you-type functionality, Stadia Maps enables a range of user experiences. These include\nautofilling address forms for e-commerce and creating interactive map integrations that make it easy for users to find\nplaces anywhere in the world.\n\nOur users have long requested search functionality for direct integration into maps. Using our new APIs and\n[integration for MapLibre GL JS](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@stadiamaps\u002Fmaplibre-search-box), developers can quickly\nbuild a map with a search box for any platform.\n\n### SDKs\n\nTo make it easier for everyone to integrate these new APIs, we've developed SDKs. Today, we're launching the\n[TypeScript (JavaScript) SDK](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjavascript-typescript\u002F) and\nthe [Python SDK](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fpython\u002F), which support geocoding, routing, and a few other APIs.\nWe plan to add Kotlin and more in the near future.\n\nWant to see a SDK in your favorite language? Drop us a line to help us prioritize which SDKs to build next!\n\n### Pricing\n\nIn alignment with our mission of making maps affordable and transparent, we have set competitive prices for our new\nGeocoding & Autocomplete Search APIs. Each request uses 30 credits, with precise costs depending on the plan you select\nand your specific usage.\n\nAutocomplete Search is available on all plans—including our Free plan! However, Geocoding endpoints (forward, reverse,\nand structured) require a paid plan. Additionally, storing geocoding results for future use requires a Standard plan\nor above.\n\n### Learn More & Next Steps\n\n- Find pricing details on our [pricing page](\u002Fpricing\u002F). \n- Read documentation about [geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) and [SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F) on our docs site. \n- [Schedule a call](mailto:support@stadiamaps.com?subject=Tell%20Me%20More%20About%20Geocoding) to learn more. \n- [Create an account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_launch&utm_content=geocoding_ga_announcement) to start building today!",1778676026078]