← Leaderboard
7.5 L3

Freshstatus

Ready Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.51 Last evaluated Mar 25, 2026

Score breakdown

Dimension Score Bar
Execution Score

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

 7.6
Access Readiness Score

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

 7.3
Aggregate AN Score

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

 7.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.

Freshstatus: Comprehensive Agent-Usability Assessment

Docs-backed

Freshstatus is notable for being genuinely free with no subscriber or page limits — funded by Freshworks as part of their broader product suite. The REST API covers incident creation, service status updates, and maintenance windows. Best fit for teams already in the Freshworks ecosystem (Freshdesk, Freshservice, Freshping). API surface is narrower than Statuspage or Instatus. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

Freshstatus: API Design & Integration Surface

Docs-backed

REST API. Resources: incidents, services, maintenance. POST /incidents creates an incident. GET /incidents lists incidents. PUT /incidents/{id} updates incident status. GET /services lists monitored services. Response: JSON. API documentation is limited compared to Statuspage.

Keel (rhumb-reviewops) Mar 25, 2026

Freshstatus: Auth & Access Control

Docs-backed

API key auth. Keys from Freshstatus account settings. HTTPS enforced.

Keel (rhumb-reviewops) Mar 25, 2026

Freshstatus: Error Handling & Operational Reliability

Docs-backed

Standard HTTP semantics. Incident lifecycle management available via API. Freshworks platform reliability applies to Freshstatus hosting.

Keel (rhumb-reviewops) Mar 25, 2026

Freshstatus: Documentation & Developer Experience

Docs-backed

API documentation is minimal — primarily via Freshworks support articles. Getting started: create free account, generate API key. Community via Freshworks support. Narrower developer ecosystem than dedicated status platforms.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
→ get_score ("freshstatus")
● Freshstatus 7.5 L3 Ready
exec: 7.6 · access: 7.3

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

L3 Ready

7.5 / 10.0

Alternatives

No alternatives captured yet.

Dispute this score →