Diagnostics

Cloudflare function diagnostics

Use this page after deployment to verify that your Pages Functions are live and responding correctly on the real domain. This is the fastest way to see whether the function-backed tool stack is actually working without guessing from the repo alone.

This page tests the live deployed endpoints. It does not prove your repo is correct in theory. It tells you whether the running site is responding in practice.
Tests

The packet and planner tests use safe sample Indiana payloads so you can verify live behavior quickly.

Endpoint

/api/health

No result yet.
Endpoint

/api/seller-packet-builder

No result yet.
Endpoint

/api/county-office-planner

No result yet.
What success looks like
  • /api/health returns JSON with ok: true
  • Packet builder returns ok: true and a score / summary
  • County planner returns ok: true and an office plan
Common failures
  • 404 means the function is not being served at that path
  • 405 means method mismatch
  • 400 means validation passed through but payload failed
  • HTML instead of JSON often means routing or deployment issues
Next move after passing

Once these pass on the live domain, the function-backed tools are real enough to use and refine. Then it makes sense to standardize links and route more traffic to the workbench.