Programmatic access
for incident operations.

API keys, service accounts, v1 endpoints, and MCP support for agents, integrations, and internal tooling.

Build on Runframe

Use governed machine access for custom tools, agent workflows, and operational automation.

API keys

Create controlled credentials for internal tools, scripts, integrations, and automation.

Service accounts

Use non-human principals for durable machine access instead of tying automation to a person.

v1 API

Build against API endpoints for incidents, postmortems, services, teams, on-call, and status pages.

MCP support

Give AI agents a safer interface on top of Runframe data and actions.

Audit context

Tie programmatic actions back to API keys, service accounts, request metadata, and organization context.

Rate limits

Protect public and internal endpoints with limits designed for operational safety.

How platform access works

1

Create controlled credentials

Use API keys or service accounts for machine access that is not tied to a human session.

2

Call incident operations APIs

Create incidents, update records, inspect services, check on-call state, or work with status pages.

3

Govern activity

Use audit context and rate limits to keep programmatic access visible and controlled.

Frequently asked questions

Connect Runframe to the systems your team owns.

Use APIs and service accounts for custom operational workflows.