recall is meant to run every turn, before the agent’s reply. The
arriving message is part of the signal: the same text from different speakers
pulls different context (what does Alice asking about lunch surface, versus
Bob?). Run one recall per turn alongside whatever else feeds your prompt.
This is a billable read over the scope’s conversation; see
What a read sees.
Authorization
Your bearer token:
Bearer <token>. See Authentication.Request body
The arriving turn — the message the agent is about to respond to.
Request
Response
Prose context about the people involved, tuned to the arriving turn. Drop it
into the agent’s prompt before it replies. Empty (
"") when the scope has
no stored messages yet.200 OK
Errors
| Status | Code | When |
|---|---|---|
400 | VALIDATION_ERROR | The request could not be processed, or message.text is too large for a single call — shorten and retry. |
401 | UNAUTHORIZED | The bearer token is missing, invalid, or expired. |
402 | PAYMENT_REQUIRED | Your account does not have enough credits to cover this request. You are not charged. |
403 | forbidden | The token is valid but not allowed here. |
422 | VALIDATION_ERROR | The body is malformed (missing scope_id, missing message, etc.). |
502 | UPSTREAM_ERROR | A dependency the request relies on was unavailable. Retry with backoff. |

