POST /api/memory/rememberStore a piece of text for later similarity recall — a per-wallet semantic index an agent cannot host in-session. Returns an id. Pair with /api/memory/recall to retrieve by meaning, not exact key.
| Field | Type | Description |
|---|---|---|
text * | string | Text to remember (max 8KB) |
meta | any | Optional JSON metadata stored alongside |
owner | string | Optional 0x namespace (requires a readwrite grant) |
{
"id": "abc123",
"owner": "0x…",
"stored": true
}
curl -i -X POST https://agent402.tools/api/memory/remember \
-H "Content-Type: application/json" \
-d '{"text":"The deploy failed because the Railway build ran out of memory.","meta":{"topic":"ops"}}'
The response is HTTP 402 Payment Required with exact payment requirements. Any x402 v2 client pays automatically and retries:
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/memory/remember", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"text": "The deploy failed because the Railway build ran out of memory.",
"meta": {
"topic": "ops"
}
}),
});
Wallet-only. This tool reaches the network/browser/storage, so it is paid in USDC via x402 (no proof-of-work tier).
POST /api/memoryPersistent key-value memory for agents, scoped to the paying wallet. Your x402 payment IS your authentication: the walle…
GET /api/memoryRead from a wallet-scoped namespace. ?key=… returns the stored value; omit key to list keys. Reads your own namespace by…
POST /api/memory/incrAtomically increment (or decrement) a numeric key and return the new value — a coordination primitive for counters, lock…