UptimeRobot API
58
AI ReadinessFoundational (C+)58/100
Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey18 EndpointsREST
For Agents
Programmatically get monitors, create a monitor. Covers 18 operations with apiKey authentication.
Use for: I need to monitors, I want to a monitor, Search for edit a monitor, Find all a monitor
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
UptimeRobot monitors websites and services for uptime. The API provides operations for managing monitors, alert contacts, maintenance windows, and public status pages. The API exposes 18 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the UptimeRobot API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the UptimeRobot API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fuptimerobot.com%2Fuptimerobot" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fuptimerobot.com%2Fuptimerobot" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with UptimeRobot API.
Get monitors
Create a monitor
Edit a monitor
Delete a monitor
Reset a monitor
Use Cases
Patterns agents use UptimeRobot API for, with concrete tasks.
★ CRM Operations
Use the UptimeRobot API to perform crm operations programmatically. The API provides 18 endpoints covering core functionality including get monitors, create a monitor, edit a monitor.
Call POST /getMonitors to get monitors
Automated Account Management
Automate account operations by combining multiple UptimeRobot API endpoints. Agents can create a monitor and then edit a monitor in a single workflow.
Call POST /newMonitor to create a monitor, then verify the result
AI Agent Integration via Jentic
AI agents discover and call UptimeRobot API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get monitors', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
18 endpoints — uptimerobot monitors websites and services for uptime.
METHOD
PATH
DESCRIPTION
POST
/getMonitors
Get monitors
POST
/newMonitor
Create a monitor
POST
/editMonitor
Edit a monitor
POST
/deleteMonitor
Delete a monitor
POST
/resetMonitor
Reset a monitor
POST
/getAlertContacts
Get alert contacts
POST
/newAlertContact
Create an alert contact
POST
/editAlertContact
Edit an alert contact
POST
/getMonitors
Get monitors
POST
/newMonitor
Create a monitor
POST
/editMonitor
Edit a monitor
POST
/deleteMonitor
Delete a monitor
POST
/resetMonitor
Reset a monitor
POST
/getAlertContacts
Get alert contacts
POST
/newAlertContact
Create an alert contact
POST
/editAlertContact
Edit an alert contact
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
U
UptimeRobot API
- Foundational (C+)58/100
99
Foundational Compliance56
Developer Experience & Jentic Compatibility42
AI-Readiness & Agent Experience94
Agent Usability50
Security49
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
42
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
18%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
49
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: D+Signals: 1
49%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the UptimeRobot API by hand means passing your API key on every POST, learning its form-style request bodies, and paging through monitors and alert contacts yourself. Through Jentic you install once, import UptimeRobot from the API Directory, store the key once, and your agent calls it.
Permission scoping
UptimeRobot addresses its monitors through POST bodies rather than the URL path, so limit the agent to the operations it needs, such as getMonitors and editMonitor. You choose that operation set, so destructive ones like deleteMonitor are not included unless you add them.
Credential isolation
Your UptimeRobot API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get monitors' or 'create a new monitor', and Jentic returns the matching UptimeRobot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using UptimeRobot API through Jentic.
What authentication does the UptimeRobot API use?
The UptimeRobot API uses an API key passed in the `api_key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get monitors with the UptimeRobot API?
Yes. Use the POST /getMonitors endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the UptimeRobot API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get monitors through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get monitors'. Jentic returns the matching UptimeRobot API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the UptimeRobot API have?
The UptimeRobot API exposes 18 endpoints covering account, alert contacts, maintenance windows operations.
Can I limit what my agent is allowed to do with the UptimeRobot API?
Yes. Because you run Jentic One yourself, you decide which UptimeRobot operations the agent can call and which credentials it may use. UptimeRobot addresses its monitors through POST bodies rather than the URL path, so you scope by operation set, for example allowing getMonitors and editMonitor while leaving destructive calls like deleteMonitor out unless you add them. Your rules are enforced at execution time, and the API key is injected then rather than exposed to the agent.
GET STARTED