At the moment no queries unless you sign with a nostr key with credits.

At the beginning it was totally open and in 2 weeks since the launch I got people abusing it, so I had to gate it somehow.

Yes it could be zap based but I would still have to check if your key has zapped vertex, so still sign in.

I could accept ecash in the request, but then your user would have to have a wallet, which imo is more selective than a sign in

Reply to this note

Please Login to reply.

Discussion

What about an NWC subscription?

but what's the difference between signing in and connecting your wallet with NWC?

I argue that the first is even easier, and it's free.

To clarify, I mean an NWC subscription to use the API from the app itself, not a per-user fee, and it doesnโ€™t require sign-in. I could choose to add a session fee on the app side, or keep it free to the user, depending on the cost.

Yes, this is a good idea.

You would have to use an API key in the client, which is the same as loading credits on a nostr key and using it in the client. It's basically the same

Right, the difference being that with NWC I can set a budget so thereโ€™s no need to manually top-up the balance.

yes this is true.

The UX for builders is not where I want it to be, but there is so much to build and I have to prioritise