For automatic payments, I think it is way better to just add a NWC uri with a set budget and give that to the service/pubkey generating content..l

NWC is a nerfed persistent connection that requires manual user pre-provisioning and doesn't even offer static payment codes or budget requests If you want better UX's you need to use better protocols, not browser extension slop

Happy to extend NWC to include those features if that is all it needs.

Needs a total rewrite for the handshake, not to mention the server handlers, it's literally leftover browser extension slop that never considered the bigger picture of ad-hoc and service connections Keep letting that NIP repo access go to your head though, muh numbers...