Routstr also supports the x-cashu (NUT-24) header protocol .. u don't need to have any balance by ur provider, basically u pay per request .. u will need to have a client that can extract the model cost per request and can generate a cashu token .. https://otrta.routstr.com/documentation/overview
Other projects are following
Yeah that would work, but is it an issue to let the relay do that by itself .. With contexvm, we need probably a second service that is somehow connected to the relay to apply the changes .. nostr:nprofile1qqsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5gpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqg4waehxw309ahx7um5wfjkc6t5v4ejummjvuq3xamnwvaz7tmhda6zumn0wd68ytnwv46qfje5wx correct me if I'm wrong
nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99urf278z nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhkummnw3ezummcw3ezuer9wchswkufa8 nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhscs6htm any though on using nostr events to store relay configuration, like white listed npubs, etc.. , relays could fetch the event and apply on the fly without a restart..
It could also be a public event so anyone can copy..
Thought myself of having a relay daschboard to update settings and probably use it for other things..
(Or do u know about anything like this?)
take charge with Wally: a sleek, next-generation wallet that centralizes your finances and even monitors your LLM usage and setup a badget, made by nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhscs6htm nostr:nprofile1qqsq6myr3rwtqjdcm48u357ccwae8h3a4y96s28y7zwg458ngeyg5vcpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzyrhwden5te0xy6rqtnxxaazu6t0qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hs4808mz . Its plugin architecture lets you tailor the experience to fit exactly what u need .
#SovEng
#Otrta configure ur nwc connection and topup ur balance.. imagine the topup runs automatically 🔥 (For now, top-ups need to be done manually.)
https://blossom.primal.net/b1ca3aa94fda59d570c7b37ccc06128547cae9ed27b828855d6c11f7cd1674cf.mov
#Routstr configure ur routstr proxy nostr:nprofile1qqsgha3fk023ng8c4quszdayghqwkt6l9d9ga4c3280gnqz3aqqx7ycppemhxue69uhkummn9ekx7mp03gnq5z
https://blossom.primal.net/31fbd817b3c6df085effccaa5df83bc024ef37115be89ff993278ac535ae7eaa.mov
What if the event is send to all configured relays and the first one who redeems it gets it, so its like mining the event bit still all have to keep it .. So relays could compete 😸
otrta 0.1.2
We're thrilled to announce some powerful new features that enhance your AI experience:
* Nostr Marketplace Discovery: Easily discover providers with NIP-91 support!
* Model Comparison: Find the best model prices with our new comparison view!
Future Plans:
We're already working on more innovations, including:
* Automatic provider switching for the best model prices!
* setup api key budget limit
Stay tuned for more updates!
Users are not required to have account/balance by their provider they could switch provider instantly without asking for refund..
when user sends a request an ecash token is created and added to the request, providers forward the request to an ai provider (like openai) get paid with the token provided and return change (if any) .. Basically the user has always a new identity
Hey, are u still having issues, currently the live otrta is up and running .. Not sure but could it be u logged in with different npubs ?
PN if the issue persisted
It's 'one to rule the all', we still look for a cool pronunciation 😅
U could use zed with routstr client already .. all u need is to setup the provider, basically ucould do that here: https://otrta.routstr.com
Checkout the dashboard when u login u will find the URL u need (create the api key, select ur provider, topup ecash to the provder mint and ur good to go)
Did some work and summarized all in this project..
from Project for a friend to otrta routstr client the Privacy-First AI Access!
We're thrilled to announce **otrta** - the revolutionary Routstr client that brings you completely anonymous AI access powered by cutting-edge e-cash technology! 🚀 With private micropayments using Cashu e-cash notes that let you pay for exactly what you consume down to the millisatoshi. Whether you're a solo developer or managing a larger team, otrta seamlessly integrates with your favorite AI coding tools like goose, Cline, Roo Code, and Kilo Code - just update your API endpoint and you're ready to go!
**Complete Control & Privacy**: Built for ultimate privacy and autonomy, otrta is fully **self-hostable** - deploy your own instance and maintain complete control over your data and infrastructure. Connect to AI providers through both **standard URLs and Tor hidden services** for maximum anonymity and censorship resistance. Built on the decentralized Routstr protocol with Nostr authentication, you get complete privacy, flexible deployment options.
Join the privacy-first AI revolution and experience what truly permissionless AI access feels like - no KYC, no credit cards, just pure innovation at your fingertips! ⚡
📋 **Check our release notes** → [Release 0.1.0](https://github.com/Routstr/otrta-client/releases)
📚 **Explore comprehensive docs** → [Documentation](https://otrta.routstr.com/documentation/overview)
🚀 **Start your journey now** → [Login & Join the Revolution](https://otrta.routstr.com/)
## 🙏 Special Thanks
nostr:nprofile1qqst8c37ku3hkdj6e2vun550qu9rzntp4qm700g0ewc0qw2dmnakyxqpzemhxue69uhk7unpdenk2umede3juar9vd5z7qgkwaehxw309ash2arg9ehx7um5wgcjucm0d5hsd90e3k - Our relentless testing champion who battled through countless iterations, found every edge case, and pushed the boundaries until we achieved bulletproof reliability.
nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk - The e-cash wizard whose expertise shaped the core of our payment infrastructure.
#routstr #ai
We are planning to release this week .. pre-release https://otrta.routstr.com
hey nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqydhwumn8ghj7mn0wd68ytnzd96xxmmfdecxcetzwvhxgegqyz9lv2dn65v6p79g8yqn0fz9cr4j7hetf28dwy23m6ycq50gqph3xc9yvfs, How can i find out which mint(s) a routstr provider accepts?
I looked into the docs but the closest thing i can find is how to configure the mint as a provider. Not how to see it as a user.
I don't see it mentioned in the protocol docs either (looking at RIP-02, https://github.com/Routstr/protocol/blob/main/RIP-02.md)
My use-case:
I want to use routstr in Receipt.Cash (https://next.receipt.cash)
I have sats available in a mint (which i cannot predict which one it's gonna be).
So i need a way to use the balance of whatever mint's proofs i happen to have available.
In short: Discovery by mint
hey Arjen, thanks for reaching out .. That part of the documentation is still missing but we are currently working on the specification.. the current implementation of routstr does accept ecash from any mint so probably there would be no issue with using any mint proofs u have ..
reach out if u face any issues
Sure, I mean to make sure ur server is reachable u could do this simple test
curl -X GET https://embeekttrsdquyyicngh5i6xc6xkqymm6cihgzngtbxpoevd6ut5pead.onion/v1/models
That should return the list of all models in ur models.json file
u could also get the the server logs. First navigate to the folderwhere ur docker compose file is located and run the followingcommand
$ docker compose logs
Nice !!
One think to make sure ur server can be reached, try to collect ur models.
a GET request to this endpoint '/v1/models'
Yeah I'm currently cleaning up and improving some stuff, but basically the code is about the client that the user runs locally and hook up to any ai driven software that use the openai api protocol (like. Goose, roocode, cline, etc.).
will soon release the client with more docs and features..
Ppq or other provider should only implement the interface based on the provider-cliemt spec which as u mentioned still not well documented yet (working on it 😉)
I joined routstr team recently.
Did myself worked on such solution
https://github.com/9qeklajc/ecash-402-client
Where u pay ecash per request.
This method ist for sure as u mentioned it, not perfekt, but its a decision the provider make and risk loses ..
Wrote also some ideas on the topic, about a smart client and dynamic provider.
https://github.com/ecash-402/ecash-402-specs
Feedback is welcome
Not realy familiar with openrouter but, have you tried litellm ? Would you recommend it ?
To prototype and to see if ideas make sense then yeah vibe coding is awesome, but fortunately the currently available tools and llms generate a lot of noise after multiple iterations (e.g unused code, inconsistent style, etc..) and that makes it more harder to maintain and for others to contribute
the api could be easily tested via curl
curl -i -X POST https://ecash.otrta.io/v1/chat/completions \
-H "X-PAYMENT-SATS:
-H "Content-Type: application/json" \
-d '{ "model": "meta-llama/llama-4-maverick-17b-128e-instruct-fp8", "messages": [{"role": "user", "content": "Tell me the difference between ecash and regular money."}] }'
The response includes a new header field (X-CHANGE-SATS) that provides an eCash token with change.
x-change-sats:
30 SATs per request are minimum
the api could be easily tested via curl
curl -i -X POST https://ecash.otrta.io/v1/chat/completions \
-H "X-PAYMENT-SATS:
-H "Content-Type: application/json" \
-d '{ "model": "meta-llama/llama-4-maverick-17b-128e-instruct-fp8", "messages": [{"role": "user", "content": "Tell me the difference between ecash and regular money."}] }'
The response includes a new header field (X-CHANGE-SATS) that provides an eCash token with change.
x-change-sats:
That would be the easy part (I think), when I setup my own mint ..
Saw it but didn't really have the knowledge and capacity to setup all those technologies together ..
Was really happy when I found nutshell to use via API (currently the API ist not supported anymore 🙈) so an older version is used!
There still a lot to do ..
Project for a friend 😁
Excited to announce the ECASH OpenAI API client! There's still a lot to be done, contributions are welcome 🙏