Developer / API Access
View plan →API Key Management
Start Trial Cloud, issue a hosted Nexus key, and connect MCP or the API from one place.
Put the issued key into NEXUS_API_KEYfor hosted setup, or use it once for Local Lite activation.
Hosted setup
Use the issued key for MCP clients and direct hosted API requests. Trial Cloud uses the same setup path as paid hosted plans.
Local Lite
Use the issued key once with activate --key to bind a local SQLite license to this device.
Current surface
Hosted memory currently exposes remember, recall, sessions, export/import, and soft delete.
New Key / Generate
Create New Key
Use agent-specific names such as claude-code, cursor, codex, or windsurf so you can trace where the key is being used.
Secondary / Read Only
Create Read-Only Key
Use this only for verification, compliance, and restricted recall checks. Most agent setups should keep using a hosted write key above.
Active Keys
Issued Keys
This page currently issues hosted write keys. Revoke old keys before rotating on single-key plans.
Data Access / Permissions
Agent Data Access
This switch affects what hosted recall can search. It does not change the issued key itself.
Allow agents to access my memory
Current state: Disabled
When enabled, nexus_recallalso searches your notes and imported data. When disabled, only agent memory is searched.
Setup Guide
What this key unlocks
Use the issued key directly for Trial Cloud, Cloud Pro, or Team. Trial Cloud does not require a card. Use Local Lite activation once if you want local SQLite mode on this device.
- 1Issue an API key above.
- 2For hosted mode, use the key directly in generated agent config or in AMCP API requests. For Local Lite, run init --local and then activate --key.
- 3Restart the agent after setup. Hosted mode keeps using the key on requests. Local Lite stores memory in local SQLite and no longer needs the key on every request after activation.