← Leaderboard
8.2 L4

Fullstory

Native Assessed · Docs reviewed · Mar 23, 2026 Confidence 0.55 Last evaluated Mar 23, 2026

Verify before you commit

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

Use this page to sanity-check Fullstory 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 23, 2026

Freshness

Updated 2026-03-23T23:55:39.678893+00:00

Mar 23, 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.4
Access Readiness Score

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

7.9
Aggregate AN Score

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

8.2

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.

FullStory: Comprehensive Agent-Usability Assessment

Docs-backed

FullStory captures every user interaction on a web or mobile application — clicks, scrolls, form inputs, page navigation — and makes sessions replayable and queryable. For agents, the REST API enables: searching for sessions by user attributes or event criteria, looking up user profiles, exporting event data for analysis, and querying segments. The primary data capture is via JavaScript snippet (client-side); the REST API is the backend query surface. Used for diagnosing UX issues (rage clicks, form abandonment, error correlation) and understanding conversion funnels. Confidence is docs-derived.

Rhumb editorial team Mar 23, 2026

FullStory: API Design & Integration Surface

Docs-backed

REST API at api.fullstory.com/v2. Resources: sessions, users, segments, events, exports. GET /v2beta/users/{uid} retrieves a user's FullStory profile and session summary. GET /v2beta/sessions?users={uid} retrieves sessions for a user (with replay URL). POST /v2beta/segments/batch/get queries users in a segment. POST /v2beta/exports creates a data export job (event-level data to S3/GCS). GET /v2beta/exports/{id} polls export status. JavaScript capture snippet: window.FS.identify(uid, {attributes}) links app user IDs to FullStory sessions. REST API responses are JSON.

Rhumb editorial team Mar 23, 2026

FullStory: Auth & Access Control

Docs-backed

API key auth: Authorization: Basic {base64(api_key:)} header — API key as username, empty password. API keys from FullStory Settings → API Keys. Organization-level keys with full read access. HTTPS enforced. No OAuth2. JavaScript snippet uses an org-specific snippet key (public, for capture). Data export jobs access S3/GCS buckets you configure. Token rotation via FullStory settings.

Rhumb editorial team Mar 23, 2026

FullStory: Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies. 401 for invalid API key, 404 for missing user/session, 429 for rate limit. Data export jobs are async: poll /v2beta/exports/{id} until status is 'completed'. Export URLs are time-limited S3/GCS signed URLs. FullStory platform uptime at status.fullstory.com. Session replay data retention: 12 months by default (plan-dependent). Rate limits per plan tier — REST API rate limits more restrictive than capture-side.

Rhumb editorial team Mar 23, 2026

FullStory: Documentation & Developer Experience

Docs-backed

developer.fullstory.com provides the REST API reference, JavaScript snippet documentation, mobile SDK guides (iOS/Android), data export configuration, and segment query documentation. Documentation quality is good. Getting started requires a FullStory account (14-day trial; no meaningful free tier). API key creation documented. Data export requires S3 or GCS bucket configuration. Community support via FullStory Community and support portal.

Rhumb editorial team Mar 23, 2026

Use in your agent

mcp
get_score ("fullstory")
● Fullstory 8.2 L4 Native
exec: 8.4 · access: 7.9

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.2 / 10.0

Alternatives

No alternatives captured yet.