Connect Instatus to your AI agent
Instatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.
We set up the connection using your own Instatus account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.
What your agent can do in Instatus
Each one is a real action the agent can take on its own, the same things a person clicking around Instatus could do. Read-only by default; write actions are confirmed against your policy.
- Add Incident Update Post a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when notify is true.
- Add Maintenance Update Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and affected-component subscribers when no…
- Create Component Create a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible.
- Create Incident Create an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and affected-component subscribers.
- Create Maintenance Schedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notify_start, notify_end, and notify_early schedule la…
- Get Component Get the current health and configuration of one component on an Instatus status page.
- Get Incident Get one Instatus incident with its affected components and update history.
- Get Maintenance Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.
- List Components List components and their current health for one Instatus status page, including child components where present. Pass the response's next_cursor back unchanged to fetch another page.
- List Incidents List incidents for an Instatus status page, optionally including or excluding lifecycle statuses.
- List Maintenances List scheduled and historical maintenances for an Instatus status page.
- List Status Pages List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.
- Update Component Change a component's health or presentation on an Instatus status page.
- Update Incident Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-component subscribers.
- Update Maintenance Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUS_GET_MAINTENANCE first and preserve unchanged values; setting noti…
How we connect it
- 1
Connect your account
You create a key in Instatus, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.
- 2
Set the guardrails
Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.
- 3
We keep it running
Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.
FAQ
Instatus questions, answered.
Ready to put Instatus to work?
Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.
All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Instatus.