How to cache VerseDB responses and how to credit VerseDB wherever its data is shown.
Cache responses whenever possible to reduce load. Respect cache headers when provided.
Credit VerseDB on every page or screen that shows VerseDB data: "Comic book data from VerseDB" (or "Data from VerseDB"), linked to versedb.com, near the data and readable without a click or a tap. One credit per page or screen is enough, however many records it shows: one line under a list of search results, at the foot of an issue page, or in the footer of a bot's reply.
Licensed organizations work under the VerseDB Developers Terms, which add three things. Where the data lands somewhere they cannot place a credit or a link (a listing on another marketplace, a printed label, a spoken answer), they credit VerseDB in their own product or on its about page instead. Data used only inside the organization needs no credit. And they may store what their applications retrieve, refreshing each stored record at least every 30 days.