it's not an API fault, it's the design flaw of sites that are using it, if they cached the things they request, they wouldn't need to rely on the API evrytime someone refreshes their site. those sites choose the easy way out, which only taxes the API and not their own site. it's just overwhelmed. No offense, but you clearly have no idea what you're talking about. If the API were returning 429s (rate limited), 500-level errors, or something else, (or simply timing out), then yes it'd likely be an overload issue. However, it's returning a 404 (not found) plus a custom status message, which is not indicative of a server being "overwhelmed".Furthermore, sites like gw2spidy actually do cache their data somewhat, as they use it for graphing price-over-time data. However, for a site like gw2spidy, relying solely on cached data is actually impossible; they'd not be able to show updated (i.e., current) price data at all if they did that.