§ faq
questions, answered.
Everything about plans, monitoring, and your account. Still stuck? Ask us.
Frequently asked questions
General
Do you have an API?
niceuptime documents a public, tenant-scoped GET /v1/monitors endpoint authenticated with a management API key. Runtime endpoints not listed in the API docs are not public API. Pro and Max also include tenant-scoped MCP read and write tools for local or self-hosted workflows.
Monitoring
What can I monitor?
Pulse checks accept Heartbeats from jobs and services you run. Probe checks send outbound GET or HEAD requests to public HTTP or HTTPS URLs.
What are the minimum check intervals?
Minimum intervals follow your plan: Free is 5 minutes; Pro and Max are 1 minute.
Can I monitor internal services?
Yes, when they can call out: use a Pulse check so the job or service sends Heartbeats. Probe checks only reach public HTTP or HTTPS targets. Probe results enter as synthetic Heartbeats before tenant policy derives state and Incidents.
Plans & Billing
Is there a free plan?
Yes. Free includes 10 active monitors, a minimum interval of 5 minutes, 1 Probe region, 1 hosted status page, and 7 visible-history days. Free: no card required.
What counts as a monitor?
Each active Pulse or Probe monitor counts toward the plan limit. Paused and archived monitors do not count toward the active monitor limit.
Account & Security
How do you handle my data?
Monitoring reads and writes are tenant-scoped. Pulse tokens only authorize Heartbeats for one monitor, and MCP tokens carry a read or write scope for one workspace.
Still have a question?
Use the contact form to ask us.