MEM9
Store and retrieve agent memory. Review required fields, credential setup and how this connector works in Zild.
Store and retrieve agent memory.
Where to configure
Open Zild Admin → Integrations → Connectors, find the provider and use Configure or Edit. Enter the data from this guide, enable the connector for the workflow and save.
Required fields
These requirements are the data needed by the workflow using the connector. Generic saving may accept empty fields that are only required when an operation runs. Saving does not confirm that the provider accepts the credential.
| Field | Workflow requirement |
|---|---|
ApiKey | Provider API key. |
How to obtain credentials
- For mem9.ai, provision a space with POST https://api.mem9.ai/v1alpha1/mem9s as described in the official documentation.
- The response contains id; that value is the space key. Copy it into ApiKey.
- For a self-hosted installation, obtain the key from its control plane and confirm the URL with your administrator.
How it works in Zild
The API requires ApiKey and sends it in X-API-Key. Without Url, it uses https://api.mem9.ai and appends /v1alpha2/mem9s. Enable the memory tool on the agent; appId separates memory context.
How to verify the configuration
After saving, use the matching workflow (query, agent, call or processing) to verify access. If it fails, check the credential, permissions and selected provider resource. For limited or legacy types, confirm availability with your administrator before use.
When editing, Zild displays protected credentials as asterisks. Preserve the masked value to keep the current credential or paste a new credential to replace it.