Skip to main content

Right now

The check above runs in your browser with a read-only GET https://api.dualmindlab.tech/health. If it fails here but works with curl, suspect your network or an extension first.

Health endpoints

/health answers from the container without touching Supabase or any provider. A healthy /health with failing battles points at configuration (Supabase keys, AI Gateway) rather than hosting. See Troubleshooting.
Response
instanceId is the Durable Object ID of the container that answered (local when you run the API yourself). With one container it stays the same until the next deploy or restart.

A live read through the database

The leaderboard below is fetched from your browser with GET https://api.dualmindlab.tech/api/arena/model-stats. If it loads, the API, Supabase and the v_leaderboard view are all working.

Watching the service

1

Keep-alive

The dualmind-api Worker’s cron pings /health every five minutes; its log line is [keep-alive] Container health: 200.
2

Logs

npx wrangler tail dualmind-api streams Worker and container logs. Every request logs a start and end line with its correlation ID, status and duration.
3

After a deploy

CI polls /health up to five times. Then run the release checklist.
There is no public status page or external uptime monitor wired up yet. Adding one (and alerts on error rates) is on the roadmap.
Last modified on October 18, 2026