Skip to content
AlpineDataWorks.AI
System status

Checking systems…

Checking

Checked live · right now, from your browser

  • Marketing site

    Cloudflare Pages · global edge

    fetches /catalog.json from the edge

    Checking…
  • Catalog & discovery

    /catalog.json · /llms.txt · /.well-known/mcp.json · openapi

    fetches the live OpenAPI spec

    Checking…
  • Intelligence API

    api.alpinedataworks.com · REST · full catalog

    API answers its health endpoint

    Checking…
  • MCP server

    api.alpinedataworks.com/mcp · keyless discovery

    reads the live tool manifest

    Checking…

Not yet monitored · no automated check

  • Payments & billing

    no automated check yet — a billing canary is planned

    Not monitored
  • Accounts & email

    no automated check yet

    Not monitored
  • GeoHealth flagship

    key-required, so it cannot be checked from this page

    Not monitored
  • GeoHealth history

    key-required, so it cannot be checked from this page

    Not monitored
  • Komodo QA monitor

    runs nightly; not surfaced publicly yet

    Not monitored
  • Auto-backfill engine

    runs daily; not surfaced publicly yet

    Not monitored

4 of 4 live checks run from your browser against public endpoints, right now, on this page load. The other 6 have no automated check yet — they are not failing, they are simply not measured, and we won't show you a green light we haven't earned. Adding real checks for them is in progress.

The Intelligence API serves the full catalog via REST (/v1/intelligence/<id>) and MCP (/mcp, keyless discovery — the tool count above is read live from the manifest, not hardcoded). GeoHealth spans 7 layers across 3,143 counties, 32,520 ZCTAs, and 29,923 cities.