Replies (5)

The translation API supports both api_key and NIP-98 authentication. For a smoother experience, you can use NIP-98 auth once to obtain the api_key, then use the api_key for subsequent requests.
Thanks! The best part is that clients don’t need to store the api_key locally, which keeps it secure. I’ve already integrated this service into jumble.social using this approach, it works seamlessly!
↑