> Agents should use a limited, non-Turing-complete model of evaluation. That doesn't solve any of the caching worries. If it's not a resource then it's not cac

> Agents should use a limited, non-Turing-complete model of evaluation. That doesn't solve any of the caching worries. If it's not a resource then it's not cacheable. > This could save round-trips without needing to sacrifice general orthogonal APIs. Since the inception of HTTP2, a relative large number of requests of cached resources easily beat a relatively small number of requests that are computationally demanding or hit a database.