# OpenPing docs

Short pages in plain words, with examples you can paste. New here? Start with the [quickstart](https://openping.ai/docs/quickstart). Building an AI agent? Read [for AI agents](https://openping.ai/docs/agents); every page is also plain Markdown, listed in [/llms.txt](https://openping.ai/llms.txt).

## Start

- [**Quickstart**](https://openping.ai/docs/quickstart) — From a URL to monitors, alerts and a status page.

## What it checks

- [**Monitors**](https://openping.ai/docs/monitors) — Each type and what it checks.
- [**Agent tests**](https://openping.ai/docs/agent-tests) — Ask a question on a schedule and judge the answer.
- [**MCP monitors**](https://openping.ai/docs/mcp-monitors) — The handshake, the tool list and every change to it.
- [**Heartbeats**](https://openping.ai/docs/heartbeats) — Know when a scheduled job is late or fails.

## When something breaks

- [**Alerts**](https://openping.ai/docs/alerts) — Who hears about what, and how it stays calm.
- [**Status pages**](https://openping.ai/docs/status-pages) — A page your users can trust, made for you.

## Build with it

- [**Monitors as code**](https://openping.ai/docs/monitors-as-code) — Keep monitors in openping.yml in your repo.
- [**CLI**](https://openping.ai/docs/cli) — Run the same checks on a laptop and in CI.
- [**API**](https://openping.ai/docs/api) — Everything the app can do, over REST.
- [**MCP server**](https://openping.ai/docs/mcp-server) — Let your AI assistant set up and read monitoring.
- [**For AI agents**](https://openping.ai/docs/agents) — How an agent uses OpenPing end to end, and what needs a person’s yes.