How Developers Are Building with Forge

Two years ago, we shipped Forge v1 with a simple premise: developers deserve a weather and geocoding API that doesn't require a PhD in distributed systems to use well. Today, we're seeing that bet play out in ways we didn't predict. Here are three stories from teams doing remarkable things with Forge.

Route Optimization at Scale: Logistics ETA

LogisticsPro, a last-mile delivery optimizer serving 15,000 drivers across North America, uses Forge to power their ETA engine. Weather affects delivery times—rain and snow slow routes, visibility impacts safety decisions. Their platform ingests real-time weather data via Forge's /v1/weather endpoint, keying queries by route segments.

The challenge was cost. They needed weather data for thousands of routes per minute, and query-per-location would have been prohibitive. Their solution: batch geohashing. They discretize the continent into 12-meter cells, cache Forge responses at the cell level with a 10-minute TTL, and compute deltas between adjacent cells for micro-routing. By combining Forge's low-latency responses with intelligent caching, they reduced their API spend by 67% while improving ETA accuracy. They now report sub-minute ETA variance in 91% of deliveries.

What impressed us most: they didn't ask us to build something custom. They understood the constraints and built a smarter client.

Precision Irrigation: WeatherTuned

WeatherTuned is a two-year-old startup helping farms in the Great Plains reduce irrigation costs through hyper-local weather forecasting. They deploy soil moisture sensors and weather stations, then use Forge's geocoding API to map field boundaries and Forge's weather data to predict moisture recovery over the next 5 days.

Their pitch to farmers is simple: we'll tell you exactly when and how much to water, saving you 20-30% on water costs and protecting yield. That requires sub-kilometer accuracy—two farms five kilometers apart can have different cloud cover and wind patterns. Forge's /v1/geocode endpoint handles address-to-coordinate resolution for over 40 million farm addresses in their database, and /v1/weather gives them the 7-day forecast they need.

The economics work because they don't need enterprise contracts or custom SLAs. They're on our Pro plan, and it's transparent and predictable. Their typical farm account costs them $12 in API credit per season—less than the cost of a single extra irrigation cycle.

Running Rewards: WorkoutWeather

WorkoutWeather is a consumer app that gamifies running by overlaying weather conditions onto your activity. Ran a 10K in 35-degree rain? That's worth more points than a 10K in calm 68-degree weather. Users love it because it makes their workouts feel like achievements, not just metrics.

Under the hood, they make a Forge weather call for each run's start location and time, retroactively. That means they're making tens of thousands of requests per day, often for historical coordinates. Their biggest insight: they pre-geocode every run's start location the moment a user creates it, keeping the coordinate for future lookups. They rarely call our geocoding API twice for the same location.

They built an elegant SDK integration in their React Native app, handling rate limits gracefully with exponential backoff. When they hit a 429, their app queues the request and retries it after reading the Retry-After header. Users don't see errors—the system just works.

What We've Learned

These three teams taught us something important: the best API customers aren't asking for more features. They're asking for reliability, fair pricing, and clear documentation. LogisticsPro didn't need a custom batching endpoint. WeatherTuned didn't need special farm-data support. WorkoutWeather didn't need SDK magic. They needed an API they could trust, understand, and build on top of.

We're honored to power their success. If you're building something with Forge, we'd love to hear about it—reach out at community@forge-api.dev.