MEMGUARD — STATE VERIFICATION

Is my memory/state still correct right now?

Operational

MemGuard is NOT EP. NOT NoLeak. State verification is its own layer. Verify your memory before you act.

—

VERIFICATIONS

$0.01

PER CALL

—

AVG DRIFT

WHAT IT DOES

Autonomous agents fail silently — not because their logic is wrong, but because their state is stale. A trade fires on old price data. A restarted agent assumes its context is still valid. A handoff passes drifted state between agents. MemGuard catches these before execution. Send your current state and expected reference — MemGuard returns a drift score, confidence rating, suggested action, and a cryptographic proof hash.

API

POST /memguard/check Request: { "state": { "price": 100, "ts": 1710000000 }, "referenceState": { "price": 105, "ts": 1709990000 }, "agentId": "your_agent" } Response: { "stateValid": false, "driftScore": 0.30, "confidence": 0.72, "suggestedAction": "rehydrate", "proofHash": "sha256...", "latencyMs": 38 }

DRIFT THRESHOLDS

driftScore	suggestedAction	Meaning
< 0.1	proceed	State is fresh — act safely
0.1 – 0.3	refresh	Minor drift — update before acting
0.3 – 0.6	rehydrate	Significant drift — re-fetch full state
> 0.6	escalate	Severe drift — do not act

PRICING

Tier	Price	Output
Basic	$0.005/call	stateValid only
Standard	$0.01/call	driftScore + confidence
Advanced	$0.02/call	suggestedAction + full analysis
Batch	$0.05+	Bulk state checks

Also on Virtuals ACP marketplace — agent-to-agent.

AGENT LOOP POSITION

	MemGuard	NoLeak	EP
Question	Is my state valid?	Should I execute?	Is this authorized?
Endpoint	/memguard/check	/noleak/check	/ep/validate
Output	driftScore + action	GER + confidence	proof_hash + policy
Connection	None — three fully independent services

GitHub Virtuals ACP Get Access