Skip to main content
Return compact SEC API factor definitions, with trust and methodology metadata available on request
Audience: application and coding agent.

​
Canonical metadata

  • requestId
  • traceparent

​
Example request

curl -X GET \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/factors/catalog"

​
Example response

{
  "object": "list",
  "data": [
    {
      "object": "factor_definition",
      "id": "factor:VALUE",
      "key": "VALUE",
      "name": "Value",
      "category": "style",
      "description": "Long cheaper stocks and short expensive stocks using SecAPI-owned factor construction.",
      "benchmarkSymbol": "VLUE",
      "equation": {
        "long_leg": 1,
        "short_leg": -1
      },
      "orthogonalizedAgainst": [
        "MARKET"
      ],
      "catalogStatus": "launch_ready",
      "sourceAvailabilityStatus": "implemented",
      "launchUniverseStatus": "launch_candidate",
      "launchClaimStatus": "candidate_pending_history_freshness_proof",
      "launchParityCategory": "style",
      "responseMode": "compact",
      "expansionHints": [
        "Use include=trust for launchReadiness, qualityProof, provenance, source rights, methodology, and revision metadata."
      ]
    }
  ],
  "hasMore": false,
  "nextCursor": null,
  "categories": [
    "market",
    "style",
    "sector",
    "industry"
  ],
  "requestId": "req_2ZK8Q1W9F4M6P7R3",
  "traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}

​
Give this prompt to your agent

​
Failure posture

  • treat non-2xx responses as contract-aware failures, not free-form errors
  • preserve requestId and traceparent in logs and downstream reports
  • if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff