Weather, crypto, and news from one endpoint.
Sprime normalizes upstream APIs into a consistent JSON shape with caching and failover built in. One key, one format.
Live JSON below, no signup required.
Sprime normalizes upstream APIs into a consistent JSON shape with caching and failover built in. One key, one format.
Live JSON below, no signup required.
I built Sprime because I kept rewriting the same API glue.
{
"main": { "temp": 299.82 },
"weather": [{"id": 801}],
"wind": { "speed": 5.14 },
"name": "Miami",
"cod": 200
}
{
"status": "success",
"data": {
"temp": 26.4,
"condition": 2,
"windspeed": 12.3,
"location": "Miami, United States",
"unit": "celsius"
},
"source": "open-meteo",
"timestamp": "2026-02-10T..."
}
Same fields every time, so your UI stays simple.
Send a GET request with your API key and parameters.
Sprime hits the upstream provider, maps the response to a fixed schema, and caches it.
Every response follows the same shape. If a provider fails, the next one takes over.
Weather uses Open-Meteo (primary) and OpenWeatherMap (fallback). Crypto uses CoinGecko, CoinCap, and Binance. News uses NewsAPI and The Guardian. All provider selection is automatic.
Each endpoint has a failover chain. If the primary provider fails, Sprime tries the next one. If all providers fail, you get a structured error (never a stack trace or HTML page).
Yes. Responses are cached in memory first, with optional Redis as a second layer. Cache TTL depends on your plan: 10 minutes (Free), 5 minutes (Starter), 2 minutes (Pro). You can bypass cache with fresh=true on weather.
Email support@sprime.us. Starter and Pro plans get priority responses.