Pure Data Feeds

Ecosystem

One ingestion layer, every product fed

External data — weather, mortgage & benchmark rates, property-tax rates — is pulled once by a cron into pure_api_feeds, reviewed for big moves, and read by every surface. Keys stay server-side, third parties get hit once instead of per page, and the same cached, summarized value shows everywhere. Sources today: API Ninjas + OpenWeatherMap.

Live now — ingested feeds

Read straight from pure_api_feeds. Refreshed by the pure-data-feeds cron (weather 2-hourly, rates daily).
Loading live feeds…

API Ninjas — where each feed earns its keep

120+ endpoints; these are the ones that move the needle for a real-estate platform. "Live" = ingesting today.
EndpointFeeds intoWhy it mattersStatus

Recommendations — getting the most from the feed

How it's wired. The pure-data-feeds cron holds the only API keys (Edge secrets), writes summaries + flags big moves, and every page reads the cached row — so a rate jump notifies active mortgage & insurance applications, and rain in the forecast auto-reschedules roof & exterior jobs. A second cron, pure-property-score, turns the property record into the nightly Pure Home Score. Handoff to Code: set API_NINJAS_KEY + OPENWEATHER_KEY and schedule both.