Doable but i believe would need to pull all the kind 9735 events, parse the description tag for originating pubkey that created the zap request compared to your pubkey.

To my understanding this is what zaplife does, possibly on an inbound stream routing from peered relays to gather it live and add a tally per pubkey receiver and sender.

Doing as an on demand type of call per pubkey would need to fetch chunks from relays. If you have a specific referenced event in mind, that narrows the data set. For what its worth, the Boost Zapper bot ive been working on tracks each zap it makes both to npub and lightning address.