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

# Target discovery

> Review candidate targets in Target Inventory and manage discovery context, schedules, and suggestions through the dashboard, API, or MCP.

## Overview

Discovery proposes candidate targets for your organization. Review suggestions before accepting them into your target inventory. Discovery is available only when enabled for your organization.

The public API and MCP support the following workflow:

1. Read the current discovery status, context, and schedule.
2. Update the context note with information that helps identify your organization's assets.
3. Start a discovery run or configure a recurring schedule.
4. List pending suggestions.
5. Accept relevant suggestions or dismiss those you do not want to add.

Accepting a suggestion creates a target through the normal target workflow. Check its verification state and complete any required ownership verification before starting an assessment.

## Dashboard

When Discovery is enabled, open **Target Inventory** to find its Discovery panel. The panel provides:

* **Add background**, **Edit background**, or **View background** for organization-specific information that guides discovery.
* **Schedule** for the cadence, local time, and time zone.
* **Run now** and **Stop** controls, with current run status.
* **Accept** and **Dismiss** actions on candidate targets.

Review a suggestion before accepting it. Acceptance adds a target; it does not demonstrate that the target has been assessed or that ownership verification is complete. Owners and admins manage discovery from the dashboard. Other members can review available background and suggestions.

## API operations

| Action               | Endpoint                                                 |
| -------------------- | -------------------------------------------------------- |
| Read status          | `GET /v1/discovery`                                      |
| Set context          | `PUT /v1/discovery/context`                              |
| Set schedule         | `PUT /v1/discovery/schedule`                             |
| Start a run          | `POST /v1/discovery/runs`                                |
| Cancel a run         | `POST /v1/discovery/runs/{run_id}/cancel`                |
| List suggestions     | `GET /v1/discovery/suggestions`                          |
| Accept a suggestion  | `POST /v1/discovery/suggestions/{suggestion_id}/accept`  |
| Dismiss a suggestion | `POST /v1/discovery/suggestions/{suggestion_id}/dismiss` |

Schedules support daily or weekly runs, a local time, and an IANA time zone such as `America/Los_Angeles`. Weekly schedules require `day_of_week`, where `0` is Monday and `6` is Sunday. Daily schedules omit that field or set it to `null`.

Suggestions have a lifecycle status of `pending`, `accepted`, `dismissed`, or `superseded`. Use the endpoint reference for request fields and pagination.

## MCP

Begin with `get_current_context` to check whether Discovery is enabled. Use `get_discovery_status`, `update_discovery_context`, and `update_discovery_schedule` to inspect and configure it. Run and review discovery with `start_discovery_run`, `list_discovery_suggestions`, `accept_discovery_suggestion`, and `dismiss_discovery_suggestion`.