Oh zap split is interesting

The payment right now is for the work of actually translating the content because the AI models, APIs and services that I’m using cost money 

But any zaps posted on the translated content itself could definitely be split with the originator

I don’t know how to do that yet though

Maybe our boy @NotBiebs knows a good way to do that 

 There’s instructions how to do it in nip-57. It kinda sucks though. Not all clients support it and the UX is terrible unless the person zapping is using NWC. 

 Couldn’t I just take the lightning address from the creator’s npub (Kind 0 metadata) and send sats using Alby API if the translated event has received a zap?

I would need to change my bot’s lightning wallet to Alby at that point 

But I don’t know how to pay a lightning address yet

Don’t I ping a webhook and get a bolt11 address or something? 

 And what will you do if a payment fails? There’s a many different ways a lightning payment can fail. Personally I wouldn’t go down this rabbit hole. 

 I’d just follow the spec. Then at least some of the zaps will be split and you don’t have to write much code.