Have not tried yet, but did see in the readme it supports x402 protocol for payments, that’s nice.
1) double checking whether it actually does, does it?
2) Which chains are supported, and how’s the x402 being handled - your service self hosted or third party?
Seems too good to be true, open-source, supports many free tools, the only part that I'm concerned about is how long will the website be up, because I bet some of those providers are not gonna appreciate it
I saw you post about Treg positioning it as Clay-alternative and also as OpenRouter for agent tools. Personally, I resonate better with Clay positioning because most use cases I can think of would come down to data enrichment and such. Something to consider. Otherwise, great product!
Useful abstraction layer for rapid prototypes, but you cannot hide upstream latency and upstream rate limits behind a single endpoint.
I am self hosting treg for development. You can setup and run treg with one click on tarvis.io
Have not tried yet, but did see in the readme it supports x402 protocol for payments, that’s nice.
1) double checking whether it actually does, does it? 2) Which chains are supported, and how’s the x402 being handled - your service self hosted or third party?
Seems too good to be true, open-source, supports many free tools, the only part that I'm concerned about is how long will the website be up, because I bet some of those providers are not gonna appreciate it
Got the same feeling but still, wanted to try
Until I went to their website, which is absolutely not like OpenRouter.
Heavy, full of useless stuff.
It’s cool, but none of the T&Cs of those providers legally allow for this. There’s a market for that, but heads up.
Can you explain more as to why T&C don’t allow for this.
I varies a lot depending on the vendor. Usually its against the terms if you're reselling rather than making calls on someone else' behalf.
My company is doing something similar but being a bit more careful about the providers we work with.
I'm using self hosted mcp-jungle for this.
Treg is really cool. It's a set of stateless APIs to get access to data sources with one single subscription.
This is one half of the coin for GTM automation.
The other half requires state: webhooks, signals, schedules. Here, a tools like pipe0 or clay still have the edge.
[dead]
[dead]
I saw you post about Treg positioning it as Clay-alternative and also as OpenRouter for agent tools. Personally, I resonate better with Clay positioning because most use cases I can think of would come down to data enrichment and such. Something to consider. Otherwise, great product!
Also, checkout https://gitwal.com/superdesigndev/treg That's every social media mention of your product.