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

# UptimeRobot

> Connect UptimeRobot to your Atako agents — 8 read and 4 write actions.

Let your agents list, create, pause, resume and delete uptime monitors, and read incidents, status pages and alert contacts via the UptimeRobot API.

## Connection

* **Authentication**: API key (Main API key).

<Note>
  Sign in at dashboard.uptimerobot.com → Integrations → API section → create the Main API key and copy it. Use the Main API key: a Read-only API key only allows the read actions (creating, pausing, resuming or deleting monitors needs the Main API key), and a Monitor-specific API key only reads a single monitor.

  See [UptimeRobot's documentation](https://dashboard.uptimerobot.com/integrations).
</Note>

## Read actions (8)

| Action | Description |
| - | - |
| `get_account` | Get the account that owns the API key (email, name, monitor count and limit, active subscription). |
| `get_incident` | Get one incident by its ID, including root cause details (see list\_incidents). |
| `get_monitor` | Get one monitor by its ID (type, URL, interval, status, alert contacts, tags). |
| `list_alert_contacts` | List the account's alert contacts, with the IDs used in create\_monitor.assignedAlertContacts. |
| `list_incidents` | List incidents (cursor pagination: cursor is an incident ID passed as a string of digits). Optional filters: monitor\_id (integer), monitor\_name (partial match), started\_after and started\_before (ISO 8601 date-time strings). |
| `list_monitor_groups` | List monitor groups (cursor pagination: pass the returned cursor to get the next page). |
| `list_monitors` | List monitors (cursor pagination: pass the returned cursor to get the next page). Optional filters, combined with AND: status (comma-separated string of PAUSED, STARTED, UP, LOOKS\_DOWN, DOWN), name and url (case-insensitive partial match), tags (comma-separated tag names), groupId (integer, see list\_monitor\_groups), limit (1–200, default 50). |
| `list_status_pages` | List public status pages (cursor pagination: pass the returned cursor to get the next page). |

## Write actions (4)

| Action | Description |
| - | - |
| `create_monitor` | Create an HTTP, KEYWORD, PING or PORT monitor. Arguments: type: string enum "HTTP" \| "KEYWORD" \| "PING" \| "PORT". friendlyName: string. url: string (full URL for HTTP/KEYWORD, hostname or IP for PING/PORT). interval: integer, seconds between checks (min 30; the shortest interval depends on the plan). timeout: integer, seconds (0–60). port: integer 1–65535, REQUIRED for PORT and only for PORT. keywordType: string enum "ALERT\_EXISTS" \| "ALERT\_NOT\_EXISTS", keywordCaseType: string enum "CaseSensitive" \| "CaseInsensitive" and keywordValue: string — all three REQUIRED for KEYWORD and only for KEYWORD. httpMethodType: optional string enum HEAD, GET, POST, PUT, PATCH, DELETE, OPTIONS (HTTP/KEYWORD only, default HEAD). assignedAlertContacts: optional array of objects \{ alertContactId: integer (see list\_alert\_contacts), threshold: integer minutes, recurrence: integer minutes } — all three keys required, use 0 for threshold and recurrence on the Free plan. tagNames: optional array of strings. groupId: optional integer (see list\_monitor\_groups, 0 = no group). |
| `delete_monitor` | Delete a monitor permanently. Arguments: monitor\_id: integer (the monitor ID, see list\_monitors). |
| `pause_monitor` | Pause a monitor: it stops being checked until resumed. Arguments: monitor\_id: integer (the monitor ID, see list\_monitors). Idempotent. |
| `resume_monitor` | Resume (start) a paused monitor. Arguments: monitor\_id: integer (the monitor ID, see list\_monitors). Idempotent. |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.

***

*Last reviewed against the provider API: September 2026.*


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