> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# UptimeRobot

> Connect UptimeRobot to CloudThinker to track monitor status, uptime history, and recent incidents with a read-only API key

Connect your UptimeRobot account to let CloudThinker agents see which monitors are down or paused, read uptime and response-time history, and review recent incidents. UptimeRobot authenticates with its **Read-only API key**, which cannot create, update, or pause monitors, so agents can only look.

## Prerequisites

* An **UptimeRobot account** that owns the monitors you want investigated.
* The account's **Read-only API key**, not the Main API key.

<Info>
  Use the Read-only key only. UptimeRobot documents that the Main API key has the same permissions as your account, while the Read-only key only queries data.
</Info>

## Setup

<Steps>
  <Step title="Open UptimeRobot">
    Sign in to your UptimeRobot dashboard and go to **Integrations & API**.
  </Step>

  <Step title="Copy the Read-only API key">
    Copy the **Read-only API Key**. Do not copy the Main API Key.
  </Step>

  <Step title="Add the connection in CloudThinker">
    Navigate to **Connections → UptimeRobot** and enter:

    * **UPTIMEROBOT\_READ\_ONLY\_API\_KEY**: the key you just copied

    Click **Connect**. CloudThinker verifies the key and shows a **Connected** status.
  </Step>
</Steps>

## Connection details

| Field | Description | Example |
| - | - | - |
| **UPTIMEROBOT\_READ\_ONLY\_API\_KEY** | The UptimeRobot Read-only API key | `<your-read-only-api-key>` |

<Note>
  There is no region or URL to enter. UptimeRobot's own API limits apply to everything agents read through this connection.
</Note>

## Required permissions

The Read-only API key is the only permission setting. It reads monitors, uptime statistics, and incidents, and it cannot create, update, or pause a monitor.

<Tip>
  Follow least privilege: never connect the Main API key. If you later need agents to change monitors, change them in UptimeRobot yourself.
</Tip>

## Agent capabilities

Once connected, agents read monitor and incident data. CloudThinker uses three read actions on this connection and nothing else.

| Capability | Description |
| - | - |
| **Discovery** | Summarize account health for a time window: monitors that are down or paused, and recent incidents |
| **Monitor inventory** | List monitors with their status and aggregate health |
| **Uptime and response time** | Read uptime statistics and response-time values over a time range |
| **Incident summary** | List recent incidents with their status and timing |

Agents leave out monitor settings, custom headers, incident logs, contacts, and integration details. They cap every read and say when a list is partial.

### Verify the connection

```text theme={null}
Run UptimeRobot discovery for the last 24 hours and summarize monitors that are down or paused and any recent incidents
```

### Example prompts

```text theme={null}
Which UptimeRobot monitors are down right now?
What was the uptime of my API monitor over the last 7 days?
List the UptimeRobot incidents from yesterday and which monitors they affected
```

UptimeRobot returns monitor lists in pages of 100 and keeps response-time history for ranges between 1 hour and 90 days. Ask for a narrower range when a question needs more detail.

## Troubleshooting

<Accordion title="The key is rejected">
  UptimeRobot reports an authentication failure or an invalid key when the key is wrong or has extra characters. Check for spaces around the pasted key, confirm you copied the **Read-only API Key** from **Integrations & API**, and generate a new key if it still fails.
</Accordion>

<Accordion title="Health shows as unavailable">
  The uptime statistics read failed, so agents report health as unavailable instead of guessing. Run discovery again. If UptimeRobot returned HTTP `429`, wait at least 60 seconds first.
</Accordion>

<Accordion title="429 Too Many Requests">
  UptimeRobot's limit depends on your plan, applies per rolling 60-second window, and is shared with every other tool that uses your account's API. Wait 60 seconds and retry with a smaller question.
</Accordion>

<Accordion title="Agents cannot pause or change a monitor">
  That is by design. The Read-only API key cannot create, update, or pause monitors, and CloudThinker does not try. Make the change in UptimeRobot.
</Accordion>

## Security

* **Least privilege** — grant only the permissions the agents need for your use case; start read-only and widen later.
* **Read-only by default** — use read-only credentials unless you want agents to make changes through this connection.
* **Rotate credentials** — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
* **Revoke on offboarding** — remove the credential at the provider when you delete a connection or a teammate leaves.

- **Never use the Main API key** — it carries the same permissions as your UptimeRobot account.
- **Shared rate limit** — keep other tools using the same account in mind, because they draw from the same request quota.

## Related

<CardGroup cols={2}>
  <Card title="Better Stack Connection" icon="https://mintcdn.com/cloudthinker/uIxpc0ZqZtveGXWt/images/icons/betterstack.svg?fit=max&auto=format&n=uIxpc0ZqZtveGXWt&q=85&s=61b580a94f2f0b8abd07eb7f494739c2" href="/guide/connections/betterstack" width="24" height="24" data-path="images/icons/betterstack.svg">
    Uptime, incidents, and log search
  </Card>

  <Card title="Datadog Connection" icon="https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/datadog.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=e8382167f2a1eb1e00971b5f4d703d48" href="/guide/connections/datadog" width="24" height="24" data-path="images/icons/datadog.svg">
    Log search, metrics, and monitoring
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.