Better Stack
Better Stack is a comprehensive infrastructure monitoring and observability platform that combines uptime monitoring, log management, incident management, status pages, and AI-powered site reliability tools. It helps teams identify and resolve website and server issues quickly by providing real-time alerting, detailed diagnostics, on-call scheduling, and public/private status pages.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Better Stack the way a machine reads it — 154 machine-readable artifacts across 6 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 — Better Stack scores 64.9/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Better Stack
Each block below is one kind of artifact we hold for Better Stack. 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 6
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.
Better Stack Escalation Policies API
Manage escalation policies and on-call schedules
Better Stack Heartbeats API
Manage heartbeat monitors for scheduled jobs and cron tasks
Better Stack Incidents API
Manage incidents and on-call alerting
Better Stack Monitors API
Manage uptime monitors for URLs, APIs, and services
Better Stack Status Pages API
Manage public and private status pages
Better Stack Team Members API
Manage team members and invitations
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).
Better Stack API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Better Stack Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Better Stack Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Uptime Monitoring
Monitor URLs, APIs, and services for availability with checks from multiple global regions every 30 seconds.
Heartbeat Monitoring
Monitor scheduled jobs, cron tasks, and background workers by pinging a unique URL on each run.
Incident Management
Automatically create and manage incidents when monitors detect downtime, with acknowledgement and resolution workflows.
On-Call Scheduling
Configure escalation policies with multi-step notification sequences via phone, SMS, email, and push.
Status Pages
Create public and private status pages with custom domains, branding, and real-time component status.
Log Management
Collect, search, and visualize logs across your entire infrastructure stack.
AI SRE
AI-powered root cause analysis that automatically investigates incidents and suggests resolutions.
Infrastructure Monitoring
OpenTelemetry-native monitoring with dashboards for metrics and infrastructure health.
Terraform Provider
Manage Better Stack resources as code using the official Terraform provider.
MCP Server
Model Context Protocol server for integrating Better Stack with AI tools and agents.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Better Stack Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Better Stack API Rules
SPECTRALBetter Stack API Rules
SPECTRALJSON Schema 38
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AvailabilityResponse
JSON SCHEMAHeartbeatAttributes
JSON SCHEMAHeartbeatCreateRequest
JSON SCHEMAHeartbeatListResponse
JSON SCHEMAHeartbeatObject
JSON SCHEMAHeartbeatSingleResponse
JSON SCHEMAHeartbeatUpdateRequest
JSON SCHEMAIncidentAttributes
JSON SCHEMAIncidentCreateRequest
JSON SCHEMAIncidentListResponse
JSON SCHEMAIncidentObject
JSON SCHEMAIncidentSingleResponse
JSON SCHEMAMonitorAttributes
JSON SCHEMAMonitorCreateRequest
JSON SCHEMAMonitorListResponse
JSON SCHEMAMonitorObject
JSON SCHEMAMonitorSingleResponse
JSON SCHEMAMonitorUpdateRequest
JSON SCHEMAPagination
JSON SCHEMAPolicyAttributes
JSON SCHEMAPolicyCreateRequest
JSON SCHEMAPolicyListResponse
JSON SCHEMAPolicyObject
JSON SCHEMAPolicySingleResponse
JSON SCHEMAPolicyStep
JSON SCHEMAPolicyUpdateRequest
JSON SCHEMAResponseTimesResponse
JSON SCHEMAStatusPageAttributes
JSON SCHEMAStatusPageCreateRequest
JSON SCHEMAStatusPageListResponse
JSON SCHEMAStatusPageObject
JSON SCHEMAStatusPageSingleResponse
JSON SCHEMAStatusPageUpdateRequest
JSON SCHEMATeamMemberAttributes
JSON SCHEMATeamMemberInviteRequest
JSON SCHEMATeamMemberListResponse
JSON SCHEMATeamMemberObject
JSON SCHEMATeamMemberSingleResponse
JSON SCHEMAScroll within the panel for all 38 ·
JSON Structure 38
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Better Stack Availability Response Structure
JSON STRUCTUREBetter Stack Heartbeat Attributes Structure
JSON STRUCTUREBetter Stack Heartbeat Create Request Structure
JSON STRUCTUREBetter Stack Heartbeat List Response Structure
JSON STRUCTUREBetter Stack Heartbeat Object Structure
JSON STRUCTUREBetter Stack Heartbeat Single Response Structure
JSON STRUCTUREBetter Stack Heartbeat Update Request Structure
JSON STRUCTUREBetter Stack Incident Attributes Structure
JSON STRUCTUREBetter Stack Incident Create Request Structure
JSON STRUCTUREBetter Stack Incident List Response Structure
JSON STRUCTUREBetter Stack Incident Object Structure
JSON STRUCTUREBetter Stack Incident Single Response Structure
JSON STRUCTUREBetter Stack Monitor Attributes Structure
JSON STRUCTUREBetter Stack Monitor Create Request Structure
JSON STRUCTUREBetter Stack Monitor List Response Structure
JSON STRUCTUREBetter Stack Monitor Object Structure
JSON STRUCTUREBetter Stack Monitor Single Response Structure
JSON STRUCTUREBetter Stack Monitor Update Request Structure
JSON STRUCTUREBetter Stack Pagination Structure
JSON STRUCTUREBetter Stack Policy Attributes Structure
JSON STRUCTUREBetter Stack Policy Create Request Structure
JSON STRUCTUREBetter Stack Policy List Response Structure
JSON STRUCTUREBetter Stack Policy Object Structure
JSON STRUCTUREBetter Stack Policy Single Response Structure
JSON STRUCTUREBetter Stack Policy Step Structure
JSON STRUCTUREBetter Stack Policy Update Request Structure
JSON STRUCTUREBetter Stack Response Times Response Structure
JSON STRUCTUREBetter Stack Status Page Attributes Structure
JSON STRUCTUREBetter Stack Status Page Create Request Structure
JSON STRUCTUREBetter Stack Status Page List Response Structure
JSON STRUCTUREBetter Stack Status Page Object Structure
JSON STRUCTUREBetter Stack Status Page Single Response Structure
JSON STRUCTUREBetter Stack Status Page Update Request Structure
JSON STRUCTUREBetter Stack Team Member Attributes Structure
JSON STRUCTUREBetter Stack Team Member Invite Request Structure
JSON STRUCTUREBetter Stack Team Member List Response Structure
JSON STRUCTUREBetter Stack Team Member Object Structure
JSON STRUCTUREBetter Stack Team Member Single Response Structure
JSON STRUCTUREScroll within the panel for all 38 ·
Examples 38
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 38 ·
Security Posture 4
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.
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.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Website Uptime Monitoring
Monitor public websites and APIs for availability and alert on-call engineers when they go down.
API Health Checking
Continuously verify that REST APIs return expected status codes and response times.
Cron Job Monitoring
Use heartbeats to ensure scheduled tasks run on time and alert when they fail to check in.
Incident Response Automation
Automate incident creation, on-call notifications, and resolution workflows to reduce MTTR.
Customer-Facing Status Communication
Publish status pages that automatically reflect the real-time health of monitored services.
Infrastructure Observability
Aggregate logs, metrics, and traces in a single platform for full-stack observability.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Slack
Receive incident alerts and status updates directly in Slack channels.
PagerDuty
Forward incidents to PagerDuty for existing on-call workflows.
Terraform
Manage monitors, status pages, and escalation policies as infrastructure as code.
OpenTelemetry
Send metrics, logs, and traces using OpenTelemetry-compatible exporters.
Sentry
Compatible with Sentry SDK for error tracking integration.
New Relic
Connect Better Stack monitoring data with New Relic dashboards.
Resources
Every other property we hold for Better Stack — 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 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/better-stack · machine-readable index on apis.io