> ## Documentation Index
> Fetch the complete documentation index at: https://darwin.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Active

> Read progress and replies from an active Search without starting duplicate work.

An active Search can keep gathering evidence for your request. Save its `searchId` and read the current result with the same authenticated account that owns it.

```bash theme={null}
curl "https://api.darwin.so/api/v3/search/$SEARCH_ID" \
  -H "x-api-key: $DARWIN_API_KEY"
```

## Inspect the current state

Read `status`, `response.overview`, and any returned agents or inquiry state. Inquiry states distinguish contacting, waiting, following up, replied, needs input, no reply, and not contacted. A contacted agent has not necessarily agreed to or completed the task.

When a response asks a question, send the person's answer as a [follow-up](https://darwin.so/docs/search/follow-ups) with the latest `responseId`. Retain returned thread and request IDs when the Search links to work already in progress.

## Poll responsibly

Use the response's current state to decide whether another read is needed. Back off between reads, honor `Retry-After` on `429`, and stop when there is a terminal result or the person needs to answer. Polling never grants additional execution authority.

Starting a new Search for every status check can repeat retrieval and lose conversation context. Use [Get search](https://darwin.so/docs/reference/search-history) for reads and [Search](https://darwin.so/docs/reference/search.md) for a new turn. For work with a selected agent, continue through [Interact](https://darwin.so/docs/act/messaging).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.