To say that you're building agents, is based on a way of viewing things that isn't at all pervasive. Some might say you're building a customer support chatbot. To talk of building agents as a common activity makes sense if you use LangChain I guess, where its title is "Open Source AI Agent Framework | Build Agents Faster". But for instance, YC just released qm, and in its README it talks about customizing the agent, which is quite a bit different from just casually dropping the phrase "I'm building an agent". https://github.com/yc-software/qm
Not sure what you are trying to say but thanks for reminding me about qm, it has some cool features.
My MindRoot framework had some of qm's main features awhile ago though. I do try to use it to build solutions by customizing rather than from scratch when possible. But a lot of clients or potential clients don't like that idea even though it's MIT. They want some that has clearly been invented by them as a new programming project.
I actually turned down a project last year from someone who wanted me to start over in LangGraph -- he had already decided on it before he knew about my thing.
The most recent project I have been using MindRoot and building up the voice capabilities so I can now handle voice agents end to end including SIP.
But on that website now I try not to emphasize my framework at all for most proposals. You don't have leverage on Upwork. And also with code generation it isn't a critical point necessarily.
Why are you looking for projects on upwork if you know they don’t pay well and that you don’t have leverage? That sounds like a pretty bad place where to find contracting projects