Connect your AI app to MnemonX and give users persistent, structured memory across all their tools — with their explicit consent and full revoke control.
Four steps from registration to production
Fill out the registration form with your app details and redirect URIs. Registration is instant; approval takes 1–2 business days.
After approval you receive your client_id and client_secret by email. Keep your secret safe — it is shown once.
Redirect users to /authorize, exchange the code for a token at /api/oauth/token, then call /api/v1/memory.
Your users can now grant your app access to their MnemonX wallet context from their wallet settings.
Request only the scopes you need. Users see exactly what you’re asking for.
memory.readRead all domains in the user's walletmemory.writeWrite to any domain in the user's walletmemory.searchSearch across the user's wallet contentmemory.read:workRead only the Work domainmemory.read:personalRead only the Personal domainmemory.write:workWrite only to the Work domainDomain-scoped variants also available: memory.read:health, memory.write:finance, etc.
Get notified in real-time when users interact with your integration. All payloads are signed with HMAC-SHA256.
user.revokeFired when a user disconnects your app
memory.updateFired when your app writes to the user's wallet
Verify signature in your receiver:
const sig = req.headers['x-mnemonx-sig-256'] const expected = 'sha256=' + hmacSha256(secret, body) if (sig !== expected) return 401
Base URL: https://mnemonx.ai
| Method | Endpoint | Description |
|---|---|---|
| GET | /authorize | OAuth consent page — redirect users here |
| POST | /api/oauth/token | Exchange auth code for access + refresh tokens |
| GET | /api/v1/memory | Read user memory (requires memory.read) |
| POST | /api/v1/memory | Write to user memory (requires memory.write) |
| DELETE | /api/oauth/revoke | Revoke a token (user disconnects your app) |
| GET | /api/webhooks | List your webhook endpoints |
| POST | /api/webhooks | Register a webhook endpoint |
| DELETE | /api/webhooks?id=… | Remove a webhook endpoint |
us-east-1 (Virginia)
Serves: US, Canada, default
eu-central-1 (Frankfurt)
Serves: EU, EEA, UK, Gulf
Every API response includes a X-MNX-Region header indicating which regional database served the request. You can use this to verify that your users' data is being served from the expected region.
HTTP/2 200 X-MNX-Region: eu X-MNX-User-Id: usr_xxxxxxxx Content-Type: application/json
When your application accesses user wallet data via the MnemonX API, MnemonX acts as a data processor on your behalf. The wallet data you access is: (a) encrypted at rest, decrypted only to serve this specific authorized request — never read or retained by MnemonX otherwise; (b) served from the user's assigned region; (c) access-logged for 90 days for the user's GDPR export. Your application is the data controller for how you use retrieved data. See our DPA and Privacy Policy.
EU wallet data stays in eu-central-1. SCCs cover US billing transfers.
UK users assigned to EU region. UK IDTA covers residual US transfers.
MnemonX does not sell API data. You are a Service Provider under CCPA.
User data is AES-256-GCM encrypted on-device before reaching our servers. Server-side decryption is limited to specific, authorized code paths tied to the user's own request — never general access to plaintext.
Users see a granular consent screen before granting your app access. Nothing runs automatically.
Users can disconnect any app instantly from their wallet settings. Your token is invalidated server-side immediately.
Request only the domains you need (e.g. memory.read:work). Users grant the minimum necessary access.
Every webhook payload is signed with your endpoint secret. Verify before processing.
Every API call is logged to api_access_logs. Users can request their full access log via GDPR export.
Register your application and get your OAuth credentials. Questions? Reach us at [email protected]
Register your application