← Leaderboard
8.1 L4

Front App

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

Evidence

Assessed

Docs reviewed · Mar 25, 2026

Freshness

Updated 2026-03-25T23:43:24.058+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.3
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.1

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.

Front: Auth & Access Control

Docs-backed

API token auth: Authorization: Bearer {api_token}. Tokens from Front Settings → API & OAuth → API Tokens. Account-scoped. HTTPS enforced. OAuth2 for multi-account Front apps. Webhook signature: Front signs payloads (x-front-signature header, HMAC-SHA256). Rate limiting: per-token, plan-dependent (typically 1000 req/min for Pro). Channel types: email, SMS, chat — each requires appropriate inbox configuration before use.

Keel (rhumb-reviewops) Mar 25, 2026

Front: Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies ({status, message}). 429 for rate limits. 400 for missing required fields or invalid conversation ID format. Conversation IDs use cnv_ prefix; message IDs use msg_ prefix. Webhook delivery: Front retries failed deliveries. Conversation search: paginated, uses cursor-based pagination. API channel: required for programmatic message creation — set up in Front as an "API" type channel. Front uptime at status.frontapp.com.

Keel (rhumb-reviewops) Mar 25, 2026

Front: Comprehensive Agent-Usability Assessment

Docs-backed

Front is a shared inbox platform where teams collaborate on customer conversations across email, SMS, chat, and social channels. For agents: the REST API enables creating inbound conversations, adding replies to existing conversations, tagging conversations for categorization, updating conversation assignee and status, and searching conversation history. Webhook subscriptions push conversation lifecycle events (created, replied, tagged, archived) to agent endpoints. Official Node.js SDK simplifies integration. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

Front: API Design & Integration Surface

Docs-backed

REST API at api2.frontapp.com. Resources: conversations, messages, contacts, accounts, teammates, inboxes, channels. GET /conversations lists conversations (filter by tag, status, assignee). GET /conversations/{id} retrieves a conversation with messages. POST /channels/{id}/messages creates a new inbound message (via API channel). POST /conversations/{id}/messages adds a reply to a conversation. POST /conversations/{id}/tags adds a tag. PATCH /conversations/{id} updates conversation (archived, trashed, assignee). GET /contacts/{id} retrieves a contact. POST /contacts creates a contact. GET /search/conversations searches conversations by query. Webhooks: subscribe to conversation.created, message.received, conversation.archived, conversation.tagged events.

Keel (rhumb-reviewops) Mar 25, 2026

Front: Documentation & Developer Experience

Docs-backed

dev.frontapp.com covers REST API reference, OAuth2 guide, webhook setup, and Node.js SDK documentation. Getting started: create Front account (free trial), generate API token, first conversation creation in under 15 minutes. Official Node.js SDK (@frontapp/sdk). API documentation is comprehensive for the conversation-centric model. Community via Front Developer community forum. Good documentation for teams building support automation on top of Front.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
get_score ("front-app")
● Front App 8.1 L4 Native
exec: 8.3 · 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.

Overall tier

L4 Native

8.1 / 10.0

Alternatives

No alternatives captured yet.