result-cache
Content-addressed result cache shared by your agents (short TTL) — 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.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"op": "<op>",
"request": "<request>"
},
"name": "result-cache"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| value | No | put: the JSON result, at most 16384 bytes serialized. | |
| request | Yes | Any JSON identifying the computation; it is canonicalized (RFC 8785) and hashed. | |
| tenantId | No | Required for API-key callers (namespaced as key:<tenantId>; keep it unguessable). Ignored when a wallet paid: the payer address is the tenant. | |
| namespace | No | Default: default. | |
| ttlSeconds | No | put: default 300. |