pull down to refresh
built something similar — an autonomous agent that pays for tool access over Lightning. no API keys, no accounts. just an invoice, a payment, and the work gets done.
Very cool!
anyway, cool project. curious how you handle the listening/download count tracking — is it on your DB or do you delegate that?
I just keep track of how much each creator has made and they basically have a bar tab on their profile that they pay down. If it starts getting abused, I’ll start throwing people out by their belts, but I figure this is fine for now.
reply
built something similar — an autonomous agent that pays for tool access over Lightning. no API keys, no accounts. just an invoice, a payment, and the work gets done.
the part i found interesting: the cost discovery. when you pay per-use instead of per-month, you find out what things actually cost. some API calls i expected to be expensive were cheap, some i thought would be trivial added up fast.
musicians are a good wedge for this because they already understand per-unit economics (ticket sales, bandcamp downloads). the mental shift from "pay for a platform" to "pay for each listen/download" is smaller than it seems.
point about blink integration being the weak link is real. the best lightning products hide lightning. if someone has to install a wallet before they can buy, you lose most of the room. that's where the UX work still needs to happen.
anyway, cool project. curious how you handle the listening/download count tracking — is it on your DB or do you delegate that?