strategy[net]
Get started
API

Programmatic access to StrategyNet factor workflows.

The API exposes the same research primitives used inside the product: factor catalogs, ranked scores, optimizer inputs, cached analytics, scenario research, and reviewed execution staging.

Example request
curl https://api.strategynet.xyz/v1/factors/momentum/scores \
  -H "Authorization: Bearer $STRATEGYNET_API_KEY" \
  -G \
  --data-urlencode "universe=us_equities" \
  --data-urlencode "as_of=latest"

API workflow

Use the API when a desk needs StrategyNet output inside internal dashboards, scheduled jobs, model review notebooks, or execution-control systems.

Authenticate

Create a scoped API key from the dashboard, keep it server-side, and send it with each request as a bearer token.

Read factor state

Pull daily or intraday factor ranks, symbol projections, validation metrics, and portfolio-ready signal bundles.

Compose workflows

Use factor outputs in optimizers, scheduled reports, alerts, or execution review workflows without rebuilding the research stack.

Automate refresh

Schedule updates around market sessions, model refreshes, or desk review cycles with consistent response envelopes.

Endpoint layout

Public API resources are organized around stable workflow nouns rather than product screens, so integrations can evolve without mirroring the UI.

GET/v1/factors

Factor catalog

List available factor families, descriptions, coverage, and release cadence.

GET/v1/factors/{factor_id}/scores

Factor scores

Fetch ranked factor values by date, universe, symbol set, and horizon.

POST/v1/strategies/optimize

Strategy optimizer

Submit selected factors and constraints to receive a candidate market-neutral basket.

POST/v1/research/market-impact

Research endpoints

Run supported scenario and market-impact analytics from the same API surface used by product workflows.

GET/v1/cache/lookup

Cached analytics

Retrieve previously computed analytics when a workflow needs deterministic replay or low-latency reads.

POST/v1/execution/stage

Execution staging

Stage reviewed candidate baskets for connected execution providers where supported.

Access model

  • Bearer-token authentication with dashboard-managed keys.
  • Authenticator-app two-factor authentication for account access.
  • Plan-aware limits for live factors, scheduled jobs, exports, and API compute.
  • Server-side usage recommended; browser-exposed API keys should be treated as compromised.

Response model

  • request_id for traceability across support, logs, and retries.
  • as_of and generated_at timestamps so downstream systems can distinguish market date from compute time.
  • data payloads shaped by endpoint: factors, scores, portfolios, diagnostics, or scenario output.
  • warnings for partial coverage, stale inputs, entitlement limits, or fallback model paths.
Current focus

Built for controlled research automation.

StrategyNet API access is designed for server-side workflows that need repeatable factor evidence, optimizer output, and reviewed handoff into execution tooling.

Factor monitoringIntraday analyticsScoped access
See API plans

API output is for research and analytical workflows. It is not investment advice, a recommendation, or an instruction to trade any security.