Docs Memory API

When something looks wrong

Most surprises come from one of five causes. Check them in this order.

#1. The job hasn’t completed

Recall only reflects completed jobs. Check GET /v1/jobs/{jobId}; a failed state includes the reason.

#2. The viewer can’t see it

Recall the same query with an identity you know is in the audience. If that works, the original viewer isn’t a member, or the record is private to its author.

#3. It was superseded

The fact you expected may be in history because a newer record changed it. Check the newer source — it may be a correction you didn’t intend.

#4. The timestamp is wrong

A record sent without occurredAt gets the time it was received, so an old email imported today looks newest. Re-send it with its real time.

#5. It didn’t fit the budget

If truncated is true, raise maxTokens or make the query more specific.

#Inspecting a memory

List memories from one record

curl "$AULD_API_BASE/v1/memories?sourceId=crm-4471&includeHistory=true" \
  -H "Authorization: Bearer $AULD_API_KEY"

Every response includes a requestId; usage records in GET /v1/usage show credits consumed per call.

Illustrative interface example · replace the host and key placeholders