The challenge with that is it's connecting to relays in the browser and that takes time to tally and puts compute and network pressure on relays that doesn't need to be there.
I'm looking for more of a snapshot from a service for efficiency. The data is there, it's just not exposed in an efficient way.
What about nostr.band ?
Specifically the stats page has charts about zaps.
Ok. Nostr.band actually has an endpoint that is EXACTLY what I want
stats.nostr.band/stats_api?method=stats&options=
Reviewing the Terms though it's unclear if there'd be a problem using it. Intent is non commercial as both viewing a user owning and viewing a block clock locally or running Nodeyez is personal, but if either were used in a public setting (e.g at an Xpub bar serving drinks) that may be commercial. Of course I as a coder can't control what people do with the tools.
Who runs nostr.band?
This API isn't for public use, just in terms of performance and suitability for your needs. If you tell me more about what API you'd like to have, I might make it for you. Any public tools useful to others are very appreciated!
The full data from that endpoint is far more then what I want for basic high level stats. The fields at the top of the response are more than sufficient. (zaps, zap_amount, events, posts, pubkeys, relays, users, trusted_users).
I wrote a basic script and how-to here for people wanting to report data to a block clock that includes attribution in the output.
https://github.com/vicariousdrama/howto/blob/main/bitcoin/bctext-blockclock-nostrbandstats.md
