Read state context before you commit to rollout

Dates alone are not enough for business approval.
The state guide endpoints give context around why those dates exist.

Endpoints

• GET /api/v1/state-guides
• GET /api/v1/state-guides/{state_code}

What business questions these answer

• Which states are currently supported in this phase?
• What notice requirement applies to each jurisdiction?
• Is the timeline logic different for one state vs another, and in what way?

How this helps procurement

Instead of asking engineering to summarize legal logic in a meeting, you can share the state guide result directly and keep decision-makers aligned.

Suggested workflow

1. Pull supported states for a clean scope.
2. Open two to three high-value states.
3. Store the differences in a single comparison table for stakeholders.
4. Use that table as the basis for pilot scope and legal sign-off.