Skip to main content
GET
/
api
/
cadence
Cadence Alignment
curl --request GET \
  --url https://api.example.com/api/cadence
{
  "weeklySummary": {},
  "monthlySummary": {},
  "alignmentStatus": "<string>",
  "mismatchedConstraints": [
    {
      "constraint": "<string>",
      "weeklyValue": "<any>",
      "monthlyValue": "<any>",
      "severity": "<string>"
    }
  ],
  "generatedAt": "<string>",
  "version": "<string>"
}

Endpoint

GET /api/cadence
Returns alignment analysis between weekly and monthly regime summaries, helping identify discrepancies in regime classification across different time horizons. This is a validation endpoint to ensure consistency in regime signals.

Response

weeklySummary
object
required
Complete weekly summary object (same structure as weekly endpoint)
monthlySummary
object
required
Complete monthly summary object (same structure as monthly endpoint)
alignmentStatus
string
required
Alignment status indicatorPossible values:
  • "ALIGNED" - Weekly and monthly assessments are consistent
  • "MISALIGNED" - Discrepancies detected between timeframes
  • "DIVERGENT" - Significant contradiction in regime signals
mismatchedConstraints
array
required
Array of constraint mismatches between weekly and monthly summaries
generatedAt
string
required
ISO 8601 timestamp when analysis was generated
version
string
required
API version (e.g., “v1”)

Example Request

curl https://your-domain.com/api/cadence

Example Response (Aligned)

{
  "weeklySummary": {
    "copy": "This week shows expansion regime with base rate at 4.15%...",
    "structured": {
      "regime": "EXPANSION",
      "constraints": ["NONE"]
    }
  },
  "monthlySummary": {
    "copy": "March 2026 demonstrates expansion characteristics...",
    "structured": {
      "regime": "EXPANSION",
      "constraints": ["NONE"]
    }
  },
  "alignmentStatus": "ALIGNED",
  "mismatchedConstraints": [],
  "generatedAt": "2026-03-03T10:00:00Z",
  "version": "v1"
}

Example Response (Misaligned)

{
  "weeklySummary": {
    "copy": "This week shows late-cycle signals...",
    "structured": {
      "regime": "LATE_CYCLE",
      "constraints": ["DEFER_MAJOR_CAPEX"]
    }
  },
  "monthlySummary": {
    "copy": "March 2026 demonstrates expansion characteristics...",
    "structured": {
      "regime": "EXPANSION",
      "constraints": ["NONE"]
    }
  },
  "alignmentStatus": "MISALIGNED",
  "mismatchedConstraints": [
    {
      "constraint": "regime_classification",
      "weeklyValue": "LATE_CYCLE",
      "monthlyValue": "EXPANSION",
      "severity": "HIGH"
    },
    {
      "constraint": "capex_guidance",
      "weeklyValue": "DEFER_MAJOR_CAPEX",
      "monthlyValue": "PROCEED_NORMAL",
      "severity": "MEDIUM"
    }
  ],
  "generatedAt": "2026-03-03T10:00:00Z",
  "version": "v1"
}

Caching Behavior

  • Cache Duration: 1 hour (3600 seconds)
  • Runtime: Edge
  • Revalidation: 3600 seconds

Alignment Logic

The endpoint compares:
  1. Regime classification - Do weekly and monthly agree on regime type?
  2. Constraint recommendations - Are operational constraints consistent?
  3. Signal direction - Are trends pointing the same way?

Interpreting Alignment Status

ALIGNED

Weekly and monthly summaries are consistent. Regime signals are stable across timeframes. Safe to act on recommendations.

MISALIGNED

Minor discrepancies detected. Common during regime transitions. Review mismatchedConstraints for specifics. Consider waiting for next update before major decisions.

DIVERGENT

Significant contradictions between timeframes. May indicate:
  • Rapid regime transition in progress
  • Data quality issues
  • Unusual market volatility
Recommend investigation before acting on either signal.

Use Cases

  • Validation: Sanity-check regime signals before major decisions
  • Transition detection: Identify when regime is actively shifting
  • Data quality: Spot potential issues in source data
  • Decision confidence: Higher confidence when aligned, caution when misaligned
  • Monitoring dashboards: Track alignment over time

Build docs developers (and LLMs) love