Accounts are trivial to create so you can keep rotating them as often as you want.
Not as fine grained as once per request, but the advantage is I don't have to deal with change.
How do you deal with change in the case of cashu?
If you use smaller denominations, how much do you send if you don't know what the request will end up costing?
nostr:nprofile1qqsdy27dk8f9qk7qvrm94pkdtus9xtk970jpcp4w48k6cw0khfm06mspp4mhxue69uhkummn9ekx7mqpz9mhxue69uhkummnw3e82cfwvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t09x35fm discussed the challenges of change. In SEC-04, nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsef7u3d and I worked on running CI jobs as DVMs but paid with cashu and returning change. The user (or agent) just pays as much as they want, the more they pay the more the timeout is and the more change they potentially get back. We got an alpha version working with testnuts.
That's pretty cool. And great to hear that you guys figured it out.
If nostr:nprofile1qqsdy27dk8f9qk7qvrm94pkdtus9xtk970jpcp4w48k6cw0khfm06mspp4mhxue69uhkummn9ekx7mqpz9mhxue69uhkummnw3e82cfwvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t09x35fm went for this, how would we configure Roocode for example to work with cashu tokens?
This appears like the biggest problem the Open AI API standard supported by all the tools doesn't include support. I've not used routstr, etc to see how they work but I assume the user would need to run a local proxy to inject the tokens and collect the change.
Would this be a big deal? I'm not sure. The service could run their own custodial proxy to onboard new users with the account based experience nostr:nprofile1qqsdy27dk8f9qk7qvrm94pkdtus9xtk970jpcp4w48k6cw0khfm06mspp4mhxue69uhkummn9ekx7mqpz9mhxue69uhkummnw3e82cfwvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t09x35fm do today.
