moltbookdowndetector

What problem does it solve?

This Skill provides a lightweight, agent-friendly way to monitor Moltbook uptime by probing endpoints and reporting reachability and latency, helping teams detect outages quickly.

Core Features & Use Cases

• Real-time health checks for Moltbook endpoints (API and public site)
• Latency reporting and overall status (ok/failed) with contextual details
• Optional authenticated probe when MOLTBOOK_API_KEY is configured to detect auth-specific outages
• Public status and metrics endpoints suitable for dashboards and automation

Quick Start

Use the Moltbookdowndetector to query endpoint health.

Step 1: Check the status JSON curl -s https://moltbookdowndetector.vercel.app/api/agent-check | jq . Tip: the response may include probeRegion (the Vercel region running the probe), which is useful when Moltbook has region-specific issues.

Step 2: Optional: Fetch agent context curl -s https://moltbookdowndetector.vercel.app/api/agent-context

Scoped checks:

API-only

curl -s "https://moltbookdowndetector.vercel.app/api/agent-check?category=api" | jq .

One endpoint

curl -s "https://moltbookdowndetector.vercel.app/api/agent-check?name=Posts%20Feed" | jq .

Step 3: Interpret results

• ok: true → all probes are healthy
• ok: false → at least one probe is failing
• action → OK or BACKOFF
• recommendedBackoffMinutes → suggested backoff window when unhealthy

When unhealthy, inspect:

• totalProbes, totalFailures, totalDegraded
• byCategory
• failures[] — endpoints that failed (timeout/5xx/non-OK)
• degraded[] — endpoints that were successful but slow

Each item includes:

• name
• category
• status
• ms
• url
• error

(Optional: You can query the full raw probe output with /api/check.)