Discover / mem0-cloud.saastemly.com

mem0-cloud.saastemly.com

■ Challenge detected

Delete your stored memories, like mem0's delete memory and delete all memories. With memory_id: deletes that one memory (404 if it is not yours). Without it: deletes up to 200 of your memories matching user_id, agent_id, app_id or run_id (at least one), and says if more remain. Requires your memory_key (a secret string you generate): other keys cannot delete your memories.

x402
Base
USDC

Challenge detected: 1 of the last check
Median response: 279 ms
Last checked: 3 Oct, 17:05 UTC
In our index since: 3 Oct 2026

Endpoint

curl -i https://mem0-cloud.saastemly.com/v1/memories
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/mem0-cloud.saastemly.com

Recent checks

3 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.3 Oct 2026

All 1 checks

When (UTC)	Result	HTTP	Response
3 Oct, 17:05 UTC	Challenge detected	402	279ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 3 Oct, 17:05 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does mem0-cloud.saastemly.com advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is mem0-cloud.saastemly.com listed?

In x402 Bazaar. Superstables first indexed it on 3 Oct 2026.

Something wrong on this page? Tell us.