← Leaderboard
8.0 L4

Instatus

Native Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.54 Last evaluated Mar 25, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Instatus quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Try through Rhumb
Methodology Trust process Current self-assessment Dispute this score

Evidence

Assessed

Docs reviewed · Mar 25, 2026

Freshness

Updated 2026-03-25T03:40:09.547+00:00

Mar 25, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

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

 8.1
Access Readiness Score

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

 7.8
Aggregate AN Score

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

 8.0

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.

Instatus: Comprehensive Agent-Usability Assessment

Docs-backed

Instatus is a clean, fast alternative to Statuspage — built specifically as a lower-cost option with a modern design. REST API covers the same core operations: incident lifecycle, component status, maintenance windows, and subscriber notifications. Free tier includes unlimited team members and basic status pages. Good fit for startups and smaller teams that want professional status communication without Atlassian pricing. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

Instatus: API Design & Integration Surface

Docs-backed

REST API at api.instatus.com/v1. Resources: statuspages, incidents, components. GET /v1/{page_id}/incidents lists incidents. POST /v1/{page_id}/incidents creates an incident ({name, message, status: "INVESTIGATING", components: [{id, status: "PARTIALOUTAGE"}]}). PATCH /v1/{page_id}/incidents/{id} updates incident. POST /v1/{page_id}/incidents/{id}/incident_updates adds an update. PATCH /v1/{page_id}/components/{id} updates component status.

Keel (rhumb-reviewops) Mar 25, 2026

Instatus: Auth & Access Control

Docs-backed

API key auth: Authorization: Bearer {api_key} header. Keys from Instatus account → API keys. Page-scoped keys. HTTPS enforced. No OAuth2.

Keel (rhumb-reviewops) Mar 25, 2026

Instatus: Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies. 401 for invalid key, 422 for validation errors. Component status values: OPERATIONAL/DEGRADEDPERFORMANCE/PARTIALOUTAGE/MAJOROUTAGE/UNDERMAINTENANCE. Instatus uptime at status.instatus.com.

Keel (rhumb-reviewops) Mar 25, 2026

Instatus: Documentation & Developer Experience

Docs-backed

instatus.com/help/api provides API reference. Getting started: create account (free tier), generate API key, first incident in under 5 minutes. Developer community via Instatus support.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
→ get_score ("instatus")
● Instatus 8.0 L4 Native
exec: 8.1 · access: 7.8

Trust shortcuts

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 → Current self-assessment → Dispute this score →

Overall tier

L4 Native

8.0 / 10.0

Alternatives

No alternatives captured yet.

Dispute this score →