# Datagran Memory and data integrations in Groovy

Groovy can use Datagran as an optional semantic Memory source and for Datagran-backed data integrations. These are separate from Groovy's private structured Wiki. When Datagran is not configured, do not claim semantic `remember`/`recall` or Datagran-backed source access is available.

Developer/enterprise setup uses `DATAGRAN_API_KEY` and `DATAGRAN_CHAT_MODEL` when these capabilities are enabled. An ordinary user should use the approved product setup flow; do not request a reusable key in chat or put one in a URL or documentation. The entitled source checkout's `docs/ai-agent-setup.md` describes CLI checks.

`GET /api/memory/config` requires the current Groovy user session and reports whether a Datagran Memory connection is **saved**. It does not test live model inference, recall quality, source freshness, or access to another user's connection. `POST /api/memory/config` accepts a Datagran key and creates/retrieves a connection; treat it as a credential-changing setup action needing the user's authorization. Neither operation is covered by the public external-key OpenAPI contract.

Supported source types and their setup methods vary. A source connection must be granted to the intended Mind or agent; a saved provider label alone does not authorize a tool. Provider OAuth and account selection remain user-controlled. Check the exact source's status and a safe read before declaring it ready. Groovy's `POST /api/memory/trace` records a trace on a best-effort basis and is not a general trace-query or observability API.