Connect Instatus to Your AI Agent

Give the assistant the affected components and incident message to create or update a status-page record.

Try a Instatus Task

Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.

oo Skill Instatus

Summarize Active Incidents

Inspect affected components and incident records to describe the page’s current situation.

/oo Instatus: On Instatus page [ID], list unresolved incidents and components, retrieve the relevant incidents, and summarize their status.

Publish an Incident Notice

Create an incident with the affected components, initial message, and chosen publication settings.

/oo Instatus: Create and publish an investigating incident on page [ID] called [name], affecting components [IDs] with statuses [statuses]. Use this message: [text]. Do not notify subscribers.

Start Working with Instatus

Install OOMOL

Set up oo CLI and the oo Skill in your agent.
Install OOMOL →
Connect Instatus

Connect an Instatus API key from developer settings.
Connect Instatus →
Give Your Agent a Task

Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →

Choose Your Agent

Codex Claude Code Cursor Hermes

An Instatus API key with access to the relevant status page.
For incident writes, specify whether to notify subscribers; incident creation also supports choosing whether to publish.

Instatus Tools

Instatus provides status pages with components and incident histories. This connection reads page records and manages components, incidents, and their individual updates.

Pages and Components

Find status pages and read, create, update, or delete their components.

Incidents and Updates

Read and manage incident records and the individual messages and statuses in their history.

15 tools

List Status Pages

List Instatus status pages in the authenticated account.

instatus.list_status_pages

List Components

List components on an Instatus status page.

instatus.list_components

Get Component

Get one Instatus component by ID.

instatus.get_component

Create Component

Create one component on an Instatus status page.

instatus.create_component

Update Component

Update one Instatus component by ID.

instatus.update_component

Delete Component

Delete one Instatus component by ID.

instatus.delete_component

List Incidents

List incidents on an Instatus status page.

instatus.list_incidents

Get Incident

Get one Instatus incident by ID.

instatus.get_incident

Create Incident

Create one incident on an Instatus status page.

instatus.create_incident

Update Incident

Update one Instatus incident by ID.

instatus.update_incident

Delete Incident

Delete one Instatus incident by ID.

instatus.delete_incident

Get Incident Update

Get one Instatus incident update by ID.

instatus.get_incident_update

Create Incident Update

Create one update on an Instatus incident.

instatus.create_incident_update

Update Incident Update

Update one Instatus incident update by ID.

instatus.update_incident_update

Delete Incident Update

Delete one Instatus incident update by ID.

instatus.delete_incident_update

Frequently Asked Questions

Can I create a notice without publishing it?

Yes. Incident creation has a separate publication choice. State that the incident should remain unpublished.

Can I add an update without notifying subscribers?

Yes. Specify no subscriber notification when creating or editing the update.

Does this connection check whether my services are running?

It reads and changes Instatus records. It does not perform availability checks against your services.