a better solution is to decouple the query from individual api requests by adding a caching layer. we’ll get there eventually

Good stuff 👍 Right now you’re using “can” and “should” which are somewhat vague. What happens if bots don’t do something they should?

Consider clarifying requirements using the following RFC-style language: “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”.

ref: https://www.rfc-editor.org/rfc/rfc2119