[{"data":1,"prerenderedAt":236},["ShallowReactive",2],{"blog-\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F":3,"related-blog-\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F":202},{"id":4,"title":5,"abstract":6,"author":7,"body":15,"description":182,"excerpt":6,"extension":183,"head":6,"image":184,"imageAlt":185,"keywords":186,"meta":194,"modified":6,"navigation":195,"path":196,"proficiencyLevel":6,"published":197,"rawbody":198,"schemaOrg":6,"schemaType":6,"section":187,"seo":199,"stem":200,"__hash__":201},"blog\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets.md","Beyond the Car: Routing for the Other 90% of Transport",null,{"name":8,"slug":9,"jobTitle":10,"bio":11,"twitterCreator":12,"sameAs":13},"Ian Wagner","ian-wagner","Founder & President \u002F COO","Ian is co-founder of Stadia Maps and leads engineering and operations. He works on routing, navigation, and the technical foundations that keep customer applications reliable at scale.","@ianthetechie",[14],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fian-w-wagner\u002F",{"type":16,"value":17,"toc":173},"minimark",[18,22,29,34,43,47,50,61,70,79,83,91,126,130,145,148,157,160],[19,20,5],"h1",{"id":21},"beyond-the-car-routing-for-the-other-90-of-transport",[23,24,25],"blockquote",{},[26,27,28],"p",{},"Standard \"car-first\" routing APIs often fail to account for the unique legal and physical constraints of specialized fleets. Stadia Maps bridges this gap by leveraging the Valhalla routing engine and OpenStreetMap data to provide granular, modal-specific routing for everything from 10-ton trucks and e-bikes to low-speed vehicles (LSVs).",[30,31,33],"h2",{"id":32},"the-problem","The Problem",[26,35,36,37,42],{},"Standard consumer mapping apps are excellent at getting a passenger car from point A to point B, but the \"car-first\" default is a significant limitation for professional use cases. The moment a business needs to route a 10-ton truck, a delivery e-bike, or a neighborhood electric vehicle, most ",[38,39,41],"a",{"href":40},"\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F","Directions APIs"," fall apart. Such platforms often lack the flexibility required for specialized fleets and fail to account for the unique legal and physical constraints these vehicles face.",[30,44,46],{"id":45},"the-logic-gap","The Logic Gap",[26,48,49],{},"Generic routing engines often treat a 10-ton semi-truck the same as an e-bike, leading to dangerous route suggestions or illegal maneuvers. Developers shouldn't have to build custom logic layers just to ensure a vehicle stays on a legal road.",[26,51,52,53,60],{},"Stadia Maps solves this by processing ",[38,54,59],{"href":55,"rel":56,"target":58},"https:\u002F\u002Fwiki.openstreetmap.org\u002Fwiki\u002FRouting_profiles",[57],"external","_blank","OpenStreetMap (OSM) data"," into a specialized routing graph. Our engine extracts both implicit and explicit vehicle access rules, bridging the gap between raw map data and safe navigation.",[26,62,63,64,69],{},"By providing tailored routing profiles for diverse vehicle archetypes, we ensure that every calculation respects the physical and legal constraints of each asset. We leverage the open-source ",[38,65,68],{"href":66,"rel":67,"target":58},"https:\u002F\u002Fvalhalla.github.io\u002Fvalhalla\u002F",[57],"Valhalla routing engine",", which allows you to customize desirability factors when you make an API request.",[26,71,72,73,78],{},"Specialized profiles for the 10-ton truck and the e-bike enable logistics platforms to automate fleet dispatch and ",[38,74,77],{"href":75,"rel":76,"target":58},"https:\u002F\u002Fwww.mckinsey.com\u002Ffeatured-insights\u002Fmckinsey-explainers\u002Fwhat-is-micromobility",[57],"micromobility"," startups to provide riders with reliable, safe navigation.",[30,80,82],{"id":81},"the-stadia-maps-difference","The Stadia Maps Difference",[26,84,85,90],{},[38,86,89],{"href":87,"rel":88,"target":58},"https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F",[57],"Dynamic costing"," gives you control over dozens of parameters on the fly, ensuring fleets navigate complex environments efficiently. Key capabilities include:",[92,93,94,102,108,114],"ul",{},[95,96,97,101],"li",{},[98,99,100],"strong",{},"Vehicle Subtypes:"," Distinguish between mountain bikes and road bikes, or golf carts and other Low-Speed Vehicles (LSVs).",[95,103,104,107],{},[98,105,106],{},"Physical Preferences:"," Configure the engine to avoid hills for scooters, disallow U-turns for long trucks, or avoid toll roads entirely.",[95,109,110,113],{},[98,111,112],{},"Precision Waypoints:"," Specify that a waypoint must be visited from a particular side of the road, a critical feature for curb-side delivery and waste management.",[95,115,116,119,120,125],{},[98,117,118],{},"Direct Map Edits:"," Map errors shouldn't take months to fix. Make your own edits directly. Updates can be live in our ",[38,121,124],{"href":122,"rel":123,"target":58},"https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fvalhalla\u002F",[57],"routing engine"," within days.",[30,127,129],{"id":128},"specialized-mobility-solutions","Specialized Mobility Solutions",[26,131,132,133,138,139,144],{},"Flexibility enables business models that standard providers simply cannot support. A prime example is our work with municipalities such as ",[38,134,137],{"href":135,"rel":136,"target":58},"https:\u002F\u002Fpeachtree-city.org\u002F216\u002FPaths-Golf-Carts",[57],"Peachtree City, GA",", and ",[38,140,143],{"href":141,"rel":142,"target":58},"https:\u002F\u002Fwww.districtgov.org\u002Frecreation\u002Ftrails.aspx",[57],"The Villages, FL",".",[26,146,147],{},"These communities have extensive, legally regulated networks for golf carts and LSVs. Stadia Maps provided the only routing profile customizable enough to fit their local ordinances, such as prohibiting LSVs on roads with speed limits over 35 mph.",[26,149,150,151,156],{},"We support almost a dozen routing profiles out of the box, including bus, motorcycle, and pedestrian, with ",[38,152,155],{"href":153,"rel":154,"target":58},"https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F",[57],"matrix routing limits"," that are often orders of magnitude higher than those of our competitors. Whether you are optimizing a transit authority's bus training or dispatching a fleet of e-bikes, your routing engine should adapt to your vehicle, not the other way around.",[158,159],"hr",{},[26,161,162,167,168,172],{},[38,163,166],{"href":164,"rel":165,"target":58},"https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F",[57],"Create a free account"," to explore our specialized routing profiles, or ",[38,169,171],{"href":170},"mailto:support@stadiamaps.com","contact our team"," to discuss a custom solution tailored to your unique vehicle constraints.",{"title":174,"searchDepth":175,"depth":175,"links":176},"",4,[177,179,180,181],{"id":32,"depth":178,"text":33},2,{"id":45,"depth":178,"text":46},{"id":81,"depth":178,"text":82},{"id":128,"depth":178,"text":129},"Car-first routing APIs fail trucks, e-bikes, and LSVs. See how Stadia Maps uses Valhalla and OpenStreetMap to deliver modal-specific routing that respects each vehicle's physical and legal constraints.","md","\u002Fimages\u002Fcontent\u002Fspecialized-routing-og.png","Beyond the Car: Routing for the Other 90% of Transport — Stadia Maps",[187,188,189,190,191,192,193],"Routing","Navigation","Valhalla","OpenStreetMap","Fleet Routing","Micromobility","Low-Speed Vehicles",{},true,"\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets","2026-05-26","---\ndescription: >-\n  Car-first routing APIs fail trucks, e-bikes, and LSVs. See how Stadia Maps\n  uses Valhalla and OpenStreetMap to deliver modal-specific routing that\n  respects each vehicle's physical and legal constraints.\npublished: \"2026-05-26\"\nimage: \u002Fimages\u002Fcontent\u002Fspecialized-routing-og.png\nimageAlt: \"Beyond the Car: Routing for the Other 90% of Transport — Stadia Maps\"\nsection: \"Routing\"\nkeywords:\n  - Routing\n  - Navigation\n  - Valhalla\n  - OpenStreetMap\n  - Fleet Routing\n  - Micromobility\n  - Low-Speed Vehicles\nauthor:\n  name: \"Ian Wagner\"\n  slug: \"ian-wagner\"\n  jobTitle: \"Founder & President \u002F COO\"\n  bio: \"Ian is co-founder of Stadia Maps and leads engineering and operations. He works on routing, navigation, and the technical foundations that keep customer applications reliable at scale.\"\n  twitterCreator: \"@ianthetechie\"\n  sameAs:\n    - \"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fian-w-wagner\u002F\"\n---\n\n# Beyond the Car: Routing for the Other 90% of Transport\n\n> Standard \"car-first\" routing APIs often fail to account for the unique legal and physical constraints of specialized fleets. Stadia Maps bridges this gap by leveraging the Valhalla routing engine and OpenStreetMap data to provide granular, modal-specific routing for everything from 10-ton trucks and e-bikes to low-speed vehicles (LSVs).\n\n## The Problem\n\nStandard consumer mapping apps are excellent at getting a passenger car from point A to point B, but the \"car-first\" default is a significant limitation for professional use cases. The moment a business needs to route a 10-ton truck, a delivery e-bike, or a neighborhood electric vehicle, most [Directions APIs](\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F) fall apart. Such platforms often lack the flexibility required for specialized fleets and fail to account for the unique legal and physical constraints these vehicles face.\n\n## The Logic Gap\n\nGeneric routing engines often treat a 10-ton semi-truck the same as an e-bike, leading to dangerous route suggestions or illegal maneuvers. Developers shouldn't have to build custom logic layers just to ensure a vehicle stays on a legal road.\n\nStadia Maps solves this by processing [OpenStreetMap (OSM) data](https:\u002F\u002Fwiki.openstreetmap.org\u002Fwiki\u002FRouting_profiles) into a specialized routing graph. Our engine extracts both implicit and explicit vehicle access rules, bridging the gap between raw map data and safe navigation.\n\nBy providing tailored routing profiles for diverse vehicle archetypes, we ensure that every calculation respects the physical and legal constraints of each asset. We leverage the open-source [Valhalla routing engine](https:\u002F\u002Fvalhalla.github.io\u002Fvalhalla\u002F), which allows you to customize desirability factors when you make an API request.\n\nSpecialized profiles for the 10-ton truck and the e-bike enable logistics platforms to automate fleet dispatch and [micromobility](https:\u002F\u002Fwww.mckinsey.com\u002Ffeatured-insights\u002Fmckinsey-explainers\u002Fwhat-is-micromobility) startups to provide riders with reliable, safe navigation.\n\n## The Stadia Maps Difference\n\n[Dynamic costing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F) gives you control over dozens of parameters on the fly, ensuring fleets navigate complex environments efficiently. Key capabilities include:\n\n- **Vehicle Subtypes:** Distinguish between mountain bikes and road bikes, or golf carts and other Low-Speed Vehicles (LSVs).\n- **Physical Preferences:** Configure the engine to avoid hills for scooters, disallow U-turns for long trucks, or avoid toll roads entirely.\n- **Precision Waypoints:** Specify that a waypoint must be visited from a particular side of the road, a critical feature for curb-side delivery and waste management.\n- **Direct Map Edits:** Map errors shouldn't take months to fix. Make your own edits directly. Updates can be live in our [routing engine](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fvalhalla\u002F) within days.\n\n## Specialized Mobility Solutions\n\nFlexibility enables business models that standard providers simply cannot support. A prime example is our work with municipalities such as [Peachtree City, GA](https:\u002F\u002Fpeachtree-city.org\u002F216\u002FPaths-Golf-Carts), and [The Villages, FL](https:\u002F\u002Fwww.districtgov.org\u002Frecreation\u002Ftrails.aspx).\n\nThese communities have extensive, legally regulated networks for golf carts and LSVs. Stadia Maps provided the only routing profile customizable enough to fit their local ordinances, such as prohibiting LSVs on roads with speed limits over 35 mph.\n\nWe support almost a dozen routing profiles out of the box, including bus, motorcycle, and pedestrian, with [matrix routing limits](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F) that are often orders of magnitude higher than those of our competitors. Whether you are optimizing a transit authority's bus training or dispatching a fleet of e-bikes, your routing engine should adapt to your vehicle, not the other way around.\n\n---\n\n[Create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) to explore our specialized routing profiles, or [contact our team](mailto:support@stadiamaps.com) to discuss a custom solution tailored to your unique vehicle constraints.\n",{"title":5,"description":182},"blog\u002Fbeyond-the-car-routing-for-specialized-fleets","pEMIlWjmKWwfavkw0_6WCqGGkIMu9m-TIe_WNlm6e3U",[203,214,226],{"title":204,"description":205,"path":206,"published":207,"keywords":208,"rawbody":213},"Why Basic OpenStreetMap Routing Needs Real-Time Traffic","OpenStreetMap is a world-class road network, but without real-time traffic it's a static dataset. Here's why algorithmic ETAs fall apart in production logistics and how Stadia Maps closes the gap with TomTom-powered routing.","\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic","2026-05-12",[187,188,190,209,210,211,212],"Traffic Data","Matrix Routing","Logistics","TomTom","---\ndescription: >-\n  OpenStreetMap is a world-class road network, but without real-time traffic\n  it's a static dataset. Here's why algorithmic ETAs fall apart in production\n  logistics and how Stadia Maps closes the gap with TomTom-powered routing.\nexcerpt: >-\n  OpenStreetMap is great geography, but without real-time traffic it falls\n  short on ETAs. Stadia Maps closes the gap with TomTom-powered routing.\npublished: \"2026-05-12\"\nimage: \u002Fimages\u002Fcontent\u002Fosm-traffic-og.png\nsection: \"Routing\"\nkeywords:\n  - Routing\n  - Navigation\n  - OpenStreetMap\n  - Traffic Data\n  - Matrix Routing\n  - Logistics\n  - TomTom\nauthor:\n  name: \"Ian Wagner\"\n  slug: \"ian-wagner\"\n  jobTitle: \"Founder & President \u002F COO\"\n  bio: \"Ian is co-founder of Stadia Maps and leads engineering and operations. He works on routing, navigation, and the technical foundations that keep customer applications reliable at scale.\"\n  twitterCreator: \"@ianthetechie\"\n  sameAs:\n    - \"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fian-w-wagner\u002F\"\n---\n\n# Why Basic OpenStreetMap Routing Needs Real-Time Traffic\n\n> OpenStreetMap (OSM) provides a world-class geographic foundation, but it remains a static dataset. Without real-time traffic integration, routing engines must rely on algorithmic proxies—like road class and legal speed limits—which often lead to unreliable ETAs and logistics bottlenecks.\n\n## The Problem\n\n[OpenStreetMap (OSM)](https:\u002F\u002Fwww.openstreetmap.org\u002Fabout) is one of the world's leading road maps, but a persistent gap remains between fixed geographic data and a [live navigation experience](\u002Fproducts\u002Frouting-navigation\u002F). Without dedicated traffic data, Estimated Times of Arrival (ETAs) are essentially educated guesses. While OSM is excellent at mapping the world's road network, a static dataset cannot capture the actual driving conditions at this exact moment. In enterprise-grade logistics, the lack of live data is often the first significant technical hurdle.\n\n## The Limits of Algorithmic Guesswork\n\nIn the absence of real-time data, a routing engine must estimate travel speeds based on tags and a few common proxies:\n\n- **Road Class:** Assuming a motorway is always faster than a residential street.\n- **Tagged Speed Limits:** Using the legal maximum as the baseline (when the tag even exists).\n- **Network Density:** Adjusting for urban vs. rural environments.\n- **Time of Day:** Using low-granularity buckets like \"daytime\" and \"nighttime.\"\n\nReal-world data show wild variances compared to these static estimates. Road class is a blunt instrument for predicting speed. Missing speed limit tags in open datasets force routing engines to rely on broad averages, resulting in unreliable ETAs and logistics delays. Rule-based algorithms are also notoriously bad at predicting choke points because open datasets don't account for traffic light timings, congestion near specific exits, or the \"invisible\" friction of a busy intersection.\n\n## The Stadia Maps Difference\n\nTo move from guesswork to precision, we integrated [TomTom's global traffic data](https:\u002F\u002Fwww.tomtom.com\u002Fproducts\u002Ftraffic-apis\u002F) directly into the [Stadia Maps routing engine](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F). High-resolution historical profiles and live feeds allow for accurate, real-time routing. We provide this through three key technical pillars:\n\n1. **Global Coverage:** Access to consistent data across more countries than almost any other vendor.\n2. **Rapid Updates:** A traffic latency of approximately two minutes allows our API to suggest alternate routes almost as soon as a wreck occurs.\n3. **Historical Profiles:** Deep granularity forms the backbone of predictive routing. High-resolution historical data enables accurate, time-dependent routing in advance, allowing you to plan a route for Tuesday at 8:00 AM based on what might happen on Tuesdays at 8:00 AM.\n\n## Fleet Intelligence at Scale\n\nFor dispatch, optimization, and fleet operations, [matrix routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F) (calculating the time and distance between many origins and destinations) is the engine's most critical function.\n\nThe Stadia Maps infrastructure supports matrix requests that are significantly larger than most competitors allow on standard plans. By integrating traffic data directly into these large-scale requests, we eliminate the need for developers to split requests into smaller chunks, reducing unnecessary complexity and latency.\n\nDevelopers maintain full agency over their implementation. We provide the fastest route based on live conditions, but the frequency of re-routing remains entirely in your control. Choice of revalidation frequency puts you in charge of the trade-off between real-time accuracy and [scaling costs](\u002Fpricing\u002F), ensuring your bills remain as predictable as your ETAs.\n\n---\n\n[Create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) to start building with real-time traffic and high-performance routing today. Our [documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F) provides everything you need to integrate TomTom-powered precision into your existing OSM workflow.\n",{"title":215,"description":216,"path":217,"published":218,"keywords":219,"rawbody":225},"Traffic-Influenced Routing Is Here (Public Preview)","Traffic-influenced routing is now available in public preview, bringing live and historical traffic data to standard routing, optimized routing, map matching, isochrones, and time\u002Fdistance matrices.","\u002Fblog\u002Ftraffic-influenced-routing-in-public-preview","2026-04-14",[220,221,222,191,223,224],"Traffic-Influenced Routing","Real-Time Traffic","Route Optimization","ETA Accuracy","Public Preview","---\ndescription: >-\n  Traffic-influenced routing is now available in public preview,\n  bringing live and historical traffic data to standard routing,\n  optimized routing, map matching, isochrones, and time\u002Fdistance matrices.\npublished: 2026-04-14\nkeywords:\n  - Traffic-Influenced Routing\n  - Real-Time Traffic\n  - Route Optimization\n  - Fleet Routing\n  - ETA Accuracy\n  - Public Preview\n---\n\n# Traffic-Influenced Routing Is Here (Public Preview)\n\nRouting without traffic data works for a lot of use cases.\nBut dispatch systems need ETAs that account for rush hour,\nride-hailing platforms need accurate pickup times,\nand telematics pipelines need traffic context to reconstruct accurate travel times.\nFor these use cases, \nrouting and ETAs that only reflect the road network,\nwithout accounting for what's happening on it,\nfall short.\n\n## Available Today\n\nStarting today,\nStadia Maps customers on Standard and Professional plans can use traffic-influenced routing,\na public preview that brings live and historical traffic data into route calculations across\n[standard routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F),\n[optimized routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Foptimized-routing\u002F),\n[map matching](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fmap-matching\u002F),\n[isochrones](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F),\nand [time\u002Fdistance matrices](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F).\n\nThe traffic data comes from TomTom and covers 80+ countries at launch,\nlayered onto the same OSM-based road network you already use.\nYou get two tiers to choose from,\nand you can pick per request,\nso you can use both in the same app:\n\n- **Adaptive** balances accuracy and credit cost.\n  A good fit for general routing, isochrones, and map matching.\n- **Premium** combines real-time conditions with predictive data for the highest accuracy.\n  Ideal where precise ETAs matter,\n  like live fleet routing and matrix requests.\n\nBoth tiers work across auto, bus, taxi, and truck profiles.\nAnd because this is Stadia Maps,\nyou can still tune all the same profile parameters you're used to.\nTraffic-influenced routing builds on the full Stadia Maps routing stack you already know:\nnot a locked-down replacement,\nand without the proprietary detour.\n\n## Pricing That Scales With You, Not Against You\n\nWe built this the way we build everything:\nwith fair, transparent pricing and no gotchas.\nYou pick the routing profile and traffic tier per request,\nuse your existing credits with no surprise minimums,\nand upgrade with a single profile parameter change.\nYou can finally use traffic-influenced routing with no contract renegotiation,\nno new SDK,\nand no mandatory user tracking;\nyour users' privacy is still the default.\n\n## Get Started\n\nTraffic-influenced routing is available now in public preview.\n \n- See the [Product page](https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002Frouting-navigation\u002Ftraffic-influenced-routing\u002F) for an overview\n- Read the [Routing docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F#traffic-influenced-profiles) for profile details\n- Get started with the [Integration guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fguides\u002Fgetting-the-best-routes-with-valhalla-turn-by-turn-directions-apis\u002F#traffic-influenced-routing)\n \nAlready on a Standard or Professional plan?\nYou can start using it right now.\nOn a different plan?\n[Reach out](mailto:support@stadiamaps.com?subject=Traffic-Influenced%20Routing%20Trial) and we can set you up with a trial.",{"title":227,"description":228,"path":229,"published":230,"keywords":231,"rawbody":235},"Fall 2024 Credit Schedule Updates","Increased matrix element limits, navigation aids with OSRM support for routing, and adjustments to the credit schedule.","\u002Fblog\u002F2024-matrix-navigation-credit-updates","2024-09-12",[210,188,232,233,234],"OSRM","Credits","Pricing","---\ndescription: \"Increased matrix element limits, navigation aids with OSRM support for routing, and adjustments to the credit schedule.\"\npublished: 2024-09-12\nkeywords:\n  - Matrix Routing\n  - Navigation\n  - OSRM\n  - Credits\n  - Pricing\n---\n\n# Fall 2024 Credit Schedule Updates\n\nFor nearly a decade, we’ve helped companies build successful products using location APIs by delivering private,\nfinancially scalable services backed by exceptional human support. In the last two years, we’ve launched two major\nproduct lines: Geocoding and Satellite Imagery, and, in the background, we’ve significantly expanded our Routing API\ncapabilities. With all of these improvements and new functionality, we’re updating our API credit schedule. Current \npricing plans, including base price and additional credit rates, will remain unchanged.\n\nStarting October 1st, we're reducing credits used by all Geocoding, Autocomplete Search, and Isochrone APIs.\nFor some Routing and Matrix APIs, we're increasing credits used. \nWe’re also opening the Optimized Routing and Matrix APIs to the Standard Plan, \nallowing more customers take advantage of our most advanced APIs.\n\n## Even More Affordable Geocoding\n\nOur Geocoding product graduated out of beta just over a year ago, and since then, we’ve reached new levels of scale.\nThis allows us to reduce credit used from 30 to 20 credits per API request—a 30% reduction. The update\napplies to all geocoding and autocomplete search endpoints.\n\n## Improved Routing & Time\u002FDistance Matrix\n\nRouting is one of our oldest services, and over the years, we’ve built it into a world-class product, \nwith customizability few providers can match. \nToday it gets a little bit better.\n\n### Voice & Banner Navigation Aids for Routing & Map Matching\n\nAvailable immediately, \nour [Routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news){ target=\"_blank\" }\nand [Map Matching](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fmap-matching\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news){ target=\"_blank\" }\nAPIs will support navigation aids, \nincluding detailed maneuver information optimized for display, \nand voice prompts in over 25 languages. \nThe new navigation aids are available in OSRM format,\nwhich is used by many mobile SDKs, \nincluding our own [Ferrostar](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fferrostar\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news){ target=\"_blank\" }. Where available, these responses also include detailed\nintersection information and speed limits in a single API request.\n\nEach request including these aids will use 30 credits and are available to all Stadia Maps accounts.\n\n### Bigger, Better Matrices\n\nOur [Time\u002FDistance Matrix API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news){target=_blank} \nis a critical component for many logistics applications, \nincluding solving the Rich Vehicle Routing Problem. \nUntil now, we’ve had to severely limit our matrix offering. \nThanks to recent infrastructure enhancements, we’re excited to introduce the following major improvements:\n\n1. We're opening the Matrix API to Standard Plan users. Previously, this was limited to our Professional and Enterprise\n   Plans.\n2. We’re increasing the maximum matrix element count by a factor of 10: from 1,000 to 10,000 (for the Professional\n   Plan).\n3. We're offering matrices larger than 10,000 elements by custom agreement. [Contact us to learn more.](mailto:entsales@stadiamaps.com?subject=Time%2FDistance%20Matrix%20Limits)\n\n### Matrix Billing Updates\n\nMatrix API requests will now calculate used credits differently. \nInstead of a flat number credits per request, the Matrix API will use credits per matrix element. \nEach matrix element will consume 10 credits, with no additional charge per request. \nThis adjustment reflects the varying sizes of matrix requests and aligns with industry standard practice. \nIt also enables us to support larger matrices more effectively going forward.\n\n### Other Routing Credit Changes\n\nIsochrone (reachable range) requests will use fewer credits, at 20 credits per request. \nOptimized and Standard routing requests will use more credits, at 40 and 20 credits per request, respectively.\n\n## Credit Change Overview\n\nSince we’ve made quite a few adjustments to the credit schedule, here’s an overview of the changes:\n\n| API                                                                                                                                                                                                                           | Previous                 | Updated                                                        |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------------------------------------------|\n| [Optimized routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Foptimized-routing\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)                          | 30 credits per request   | 40 credits per request & \u003Cbr> available on the Standard Plan   |\n| [Standard routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)                            | 10 credits per request   | 20 credits per request                                         |\n| [Standard routing (OSRM Format)](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)              | -                        | 30 credits per request                                         |\n| [Map matching (OSRM Format)](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fmap-matching\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)                      | -                        | 30 credits per request                                         |\n| [Matrix](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)                                  | 30 credits *per request* | 10 credits *per element* & \u003Cbr> available on the Standard Plan |\n| [Isochrones](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)                                        | 30 credits per request   | 20 credits per request                                         |\n| [Forward Geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)               | 30 credits per request   | 20 credits per request                                         |\n| [Reverse Geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)       | 30 credits per request   | 20 credits per request                                         |\n| [Structured Geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news) | 30 credits per request   | 20 credits per request                                         |\n| [Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)       | 30 credits per request   | 20 credits per request                                         |\n| [Place Lookup](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fplace-lookup\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)              | 30 credits per request   | 20 credits per request                                         |\n\n## Learn More & Next Steps\n\n- [Create an account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_campaign=matrix_navigation_credit_updates&utm_content=matrix_navigation_credit_update_news)\n  to get your API key. You can start building today without a credit card!\n- Join our community on [Discord](https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT) or [Slack](https:\u002F\u002Fslack.openstreetmap.us\u002F) to share what you're working on or get help.\n- Follow us 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 [mailing list](https:\u002F\u002Feepurl.com\u002Fgs51fD) to stay up to date.",1779866017945]