Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Keep website screenshot

Keep

Keep is an open-source AIOps and alert management platform that unifies alerts from any monitoring tool, providing deduplication, correlation, enrichment, and workflow automation across observability, incident response, ticketing, and CMDB systems. The Keep REST API enables programmatic access to alerts, incidents, workflows, providers, and integrations with FastAPI-generated OpenAPI documentation.

agent aware

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Keep the way a machine reads it — 32 machine-readable artifacts across 27 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Keep scores 27.7/100 (emerging), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 27.7/100 · emerging
Contract Quality 12.7 / 25
Developer Ergonomics 4.3 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 41/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Keep

Each block below is one kind of artifact we hold for Keep. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 27

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Keep actions API

The actions API from Keep — 2 operation(s) for actions.

Keep alerts API

The alerts API from Keep — 24 operation(s) for alerts.

Keep auth API

The auth API from Keep — 8 operation(s) for auth.

Keep dashboard API

The dashboard API from Keep — 3 operation(s) for dashboard.

Keep deduplications API

The deduplications API from Keep — 3 operation(s) for deduplications.

Keep enrichment API

The enrichment API from Keep — 4 operation(s) for enrichment.

Keep extraction API

The extraction API from Keep — 2 operation(s) for extraction.

Keep groups API

The groups API from Keep — 2 operation(s) for groups.

Keep healthcheck API

The healthcheck API from Keep — 1 operation(s) for healthcheck.

Keep incidents API

The incidents API from Keep — 13 operation(s) for incidents.

Keep Keep API API

The Keep API API from Keep — 1 operation(s) for keep api.

Keep maintenance API

The maintenance API from Keep — 2 operation(s) for maintenance.

Keep mapping API

The mapping API from Keep — 2 operation(s) for mapping.

Keep metrics API

The metrics API from Keep — 1 operation(s) for metrics.

Keep permissions API

The permissions API from Keep — 2 operation(s) for permissions.

Keep preset API

The preset API from Keep — 5 operation(s) for preset.

Keep providers API

The providers API from Keep — 16 operation(s) for providers.

Keep pusher API

The pusher API from Keep — 1 operation(s) for pusher.

Keep roles API

The roles API from Keep — 2 operation(s) for roles.

Keep rules API

The rules API from Keep — 2 operation(s) for rules.

Keep settings API

The settings API from Keep — 7 operation(s) for settings.

Keep status API

The status API from Keep — 1 operation(s) for status.

Keep tags API

The tags API from Keep — 1 operation(s) for tags.

Keep topology API

The topology API from Keep — 3 operation(s) for topology.

Keep users API

The users API from Keep — 2 operation(s) for users.

Keep whoami API

The whoami API from Keep — 1 operation(s) for whoami.

Keep workflows API

The workflows API from Keep — 11 operation(s) for workflows.

Scroll within the panel for all 27 ·

Open Collections 1

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Keep API

OPEN COLLECTION

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Keep Authentication

apiKey/http/oauth2 · 3 schemes

SECURITY

Keep Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Keep Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Keep Agentic Access

136 operations · 81 acting · 5 human-in-the-loop

136 operations · 81 acting

AGENTIC

Resources

Every other property we hold for Keep — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/keep · machine-readable index on apis.io