ROAD INTELLIGENCE, FOR BUILDERS

Know the
road ahead.

Bring detailed surface materials into your cycling and mapping applications—from asphalt and concrete to gravel, dirt, and paving stones.

Explore API plans See how it works

Built on OpenStreetMap. Made for the ride.

SURFACE EXPLORERInteractive example
SELECTED SURFACEAsphaltTagged in the source data"surface_tagged": true
Illustrative route · not live map data
Explore the surface types

A focused API for products that move.

Route planningCycling & gravelRace preparationMapping applications

MORE THAN A LINE ON A MAP

Give every route
more context.

Help riders understand what’s under their wheels. Specific material values are available where the source data supports them; broader and unknown values remain visible.

01 / DISCOVER

See what’s under the wheels.

Look up specific surfaces, including asphalt, concrete, gravel, and dirt, at a point or across route segments.

02 / UNDERSTAND

Keep estimates in perspective.

Distinguish explicit surface tags from values estimated using road type. A mapped road doesn’t always have a known surface.

03 / INTEGRATE

Build it into your product.

Use HTTPS, API key authentication, and JSON responses to add surface context to your existing workflow.

A SMALL API. A USEFUL LAYER.

From coordinates
to context.

Send a location. Get the nearby road’s surface, road type, and distance from your point. Batch endpoints help you work through a route.

Read the API documentation

Keep API keys on your server.
Review the target region before integrating.

curl --get \
  'https://surface.enduranceplayground.com/api/surface/point' \
  -H 'X-API-Key: YOUR_API_KEY' \
  --data-urlencode 'lat=30.2672' \
  --data-urlencode 'lon=-97.7431'
Illustrative response · actual values vary by location

COVERAGE THAT YOU CAN EVALUATE

Start with the roads
your users ride.

Our dataset includes the United States and selected international regions. Availability and surface-tag detail vary by location. We’re preparing a refreshed data release and expanding priority areas.

Explore coverage & data quality
01United States

All 50 states and DC represented in the existing dataset.

02International regions

Selected coverage across Europe and other cycling destinations.

03Your target routes

Evaluate local availability and surface detail before launch.

SELF-SERVICE ACCESS, COMING NEXT

Your next product.
A better surface layer.

We’re preparing API plans for developers and growing applications, with self-service sign-up and billing.

Explore API plans

Commercial plans are in preparation. Live purchases are not yet available.

A few things to know.

Is a surface value always directly mapped?

No. Some roads have an explicit OpenStreetMap surface tag; others use an estimate based on road type. The API’s surface_tagged field helps you distinguish those cases. Unknown values and missing roads need to remain visible in your application.

Can I buy an API plan today?

Self-service paid plans are being prepared. The plans page will show prices, usage allowances, and checkout availability when they are finalized. Existing API customers can continue using their current access.

Does the API cover every road?

No. Imported regions and surface tags vary, and a road’s presence does not establish its surface condition. Check our coverage notes and evaluate your target routes before relying on the data.

Where does the underlying data come from?

The road data is derived from OpenStreetMap contributors and is available under the Open Database License. See OpenStreetMap’s attribution and licensing information. The planned commercial offering provides hosted API access to this data.