Skip to main content
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.
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.

​
Setup

1

Open UptimeRobot

Sign in to your UptimeRobot dashboard and go to Integrations & API.
2

Copy the Read-only API key

Copy the Read-only API Key. Do not copy the Main API Key.
3

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.

​
Connection details

There is no region or URL to enter. UptimeRobot’s own API limits apply to everything agents read through this connection.

​
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.
Follow least privilege: never connect the Main API key. If you later need agents to change monitors, change them in UptimeRobot yourself.

​
Agent capabilities

Once connected, agents read monitor and incident data. CloudThinker uses three read actions on this connection and nothing else. 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

​
Example prompts

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

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.
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.
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.
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.

​
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.

Better Stack Connection

Uptime, incidents, and log search

Datadog Connection

Log search, metrics, and monitoring