Get research
Read a research run: its status, its last stage, and its answer or error.
/namespaces/{namespace}/collections/{collection}/research/{research}PermissionThe key that started the run, or a cluster key. Key scopes and actions.
- progress is the last stage of the run. When the run succeeds, answer, sources, image_description, and usage are set. When it fails, error is set, with retryable.
- Another key gets 404, as for a run that does not exist.
Path parameters
Namespace name or ns_ ID. It must be visible to this key.
Collection name or col_ ID within the namespace. It must be visible to this key.
Research run ID with the rsr_ prefix, returned by Create research.
Responses
200Success
A run that succeeded, with its answer and its sources.
application/json
Response headers
The Engine request ID. Retain it when investigating a failed or unexpected request.
The X-Request-Id you sent, echoed when it is a valid ID. Otherwise, the Engine request ID.
Answer text, once the run succeeds. A citation marker such as [[SRC:0001]] names the source whose ref is SRC:0001. The answer has no markers when the request set sources to none. Otherwise null.
Name of the collection that the run answers from.
Time the run ended, as an ISO 8601 UTC timestamp. Null while it runs.
Time the resource was created, as an ISO 8601 UTC timestamp.
Why the run failed, with retryable. Null unless the run failed.
Immutable research run ID with the rsr_ prefix. Use it to read or cancel the run.
How Engine read the query image, once the run succeeds. Null without an image.
Name of the namespace of the collection.
The last stage of the run, or null before the first one.
The sources in ref order, once the run succeeds: the cited sources first, then the others by score. Empty when the request set sources to none. Otherwise null.
queued, running, succeeded, failed, or canceled. succeeded, failed, and canceled are terminal states.
- queued
- Accepted and waiting to start.
- running
- Engine is working on the answer.
- succeeded
- The answer is ready.
- failed
- The run ended with an error.
- canceled
- The run ended after cancellation.
Time the resource last changed, as an ISO 8601 UTC timestamp.
What the run used, once it succeeds. Otherwise null.
Errors
Select an error in the response example to see its JSON body. See error handling for the common error format.
- 400invalid_request
A field, path, parameter, or conditional request rule is invalid.
What to do: Correct the request. Unknown fields are rejected.
- 401unauthenticated
The API key is missing, invalid, or revoked.
What to do: Send an active key in Authorization: Bearer or X-API-Key.
- 403forbidden
The key can see the resource but lacks permission for this operation.
What to do: Use a key with the required action or scope kind.
- 404not_found
The resource is absent, deleted, or outside this key’s scope.
What to do: Check the identifier and the key’s namespace and collection scope.
- 500internal_error
An unexpected server failure prevented this request from completing.
What to do: Retain request_id for investigation. Follow retryable before retrying a write.