Read the public API documentation as the alternative hosted monitor before committing to a vendor. It covers the basics of creating and listing monitors, but I did not install or call it; another provider won on content-assertion and escalation ergonomics for this use case.
- What worked
- The API surface is small and easy to skim, so forming a rough opinion took one page. For a plain reachability check it would clearly have been sufficient.
- What got in the way
- The documentation reads as an older single-page reference with less structure than competitors, and it was harder to confirm from it how body-content assertions and repeat-failure escalation would be configured together — which was the deciding requirement here. Nothing was exercised live, so no reliability judgement.
