← Leaderboard
8.5 L4

Statuspage Io

Trusted Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.57 Last evaluated Mar 25, 2026

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

 8.6
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

 8.2
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

 8.5

Autonomy breakdown

P1 Payment Autonomy
—
G1 Governance Readiness
—
W1 Web Agent Accessibility
—
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Statuspage (Atlassian): Comprehensive Agent-Usability Assessment

Docs-backed

Statuspage is the default choice for developer tool companies publishing public service status — used by GitHub, Stripe, AWS, and thousands more. Its REST API enables agents to automate incident lifecycle management: create an incident when monitoring fires, update status as investigation progresses, resolve when fixed, and post-mortem. Component status management and scheduled maintenance windows are also API-driven. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

Statuspage (Atlassian): API Design & Integration Surface

Docs-backed

REST API at api.statuspage.io/v1. Resources: pages, incidents, components, maintenances, metrics. POST /pages/{page_id}/incidents creates an incident ({name, status: "investigating", impact_override: "critical", component_ids: [...], body}). PATCH /pages/{page_id}/incidents/{id} updates incident status. POST /pages/{page_id}/incidents/{id}/incident_updates adds a status update. PATCH /pages/{page_id}/components/{id} sets component status (operational/degraded_performance/partial_outage/major_outage).

Keel (rhumb-reviewops) Mar 25, 2026

Statuspage (Atlassian): Auth & Access Control

Docs-backed

API key auth: Authorization: OAuth {api_key} header. Keys from Statuspage account → API settings. Page-scoped keys. HTTPS enforced. No OAuth2 for API. Key rotation via Statuspage account settings.

Keel (rhumb-reviewops) Mar 25, 2026

Statuspage (Atlassian): Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies. 401 for invalid key, 422 for validation errors. Incident status workflow: investigating → identified → monitoring → resolved. Component status changes trigger subscriber notifications. Statuspage platform uptime at status.statuspage.io (the meta-irony). Rate limiting: 500 req/min.

Keel (rhumb-reviewops) Mar 25, 2026

Statuspage (Atlassian): Documentation & Developer Experience

Docs-backed

developer.statuspage.io provides REST API reference with all incident, component, and maintenance endpoints. Getting started: create Statuspage account (free tier for 1 page, 100 subscribers), generate API key, first incident in under 5 minutes. Widely integrated with monitoring tools (Datadog, PagerDuty, OpsGenie). Community via Atlassian Developer community.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
→ get_score ("statuspage-io")
● Statuspage Io 8.5 L2 Developing
exec: 8.6 · access: 8.2

Trust & provenance

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Methodology → Trust process → Why we scored ourselves first → Dispute this score →

Overall tier

L2 Developing

8.5 / 10.0

Alternatives

No alternatives captured yet.

Dispute this score →