Content-addressed result cache shared by your agents (short TTL)
https://agents.writerslogic.com/api/v1/result-cacheOverview
Caches a result under the SHA-256 of the canonical (JCS) request, so every agent in your fleet that makes the same request reuses one answer for up to an hour. get returns hit with the value and age, or a miss (status unknown). Scoped to your wallet or tenantId, never shared across customers, so nobody else can poison your cache.