Those are useful, but "open-sourceness" is not a relevant trait. I plan to publish another short post covering the tech stack, commercial and open, which will include such payment-related packages.
I went to syria instantly after Tha fall of the regime and building there now. Relying on opensource is a culture here. Am really interested in learning from u and really looking 4 payment solutions to replicate here and custmiz to solve local problems
APIs will always be the preferred method given that they are structured and scoped. The post covers websites and apps that don't expose a direct API, which is a less rigid alternative to an API.
Good post, but you're missing https://github.com/dagworks-inc/burr ;) It is not only an open source framework that you can pair with things like langchain & haystack (see https://blog.dagworks.io/), it also comes with integrated observability that you can self-host.
So it's a complete framework + observability solution.
I would love to see the addition of open source ui driven agent builders to this list. Flowise and Langflow come to mind as two of the top ones in this space built on top of langchain
How about build everything you truly need in your agent architectures from scratch? Making so many dependencies can be counter productive on the long run.
Great AI products don’t feel like AI—they feel like magic that *just works*. That happens when technology disappears behind seamless value, not when it demands attention for being ‘smart.’
This was unbelievably helpful and well timed, thank you!
When are we adding payments as a category? :)
(stripe SDK, Coinbase SDK, Circle SDK, OpenCommerce SDK)
Those are useful, but "open-sourceness" is not a relevant trait. I plan to publish another short post covering the tech stack, commercial and open, which will include such payment-related packages.
I went to syria instantly after Tha fall of the regime and building there now. Relying on opensource is a culture here. Am really interested in learning from u and really looking 4 payment solutions to replicate here and custmiz to solve local problems
What about interacting with a website or app through it's API? And how do you define, constrain and focus on the function of the system?
APIs will always be the preferred method given that they are structured and scoped. The post covers websites and apps that don't expose a direct API, which is a less rigid alternative to an API.
Anthropic answered that question a couple of weeks ago with the release of Model Context Protocol (MCP)
https://modelcontextprotocol.io/introduction
A worthy read for seasoned and beginners. Appreciate the time and effort it took you to publish.
Thanks for making this!
Very useful, thanks for sharing !
Good post, but you're missing https://github.com/dagworks-inc/burr ;) It is not only an open source framework that you can pair with things like langchain & haystack (see https://blog.dagworks.io/), it also comes with integrated observability that you can self-host.
So it's a complete framework + observability solution.
I would love to see the addition of open source ui driven agent builders to this list. Flowise and Langflow come to mind as two of the top ones in this space built on top of langchain
Did you write this with Claude? It always gives me ‘looking ahead’ as a last subheading as well😊
i bet the author don't even use half of them himself
Great discussion post
Hi great post! Also follow dr_scientis for some data science tips too that really helps to level up your game!
I need this
What are ai agents actually?
🙌
How about build everything you truly need in your agent architectures from scratch? Making so many dependencies can be counter productive on the long run.
Great AI products don’t feel like AI—they feel like magic that *just works*. That happens when technology disappears behind seamless value, not when it demands attention for being ‘smart.’