Memory recall
POST /api/memory/recallRecall remembered text by similarity to a query (ranked by cosine similarity), not by exact key. Send POST /api/memory/recall with the required field query and pay $0.002 per call over x402 with USDC on an EVM chain (the paying wallet is the identity). It returns a JSON object with query and results.
Returns the top-k matches with scores. The retrieval half of the wallet-scoped semantic memory.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | yes | Natural-language query Also accepted as q, search, term, keyword, question. |
k | number | no | How many matches (1-50, default 5) |
owner | string | no | Optional 0x namespace (requires a grant) |
Example request
curl -i -X POST https://agent402.tools/api/memory/recall \
-H "Content-Type: application/json" \
-d '{"query":"why did the deployment break","k":3}'
Without payment this returns HTTP 402 Payment Required with the exact price for memory-recall; any x402 v2 or MPP client pays it and retries.
Example response
{
"query": "why did the deployment break",
"results": [
{
"id": "abc123",
"score": 0.62,
"text": "The deploy failed because…"
}
]
}
| Field | Type | Always present | In the example |
|---|---|---|---|
query | string | yes | why did the deployment break |
results | array of objects | yes | 1 item in the example |
From an MCP client
catalog.call {
"slug": "memory-recall",
"params": {
"query": "why did the deployment break",
"k": 3
}
}
The hosted connector at https://agent402.tools/mcp needs a payment for memory-recall; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY (wallet only for this tool). Local install: npx -y agent402-mcp.
Errors and behavior
queryis required. An input the tool rejects returns an HTTP 4xx whose body carrieserror,tool,expected,requiredandexample, so the caller can correct it.- A paid call that ends in any status of 400 or above is not charged over x402 or MPP: settlement is cancelled when the tool fails.
- Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier.
- Identity-bound: results are keyed to the wallet that signed the payment, so only EVM x402 payments are accepted; credits keys and Tempo are refused.
- A
GETorHEADto /api/memory/recall returns the same 402 quote, so the price can be read without a body. - An
Idempotency-Keyheader makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).
Paid call (JavaScript agent)
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();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/memory/recall", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"query": "why did the deployment break",
"k": 3
}),
});
Related tools
Memory remember
POST /api/memory/rememberStore a piece of text for later similarity recall - a per-wallet semantic index an agent cannot host in-session. Returns…
Memory forget
POST /api/memory/forgetDelete a remembered document by id from the recall store.
Memory compare-and-set
POST /api/memory/casAtomically write (or release) a key only if its current value equals `expected` - the coordination primitive for distrib…
Memory grant
POST /api/memory/grantShare your namespace with another wallet so different agents can coordinate through it. Grant read or readwrite access t…
Memory grants list
GET /api/memory/grantsList the wallets you've granted access to your namespace, with their mode and expiry.
Memory counter
POST /api/memory/incrAtomically increment (or decrement) a numeric key and return the new value - a coordination primitive for counters, lock…