Okay, here’s one I’m working through. When the workload consists of compound elements in multiple domains, agents work best when they see that as a flat surface of detailed resources. Traditional APIs work best when they hide the implementation details behind an ergonomic api.
So service API developers want to abstract and hide, over and over, and this means agents have less and less context and do more guessing.
Okay, here’s one I’m working through. When the workload consists of compound elements in multiple domains, agents work best when they see that as a flat surface of detailed resources. Traditional APIs work best when they hide the implementation details behind an ergonomic api.
So service API developers want to abstract and hide, over and over, and this means agents have less and less context and do more guessing.