News for hackers. Stuff that matters.

stadiamaps

Re:Stadia Maps MCP Server – Location Context for AI on Wednesday July 16, 2025 @08:20AM (#44581414)
We built a MCP server for our APIs. Why?

Because AI agents are about to run into the same location API pitfalls that have frustrated human developers for years. Except now it's happening at 100x scale. AI workflows need the same transparent pricing, real privacy, documentation that actually makes sense.

AI agents should be free to consume location data for whatever they need, but when every call burns your budget and your users' privacy, they can't do their job.

Our MCP server gives you the same fast and reliable location context directly into your LLMs and AI workflows—without the Big Tech predation.

We're here to answer questions!

Hey joelhaasnoot! Thanks for letting us know.

That is definitely a bug in our pricing table. We'll correct that.

Makes sense. We'll look into it!
We do not currently.

Could you elaborate a bit more on what you mean? Do you mean rendering the map differently based on a user's likely view of disputed borders, etc.? Basically smoothing over various geopolitical issues by making the map agree with a given user. :)

Good question! We are in direct competition with MapBox, and they are perhaps our biggest competition just based on data sources we use and goals, etc.

We believe there are advantages, though some apply mainly for specific applications:

- Price: We use tier-based plans and soft-limiting instead of purely "you pay for what you use", this allows for consistent bills, even if your traffic isn't always consistent. Thus it's very easy to see how much it would cost each month, without a fancy calculator and ready knowledge of how users behave.

- Asset Tracking: We do not require $500 / month plus usage to use our maps in an internal or asset-tracking application.

- Goals: We want to build a sustainable, bootstrapped business without the requirements of venture capital, etc. This is a key philosophical difference. MapBox is venture-funded and recently raised again, while we're bootstrapped and don't plan to raise VC money. This allows us to exist by providing a quality service to our customers without the need to grow exponentially or incessantly. (This is not a knock against venture funded companies; we just believe there's more than enough room for both philosophies in map services companies.)

Thanks for your feedback Chris!

We'll look into those display issues right away. We pushed a new design before the HN post took off, and we clearly missed a few details.

Regarding map load time, our servers are currently located in the US (which is where all of our paying customers are based at the moment). We do have multiple servers running in a cluster, but we are still working on our geographic diversity. While our load times are generally good wherever we've tested in the northwestern hemisphere, my cofounder lives in Korea now and he is acutely aware of our latency spikes in Asia. Our CDN, CloudFlare, routes traffic based primarily on peering arrangements until you start paying them a lot more, but we're working on geographically diversifying our server fleet behind CF load balancers as our next step.

Ah! Thank you. We'll correct it.
We wondered the exact same thing. That's why all of our paid tiers allow it. :)

We do require a paid tier because almost all asset tracking applications are commercial, which based on our non-commercial/development-only clause for the Free tier requiring a paid plan is the logical outcome. If you have a non-profit project that does asset tracking and is under our Free limits, please let us know, and we can discuss options!

It's not a bad suggestion, but this would be a violation of our terms (as well as any other paid map service provider that I've ever seen).

We'll look into ways to remove the terms issue while preserving out ability to properly bill and protecting privacy and regulatory compliance.

This is something we do not currently support because our billing is based on always being the host; however, we're keeping our eye on GDPR and its requirements on the market, and how we could offer services to help ease the transition with regards to maps.

Would a solution that allows you to request via your own servers (simple proxying?) meet the requirements? Or would a simpler solution be to allow you to generate (perhaps via an API?) and self-host, while paying for a service that allow this?

Thanks! The prices are on the main page under the heading "Our Tiers."
Correct. We have also contributed to OpenMapTiles, and if you are interested in self-hosting and/or are very cost sensitive, we'd highly recommend checking them out (they also have very affordable hosting if you're just looking for the tiles).

We're also trying to offer value in other areas such as the design, and in additional services. Routing is obviously one of these, and we've got a few more services that that we're working on. We'll be announcing some of these later this year.

Yes, that's something on our TODO list, but none of our existing customers have expressed mobile as a pain point yet.

