# Start an investigation

**POST** `/v1/investigations`

**Operation ID**: `start`
**Summary**: Start an investigation
Triggers an agent investigation with optional free-form context and returns the new investigation id. The investigation is queued and runs asynchronously once the agent has a free concurrency slot. With issueId, a person hands the agent that issue, which becomes the investigation's subject and records the handoff in its history.

## Tags
- Investigations
## Request Body

**Content-Type**: `application/json`

**Schema**: `StartInvestigationRequest`

## Responses

### 202

Investigation queued

- **Content-Type**: `application/json` / `StartInvestigationResponse`
### 400

An invalid continuation, or a handoff that is also a continuation or to an agent with no issue tools (a handoff's refusals carry an issue error body)

### 401

Unauthorized

### 403

No permission to run investigations, or a handoff by anyone but a person, by a person who may not edit the issue, or to an agent that may not view and edit it

### 404

Agent not found, or the handed issue doesn't exist or the caller can't see it

### 409

The agent is paused or the continued investigation is still active, or a handoff of a closed issue or to an agent a person removed from it

### 429

The agent is at its maximum concurrent investigations and its concurrency-limit policy discards new work instead of queueing it (the response carries the id of the recorded DISCARDED investigation), or the agent's or its LLM integration's max tokens are reached (the response carries a code and message).

- **Content-Type**: `application/json` / `StartInvestigationRejectedResponse`