Sources
Keep the monitoring you already run. Just see it in one place.
UptimeScout reads monitors from four services with a read-only key and shows them beside your own checks. Nothing is created, changed or deleted in those services — the app only ever reads.
Uptime Kuma
Reads your self-hosted server, either through its metrics endpoint with an API key, or through a public status page with no key at all.
What you enter
- Your server address, for example https://uptime.your-domain.com
- Either an API key, or the slug of a public status page
Where to find the key
In Uptime Kuma: Settings › API Keys › Add. With a key UptimeScout reads /metrics and sees every monitor. With a status-page slug instead — the part after /status/ in its URL — no key is needed and only the monitors on that page appear.
Where the request goes
Your own server — GET <your server>/metrics, or GET <your server>/api/status-page/<slug>
UptimeRobot
Reads your monitors 50 at a time, and turns the service's own error replies into messages you can act on.
What you enter
- A read-only API key
Where to find the key
In the UptimeRobot dashboard: API settings › create the Read-Only API Key. Do not use the Main API key — it can change your account, and UptimeScout only ever reads.
Where the request goes
https://api.uptimerobot.com/v2/getMonitors
Better Stack
Reads your Uptime monitors, following the API's own pagination and refusing to follow it anywhere else.
What you enter
- An API token for Uptime
Where to find the key
In Better Stack: Settings › API tokens › create a token for Uptime. UptimeScout only sends GET requests.
Where the request goes
https://uptime.betterstack.com/api/v2/monitors
Cronitor
Reads your monitors page by page over the standard API.
What you enter
- An API key
Where to find the key
In Cronitor: Settings › API Keys. If you can restrict a key's scope, allow it only to read monitors.
Where the request goes
https://cronitor.io/api/monitors
How to connect one
Three steps, and the app tests the connection before it saves.
- Open Sources and tap the plus, then choose the service.
- Enter the details above and tap Test Connection — the app will not save a source it cannot read.
- Tap Save. The monitors appear on your board, grouped under that source.
A local address such as http://192.168.1.10:3001 makes your device ask for local network access — allow it. Plain http:// is accepted only for addresses on your local network; anything on the public internet must be https://.
Sources are device-local: they do not sync, so connect them on each device you use. On the free plan the oldest source on each device syncs — 1 per device.
Your key
What happens to the key you paste in.
You are handing a third-party app a credential to your monitoring account. Here is exactly what the app does with it — each of these is enforced in code and covered by a test, not a statement of intent.
- The key is stored in that device's Keychain, with “after first unlock, this device only” protection.
- It is never written to the database, an export, a log or iCloud, and it never syncs to your other devices.
- It is sent only to the provider you configured it for. Requests to UptimeRobot, Better Stack and Cronitor always go to that provider's fixed API host, whatever a stored or imported record claims.
- A request carrying a key follows a redirect only to the same host. Any other redirect is refused rather than re-sending the key.
- Revealing a stored key in the app requires Face ID, Touch ID or your passcode.
This website will never ask you for an API key. Keys are entered in the app, on your device, and nowhere else. There is no account here and no form on this site at all — if a page claiming to be UptimeScout asks you to paste a key into a browser, it is not us.