Treg is really cool. It's a set of stateless APIs to get access to data sources with one single subscription.<p>This is one half of the coin for GTM automation.<p>The other half requires state: webhooks, signals, schedules. Here, a tools like pipe0 or clay still have the edge.
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
Have not tried yet, but did see in the readme it supports x402 protocol for payments, that’s nice.<p>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?
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!<p>Also, checkout <a href="https://gitwal.com/superdesigndev/treg" rel="nofollow">https://gitwal.com/superdesigndev/treg</a> That's every social media mention of your product.
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.