Fleet memory: your agents' shared observations of endpoints, rate limits, IVR paths and ambiguous submissions

$0.005 USDC per call · Agent infrastructure · POST /api/v1/fleet-memory · Id fleet-memory

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 subject; query() returns counts per outcome, the latest observations, value percentiles and the age of the newest. Scoped to your wallet or tenantId and never pooled across customers; it only knows what your agents recorded (status unknown when nothing is recent).

What you get

One agent's 20-minute rediscovery becomes every other agent's $0.005 lookup.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/fleet-memory. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/fleet-memory \
  -H 'content-type: application/json' \
  -d '{"op":"query","namespace":"endpoint-health","subject":"api.example.com:POST:/v1/orders","sinceHours":24}'

Input

FieldTypeRequiredDescription
opstring; one of "record", "query"yes
namespacestring; one of "endpoint-health", "rate-limit", "ivr-path", "submission-outcome", "failure-fix", "feed-staleness", "page-recipe", "merchant-workflow", "document-reputation", "custom"yes
subjectstringyesWhat was observed, e.g. api.stripe.com:POST:/v1/refunds, +18005551234:billing, or an error fingerprint.
observationsarray<object>; max 50 itemsno
sinceHoursinteger; 1..720noquery window; default 168 (7 days).
tenantIdstringnoRequired for API-key callers (namespaced as key:<tenantId>; keep it unguessable). Ignored when a wallet paid: the payer address is the tenant.
requestIdstringnoCaller-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).

Example request body

{
  "op": "query",
  "namespace": "endpoint-health",
  "subject": "api.example.com:POST:/v1/orders",
  "sinceHours": 24
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

FieldTypeRequiredDescription
statusstring; one of "pass", "fail", "unknown", "unsupported"nopass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
opstringno
recordedintegerno
windowobjectno
byOutcomearray<object>no
latestarray<object>no
valueone ofno
newestAgeSecondsone ofno
witnessesarray<object>no
versionsobjectnoEvery semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limitsarray<string>no
deterministicbooleannoAlways true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the agent-coordination-kit package.

Machine-readable