the price data used for this
and EVE Asset Manager
and probably a killboard or two can be found in batches here
batches are grouped in 7 and 30 day temporal scopes, and by region / connectedhighsec (chs) / eve-global (all).
the processing works better on high-volume items. pay attention to the volume information in the rows.
and a "first" that is older than 7 or 30 days indicates this is not the freshest data.
on the narrower temporal or spatial scopes, less fresh data will be available.
the format is mostly the same as eve-api xml-rowset.
most people interested in pricing data for their app probably already have a parser that can be reused for this.
those are actual static files, updated several times a day, performance and availability of the http interface should not be an issue.
not even if evemon decided to use the data, without caching.
intended use is anything that prefers conservative stable longterm pricing over specific order-oriented data.
personally, i use the 30d-chs.
as usual, feedback and feature requests welcome.