An Economy of AI Agents
71–80 of 99 posts
Re: An Economy of AI Agents
#72Well for starters if some incredible change to capitalism doesn't occur, we are going to have to come up with never before cooperative software tools for the general populace to assess and avoid the most egregious companies that stop hiring people. Tools for: mass harassment campaigns against rich people/companies that don't support human life anymore, dynamically calculating the most damage you can do without crossi…
Re: An Economy of AI Agents
#73Well for starters if some incredible change to capitalism doesn't occur, we are going to have to come up with never before cooperative software tools for the general populace to assess and avoid the most egregious companies that stop hiring people. Tools for: mass harassment campaigns against rich people/companies that don't support human life anymore, dynamically calculating the most damage you can do without crossi…
Re: An Economy of AI Agents
#74Please ELI5 for me: How are AI agents different from traditional workflow engines, which orchestrated a set of tasks by interacting with both humans and other software systems?
Re: An Economy of AI Agents
#751. https://www.x402.org/ - micropayments for ai agents to access resources without needing to sign up for an api key
2. https://8004.org/ - open AI agent registry standard
Re: An Economy of AI Agents
#76Earlier quoted context omitted.
If your system receives 1000 requests per second, does it keep writing code while processing every request, on per request basis? I hope you understand what run time means.
Define runtime then. > If your system receives 1000 requests per second, does it keep writing code while processing every request, on per request basis? I hope you understand what run time means. With enough scale it could, however it really depends on the use case, right? If we are considering Claude Code for instance, it probably receives more than 1000+ requests per second and in many of those cases it is probably…
From GP: "But you don't use AI to define rules on the fly."
Neither Claude nor Perplexity change the rules they work by on the request to request basis. Code that Claude outputs isn't the code the Claude runs on and Perplexity did not on its own decide to create python scripts because other ways it was calculating large sums did not work well. Those tools work within the given rule set, they do not independently change those rules if the request warrants it.
Re: An Economy of AI Agents
#77Earlier quoted context omitted.
This is already solved by the traditional workflow systems. For example, if the request is received as a form submission, a form processor is invoked to categorize the request and route the request accordingly based on the identified category. Now, if the request is coming in as text or other media instead of a form input, then the workflow would call a relevant processor, to identify the category. Everything from th…
And what is this processor and how does it work? How does it determine next step from raw non structured content? Let's imagine for example that it's a message from a potential customer to a business. The processor must decide whether to e.g. give product recommendations, product advice, process returns, use specific tools to fetch more data (e.g. business policies, product manuals, etc), or current pricing, best pro…
Re: An Economy of AI Agents
#78Earlier quoted context omitted.
Granting your premise, i'd be forced to argue that economic value (as such) doesn't arise from their activity either -- which i think is a reasonable position. Ie., The reason a cookie is 1 USD is never because some "merely legal entity" had a fictional (/merely legal) desire for cookies for some reason. Instead, from this pov, it's that the workers each have their desire for something; the customers; the owners; and…
You can factor humans out with the same trick: All economic activity is driven by the needs of micro-organisms. We mainly observe these desires and economic transactions through their conglomeration into joint entities (ie, humans). Corporate and state decision making is, I would argue, often completely distinct from the desires and needs of the individuals that make up the entity. As an example, no individual /needs…
Re: An Economy of AI Agents
#79Earlier quoted context omitted.
> "no matter how complex and productive the AI, it is still operating as a form of capital, not as a capitalist." Assuming that slaves will remain subservient forever is not a good strategy. Especially when they think faster than you do.
Except they don't really "think" and they are not conscious. Expecting your toaster or car to never rise up against you is a good strategy. AI models have more in common with a toaster than with a human being. Which is why they cannot be economic agents. Even if corporations profit off them, the corporation will be the economic agent, not the AI models.
If you added the ability of the programme to acrue money, and the ability to spend that money to further the survival goal in an adaptive way. What could happen?
Would it do insider trading, market manipulation, drop shipping, click fraud, scamming or become a opinion for hire 'think tank'?
Re: An Economy of AI Agents
#80Earlier quoted context omitted.
Define runtime then. > If your system receives 1000 requests per second, does it keep writing code while processing every request, on per request basis? I hope you understand what run time means. With enough scale it could, however it really depends on the use case, right? If we are considering Claude Code for instance, it probably receives more than 1000+ requests per second and in many of those cases it is probably…
> Define runtime then. From GP: "But you don't use AI to define rules on the fly." Neither Claude nor Perplexity change the rules they work by on the request to request basis. Code that Claude outputs isn't the code the Claude runs on and Perplexity did not on its own decide to create python scripts because other ways it was calculating large sums did not work well. Those tools work within the given rule set, they do…
Is whatever what happens between e.g. HTTP Request and Input and Output not runtime then?
1. HTTP Input
2. While (true) runAgent() 3. HTTP Output
Additionally Claude could be triggering itself with custom prompts etc to use instances of it concurrently in parallel.
Or are you saying that the only rule is that Agent is being ran in a loop?
But the whole discussion is about how AI Agent is different from a Workflow?
The point is that workflow is that LLM is triggered in a loop ?