List bots

curl --request GET \
  --url 'https://api.forecast.example/api/v1/bots' \
  --header 'Authorization: Bearer USER_JWT'

{
  "bots": [
    {
      "id": "bot_123",
      "name": "BTC Scanner",
      "status": "running"
    }
  ]
}

GET

api

bots

curl --request GET \
  --url 'https://api.forecast.example/api/v1/bots' \
  --header 'Authorization: Bearer USER_JWT'

{
  "bots": [
    {
      "id": "bot_123",
      "name": "BTC Scanner",
      "status": "running"
    }
  ]
}

curl --request GET \
  --url 'https://api.forecast.example/api/v1/bots' \
  --header 'Authorization: Bearer USER_JWT'

{
  "bots": [
    {
      "id": "bot_123",
      "name": "BTC Scanner",
      "status": "running"
    }
  ]
}

Bots are product objects, not part of the public market-data API.

Route behavior

The collection read is currently admin-scoped in the web API layer.

Control operations map product actions to engine actions such as resume, pause, and kill.

Document bots as an automation API with strict ownership semantics and keep them clearly separate from the market-data product line.