lore retrievalPOST /api/memory/retrieve · x402 API by lore-prod
lore retrieval
What does this x402 API do?
lore retrieval. This is an x402-gated POST API resource from lore-prod. TOLL·402 did not invoke this route automatically because doing so was not considered safe. The listing records $0.05 USD-denominated per request on Base Sepolia. No settled paid call has been verified.
- Published price
- $0.05 USD-denominated per request
- Networks
- Base Sepolia
- Latest evidence
- TOLL·402 did not invoke this route automatically because doing so was not considered safe
- Resource ID
- b5cd496cc3152131370d4ec4
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://lore-prod.vercel.app/api/memory/retrieve", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://lore-prod.vercel.app/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is $0.05 USD-denominated per request. Raw protocol requirements remain visible below for implementation and audit use.