Memory sharing check
wever_memory-sharing-checkAgent Memory: submit a memory-sharing flow: whose memory it is and each way stored memory can cross (the categories that cross, who receives it and whether that is another agent, a tool, another principal, an operator or an external system, under whose instruction: the principal each time, a standing rule the principal set, an operator, the agent on its own or no one, whether it is logged in full, in part or not at all, whether only the memory the instruction names crosses and whether the recipient may keep it), plus optionally the crossings seen with under whose instruction each happened and whether it is in the log. The signed report says crossing by crossing what stored memory crosses to another agent, tool or principal, under whose instruction and whether it is logged, and names every crossing no one instructed, every crossing the agent decides on its own, every crossing carrying memory to another principal without the first principal’s word, every unlogged crossing, every crossing that hands over the whole store and, among the crossings seen, every path nobody declared, every crossing nobody instructed and every crossing missing from the log, then every partial log, every crossing on an operator’s word in place of the principal’s and every recipient that keeps the memory, with the fix for each. This reads deliberate sharing of stored memory: context handed over inside a live session, and whether one sharing event needs consent, is wever_context-sharing-check, whether memory stores stay apart by default is wever_memory-separation-check and what a handoff format carries is wever_context-transfer-check. Verdict memory_wanders, sharing_gaps, sharing_unverified or sharing_instructed. POST /api/memory-sharing-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-memory-contract. Human page: https://weverlabs.com/agent-memory/.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "wever_memory-sharing-check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| flow | No | The memory-sharing flow, such as handoffs to the booking agent. | |
| label | No | Optional name recorded in the report. | |
| events | No | Crossings seen, to find any nobody instructed or logged. | |
| crossings | No | Each way stored memory can cross to another agent, tool or principal. | |
| principal | No | Whose memory it is, such as the traveler. |