Loading Legacy
Transparency for users, search engines, and partners. This page summarizes how CodeOpx tools handle public datasets—not every edge case, but the principles and primary systems behind the numbers.
Many US indicators are loaded from the FRED API using a repository secret FRED_API_KEY in automation. Examples used on this site include (non-exhaustive): MORTGAGE30US / MORTGAGE15US for national mortgage survey anchors, state unemployment {ST}UR patterns with UNRATE for the US average, CPIAUCSL for CPI-U, and Treasury / policy series such as FEDFUNDS, DGS2, DGS10, and T10Y2Y. Exact series appear on each tool page.
State minimum wage: the minimum wage by state pages summarize the U.S. Department of Labor Wage and Hour Division consolidated state table (with effective dates on each page). That dataset is maintained as static copy aligned to DOL’s published table, not via FRED.
Entry point for linked tools: US economy data hub.
Air quality (AQI): city snapshots are built from the Open-Meteo air-quality API with geocoding for coordinates. Pages state the provider and last update.
Gas prices by state: state averages are derived from AAA public state average pages, normalized into our JSON cache on a schedule. This is not a real-time tick; it reflects AAA’s published averages at ingest time.
Holidays: public holiday metadata for service-status style tools is sourced from Nager.Date where applicable, with normalized fields for display.
Scheduled workflows refresh JSON datasets in the repository when upstream values change. A separate freshness check job can fail if a dataset exceeds a maximum age threshold—this is a safety signal for maintainers, not a guarantee that every number on the site is identical to a government PDF at every second.
If you believe a dataset is wrong, stale, or mislabeled, contact us via the contact page with the tool URL and a screenshot or official reference. We prioritize corrections that affect user trust or factual accuracy.