Monitor a portfolio

A portfolio monitor watches your portfolio the way an oversight committee would: what it holds, how it differs from its benchmark and peers, how easily it could be sold down, and whether it stays inside the limits you set. Itoflow’s risk engine computes the figures; the agent explains what changed and why. What you’ll get: a scheduled report on the portfolio, with numbered findings, its tracking error and active weights against the benchmark, comparisons with peers, and liquidity at different portfolio sizes. Use any portfolio you keep in Itoflow: one you imported, a paper portfolio, or one connected to your broker. This guide compares it with the S&P 500 and a minimum-volatility peer fund. Swap in the benchmark, peers and limits that fit your portfolio.

Before you start

An Itoflow account.
A portfolio in Itoflow that no strategy runs. If you don’t have one yet, import your holdings or connect a broker. The assistant and the app can also help you build one along the way.

Quick start

Ask your AI assistant
In the Itoflow app
With the API

With Itoflow connected to Codex or Claude, paste this into your assistant:

Use Itoflow to set up oversight of one of my portfolios. List my portfolios and
ask me which one to monitor. If I don't have one yet, help me import my
holdings and show me the full import draft before saving it. Then propose a
fund-oversight monitor on that portfolio: benchmark S&P 500 (index GSPC.INDX,
basket SPY.US), peer fund USMV.US, a 4% tracking-error budget against the
benchmark, sector limits of 15 points and single-name limits of 6 points either
side of the benchmark, and a weekly report every Monday at 08:00
America/New_York. If the S&P 500 is a poor fit for what the portfolio holds,
suggest a better benchmark first. Show me the monitor before creating it. Once
I approve, create it, enable it, run the first report, and summarize its
findings.

Open in Claude

Start this in Claude with the Itoflow plugin.

Open in ChatGPT

Start this in ChatGPT with the Itoflow plugin.

Using another client? Copy the prompt with the button on the code block.

Open New monitor and choose Use an existing portfolio, then pick your portfolio. If you don’t have one, choose Search symbols or Upload a holdings file and Itoflow helps you build it.
Under What should this monitor track?, set a benchmark, such as SPY.US, any peer funds, and your limits, such as a 4% tracking-error band. Select Continue to chat. The chat opens with your message filled in. If you chose a holdings file, attach it in the chat box. Then send the message.
If you started without a saved portfolio, check the portfolio the agent prepares and confirm it.
The agent asks for anything it still needs, then saves the monitor paused and starts its first report. It tells you what it saved. Ask for any changes in the same chat.
On the monitor’s page, select Edit and set a schedule, such as weekly on Monday at 08:00.
Turn on Agent reports so the schedule runs. Without a schedule, this sets a daily 08:00 report in your time zone.
The first report appears on the monitor’s page when it finishes.

Check Report history for each scheduled date. If a previous date is still running, the new date shows a failure that names it, while the older report continues. Select a failed run to read the reason. An outage may delay the history update, but schedule history keeps each due date. A run still open at its next scheduled time becomes a visible failure. Pausing keeps dates already due and stops future dates; resuming skips the paused gap. A waiting report uses the configuration current when it starts and keeps its original local date.

You need an access token in ITOFLOW_ACCESS_TOKEN.

Find your portfolio

curl --fail-with-body --silent --show-error \
  'https://api.itoflow.ai/portfolios' \
  --header "Authorization: Bearer $ITOFLOW_ACCESS_TOKEN" |
jq '.portfolios[] | { portfolio_id, name, linked_strategy }'

Pick a portfolio whose linked_strategy is null and note its portfolio_id. To create one from your holdings first, see Import holdings.

Create the monitor

curl --fail-with-body --silent --show-error \
  'https://api.itoflow.ai/watchlists' \
  --header "Authorization: Bearer $ITOFLOW_ACCESS_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Portfolio oversight",
    "mandate": "Lead with material changes against the benchmark and explain what caused them.",
    "profile": "fund_oversight",
    "profile_config": {
      "subject": { "name": "My portfolio", "portfolio_id": "PORTFOLIO_ID" },
      "comparators": {
        "benchmark": { "name": "S&P 500", "index_symbol": "GSPC.INDX", "basket_symbol": "SPY.US" },
        "peer_funds": [{ "name": "Minimum volatility peer", "symbol": "USMV.US" }]
      },
      "thresholds": {
        "relative_weight": { "sector": 15, "single_name": 6 },
        "tracking_error_budget": 4
      }
    },
    "recurrence": { "kind": "weekly", "weekdays": ["monday"], "local_time": "08:00", "timezone": "America/New_York" }
  }'

Replace PORTFOLIO_ID with the ID from the previous step. The monitor starts paused. See fund-oversight monitors for every limit and its unit.

Enable it and run the first report

POST /watchlists/{id}/control with {"action": "enable"} arms the weekly schedule. To get a report now, POST /watchlists/{id}/reports/run.

Read the report

GET /watchlists/{id}/active-execution shows the run in progress. When it finishes, GET /watchlists/{id}/reports/latest returns the report.

Limits

A strategy can’t run the portfolio you monitor.
Reports use the portfolio’s current positions, so you can’t run a report for an earlier date.
Risk figures measure a fund held beside other holdings through its dated holdings at the line’s signed weight. Holdings lists, concentration and liquidity keep the fund line.
Each peer fund needs published holdings; a symbol with price history alone isn’t enough.
A plain index with no basket fund is compared by returns only.

Next steps

Monitors: every limit, warning level and report field.
Get a daily news brief: add news on the portfolio’s holdings.

Get started

Platform

Use cases

Features

HTTP API

Troubleshooting

Endpoints