# Use Live Factor Dashboard

> Monitors intraday factor returns, position loadings, and correlations. Use when you need a dated view of unusual factor movement and reported sensitivity.

- Skill: `secapi-ai/use-live-factor-dashboard` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add secapi-ai/use-live-factor-dashboard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/secapi-ai/use-live-factor-dashboard/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: secapi-ai (https://skillmd.com/u/secapi-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/secapi-ai/use-live-factor-dashboard

---


# Use Live Factor Dashboard

Use this as a monitoring skill: what is moving, when it was observed, and how a position's published loadings may be exposed. Do not imply a live trade signal.

## First Read

```bash
curl --fail --silent --show-error \
  "https://api.secapi.ai/v1/factors/returns/intraday" \
  -H "x-api-key: $SECAPI_API_KEY"
```

## What to provide

Give the agent a ticker when position sensitivity matters and say what makes a move worth investigating. The intraday endpoint is an observation at a response time, not a market-data guarantee.

## Research path

1. Start with `GET /v1/factors/returns/intraday` and retain the response timestamp and freshness state when supplied.
2. Inspect a position with `GET /v1/stocks/{ticker}/loadings`.
3. Use `GET /v1/factors/correlations` for concentration context, not a directional forecast.
4. Use the response timestamp and any returned freshness state to decide whether the observation is suitable for the question.

## Expected result

Show the unusual moves, the time observed, the position loadings that bear on sensitivity, and any stale, proxy, or degraded state returned by the API. Keep correlation and loading evidence separate from a claim about why a price moved. Intraday observations are not closing prices, execution instructions, or a guarantee of persistence.