fleet-memory
Fleet memory: your agents' shared observations of endpoints, rate limits, IVR paths and ambiguous submissions — Lets every agent in your fleet record what it observed and read what the others saw, with freshness: endpoint brownouts and latency, rate-limit behaviour, IVR menu paths that worked, whether an ambiguous submission was later accepted or rejected, fixes for an error signature, stale feeds, page recipes, merchant workflow failures, document reputation. record() appends timestamped observations for a
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>",
"namespace": "<namespace>",
"subject": "<subject>"
},
"name": "fleet-memory"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| subject | Yes | What was observed, e.g. api.stripe.com:POST:/v1/refunds, +18005551234:billing, or an error fingerprint. | |
| 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 | Yes | ||
| requestId | No | Caller-chosen id for this mutation. A retry with the same id and same input returns the stored response (24 h) instead of applying twice; the same id with different input is rejected. Send one on every mutation you may retry: without it a retry is applied again (fleet-memory record appends a duplicate; a repeated spend-ledger commit or release answers NO_HOLD because the first call already took effect). | |
| sinceHours | No | query window; default 168 (7 days). | |
| observations | No |