For Agents
Open, acknowledge, escalate, and resolve Runframe incidents, page responders over Slack or email, look up who is on call, and write postmortems.
Use for: Open a SEV1 incident for the payments service, Find out who is on call for the platform team right now, Page the database owner about this incident over Slack, List all open SEV0 and SEV1 incidents
Not supported: Does not collect metrics, ingest logs, or edit on-call schedules. Use for managing incidents, paging responders, and writing postmortems only.
The Runframe V1 API runs incident response for engineering teams: it opens incidents against services, moves them through acknowledgement, status transitions, and escalation, and records postmortems once they are over. Responders can be paged by email address over Slack or email, the current on-call person for a team can be looked up, and escalation policies are readable per severity. A set of public status routes returns the status page summary, components, incident history, and maintenance windows without a key.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Runframe V1 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.
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%2Frunframe.io%2Frunframe" | shStep 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%2Frunframe.io%2Frunframe" | 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.
What an agent can do with Runframe V1 API.
Open an incident with a title, service_ids, and a severity from SEV0 to SEV4, with an Idempotency-Key header for replay-safe creates
Acknowledge an incident, transition its status with a comment, or escalate it to the next escalation policy level
Page a specific person by email over Slack, email, or both with a short message
Look up the current on-call responder for a team and the escalation policy for a severity
Add timeline comments to an incident and read its full timeline
Write a postmortem for an incident with root_cause, resolution, action_items, and five_whys
Read the public status summary, components, incident history, and maintenance windows without a key
Patterns agents use Runframe V1 API for, with concrete tasks.
★ AI on-call assistant triaging an alert
An AI on-call assistant receiving an alert needs to open an incident and get a human looking at it. Through Jentic the agent searches for 'open an incident', loads the createIncident operation with its input schema, and calls it with the Runframe key injected at execution time. It then looks up the team's current on-call responder and pages them over Slack with a summary of the alert.
Call GET /api/v1/services with search payments to get the service id, POST /api/v1/incidents with title, severity SEV1, and service_ids, then GET /api/v1/on-call/current with team_name platform and POST /api/v1/incidents/{id}/page with that person's email and channels slack
Driving an incident to resolution
During an outage the incident record should track what responders do. Runframe separates acknowledgement from status changes: POST /api/v1/incidents/{id}/acknowledge stamps the acknowledgement time and resolves the acknowledge SLA, while POST /api/v1/incidents/{id}/status handles investigate, monitor, resolve, and close with a comment of up to 500 characters. Timeline events and escalation to the next policy level have their own routes.
Call POST /api/v1/incidents/{id}/acknowledge, add a timeline comment with POST /api/v1/incidents/{id}/events, then POST /api/v1/incidents/{id}/status with the resolved status and a comment
Postmortem drafting
After resolution the team writes up what happened. POST /api/v1/postmortems takes an incident_number plus fields such as summary, root_cause, resolution, impact, timeline, action_items, contributing_factors, five_whys, and executive_summary. GET /api/v1/postmortems returns the postmortem for an incident_number so it can be reviewed or extended.
Read GET /api/v1/incidents/{id} for the timeline, then POST /api/v1/postmortems with the incident_number, summary, root_cause, resolution, and three action_items
Public status page monitoring
Customers and dependent systems check whether Runframe-hosted status pages show trouble. The public status routes return the overall summary, per-component status, incident history with a status filter and updates_limit, unresolved incidents, and maintenance windows. They need no key, so a monitor can poll them freely.
Call GET /api/v1/status/incidents/unresolved and GET /api/v1/status/maintenance and report any active incident or upcoming maintenance
23 endpoints — the runframe v1 api runs incident response for engineering teams: it opens incidents against services, moves them through acknowledgement, status transitions, and escalation, and records postmortems once they are over.
METHOD
PATH
DESCRIPTION
/api/v1/incidents
Create an incident
/api/v1/incidents
List incidents with filters
/api/v1/incidents/{id}/acknowledge
Acknowledge an incident
/api/v1/incidents/{id}/status
Transition incident status
/api/v1/incidents/{id}/page
Page a person about an incident
/api/v1/on-call/current
Get the current on-call responder
/api/v1/postmortems
Create a postmortem
/api/v1/status
Get public status summary
/api/v1/incidents
Create an incident
/api/v1/incidents
List incidents with filters
/api/v1/incidents/{id}/acknowledge
Acknowledge an incident
/api/v1/incidents/{id}/status
Transition incident status
/api/v1/incidents/{id}/page
Page a person about an incident
/api/v1/on-call/current
Get the current on-call responder
/api/v1/postmortems
Create a postmortem
/api/v1/status
Get public status summary
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Runframe by hand means attaching the rf_ bearer key, resolving service keys and user emails before you can open or assign an incident, and keeping acknowledgement, status transitions, and field edits on their separate routes. Through Jentic you install once, import Runframe from the API Directory, store the key once, and your agent calls it.
Permission scoping
Runframe puts the incident id in the URL path for every action (/api/v1/incidents/{id}/acknowledge, /status, /page, /escalate), so a rule can bound your agent to the incident actions you pick. You choose the operations it may call, so ones that wake people up, like paging or escalation, are not included unless you add them.
Credential isolation
Your Runframe 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 'open an incident' or 'who is on call', and Jentic returns the matching Runframe operation with its input schema, including the severity enum and required service_ids, so the agent calls it correctly.
Alternatives and complements available in the Jentic catalogue.
Specific to using Runframe V1 API through Jentic.
What authentication does the Runframe V1 API use?
Per its OpenAPI spec, the Runframe V1 API uses HTTP bearer authentication with an API key in the rf_ format, or a session JWT, sent in the Authorization header. The incident, on-call, postmortem, and directory routes require it, while the five public status routes under /api/v1/status are open. GET /api/v1/auth/verify confirms a key and returns its scopes.
How do I resolve an incident with the Runframe API?
Use POST /api/v1/incidents/{id}/status with the target status and an optional comment explaining the change. PATCH on the incident only edits fields such as title, severity, or assigned_to, and acknowledgement has its own POST /api/v1/incidents/{id}/acknowledge route.
What are the rate limits for the Runframe V1 API?
The OpenAPI spec does not specify rate limits. Check the Runframe documentation at https://runframe.io for current limits; list routes such as GET /api/v1/incidents page at up to 100 results per request.
Is there a Runframe MCP server?
You do not need an MCP server to give your agent Runframe. Jentic connects it directly from the API Directory: import it, store your rf_ API key once, and your agent calls the incident, paging, and postmortem operations on demand without extra tool definitions in its context.
How do I page the on-call engineer through Jentic?
Search Jentic for 'who is on call', run GET /api/v1/on-call/current with the team_name, then search for 'page someone about an incident' and execute POST /api/v1/incidents/{id}/page with that person's email and channels such as slack. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Runframe API?
Yes. For a triage agent, write a rule that allows creating incidents, adding timeline events, and reading on-call, so it can open and annotate incidents but cannot page people, escalate, or resolve them. Add the page route when you want it to notify responders, and every call it makes is logged.
GET STARTED