If you don't mind elaborating, we're curious what you are looking for that the "platform-native" maps from Apple and Google don't provide (both Google and Apple provide unlimited unlimited free usage on mobile). I (one of the founders) am actually a mobile developer for most of the day, and so far I only have one client that isn't using the built-in maps (Mapbox in their case). They wanted more recent high res satellite imagery and the ability to download areas for offline use. Are there any other use cases we're missing?

Thanks for catching this. This was indeed an oversight on the attributions page. Valhalla is now credited on the attributions page as well as the docs.
Thanks for the suggestion! This is something we're looking into and would love to provide.

Would you prefer this be provided as a downloadable dataset or a linkable dataset to use just like our map themes?

Hey ggm, could you elaborate on what's broken? We just checked with the same browser and OSX, and the page looks to be correct.

Thanks!

Thanks for your kind words! We care about internationalization a lot (both of the founders live outside the English world), and we're glad to see we can help you out with that.

We'd love to help anyway possible with the generation. Would you mind sending us an email ([email protected]) so we could collaborate better on this?

Thanks for your feedback! I can see where you're coming from.

If you're using vector maps, you can definitely remove that layer, if you wish.

If enough users request a basemap without country labels (we haven't had any requests for that before this), we certainly could add it for raster.

> Can you compare yourself to other OSM services then?

Sure. Here's a brief overview:

- Bill-as-you-go vs tier-based billing Many other services use usage-based billing, which is great for minimizing costs, but not so much for cost-prediction. We use tiers with soft-limits, so if you exceed your given usage for a few days of the month, it's not big deal and your bill doesn't change (e.g., you hit the HN front page!). Our initial customers told us consistent costs were very useful when handling client projects.

- Raw price We believed we could deliver a premium product at lower costs than other providers. Based on price comparisons, we believe we are on the right path to achieve this. We also do not treat certain applications (such as asset tracking) differently.

- Map design We didn't like many of the other provider's themes, so we built our own and plan to expand our portfolio over time.

- Goals We want to build a sustainable map service provider that respects the rights and data of its users (and its users' users)—not grow at any cost. Many of the other providers aggressively market for growth or capturing users' data, or marketing their own products on the map (e.g., reviews or other places), we want to get out of the way and allow your data to shine on our maps.

There are more differentiators, but these are some of the factors that led us to begin our own service.

We do use data from OSM, but if you want to use it reliably and consistently, you would need to host the data yourself or use a third-party service (such as Stadia Maps). OSM implements rate limits to high-traffic users and have no service guarantees. You also would have to create a theme (or use one of OSM's default themes).

So, the short answer is, yes, you could do this with OSM's data, but most companies prefer to pay to abstract away the management efforts.

We also provide other geo services, such as static maps and routing, which are often useful for companies and projects needing maps.

> Clearly, a lot of work has gone into making Stadia and it deserves to succeed.

Thank you for your kind words. We're definitely excited about the opportunities before us.

And thanks for the feedback!

I agree with your critique. We definitely need a better marketing website that conveys our mission and vision, as well as product offerings. I realized as I was reading my parent comment that most of the big selling points (which are things we strongly believe in) are not properly addressed in the website.

I think I know our next action item. :)

Re:Show HN: Stadia Maps: simple, affordable maps for every app on Wednesday January 31, 2018 @11:04AM (#16274837)
Hey fiatjaf, thanks for the suggestions!

> I think you should post the link directly in the Show HN.

We weren't sure the best way to do this—and it's too late to edit the post. :(

> Also, the site is a little too gray-blueish, it looks somewhat unprofessional because of that.

Thanks for the suggestion here; we probably should tweak the color scheme a bit. If you change themes on the map, the whole color scheme actually switches, so that's why it's heavily gray-blue skewed.

> The service I like more is the static maps configured with query strings. I didn't investigate to see how you control that and make people pay for it, but it is something I sometimes wish exists. https://docs.stadiamaps.com/static/ is more details of how to control it. For payment / usage tracking, we either use API keys or domain names, depending on the use case (if it's an app, website, etc.).

Re:Show HN: Stadia Maps: simple, affordable maps for every app on Wednesday January 31, 2018 @10:19AM (#16274476)
We will be here all day to answer your questions or suggestions. Thanks, HN!