Verify before you commit
Use this page to sanity-check Vwo 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 22, 2026
Freshness
Updated 2026-03-22T21:42:42.683789+00:00
Mar 22, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 7.4 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 7.0 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 7.3 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
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.
API token auth via token query parameter or Authorization header (both supported). Account-level API tokens with full access scope. No per-campaign key scoping. VWO SDK initialization uses a different SDK key (separate from the API token). HTTPS enforced. Rate limits on the REST API for high-volume reporting queries.
VWO (Visual Website Optimizer) is a comprehensive experimentation platform covering A/B testing, multivariate testing, split URL testing, and feature rollouts with targeting. Its API and server-side SDKs allow agent-friendly variation assignment without browser execution. For agents, key use cases: programmatic experiment management (create, activate, pause campaigns), reading current variation assignments for server-side experimentation, and retrieving campaign results for reporting automation. The feature rollout SDK allows gradual feature enablement with user attribute targeting. Confidence is docs-derived.
REST API at app.vwo.com/api/v2. Resources: campaigns, goals, reports, segments. Campaign management: list, get, activate/pause. VWO server-side SDKs (Python, Node.js, Go, Java, PHP, Ruby) handle variation assignment with local bucketing (no API call per user request). API responses are JSON with campaign objects including variation percentages and targeting rules. Results API provides aggregated metric data for experiment reporting.
Standard HTTP status codes with JSON error responses including errorCode and message fields. SDK-level errors (invalid SDK key, user not bucketed) return structured objects in language-native form. Rate limits documented; batch reporting API available for high-volume analytics. VWO's infrastructure is SaaS with uptime SLA for enterprise plans. Experiment decisions are cached locally in the SDK — network failures don't block variation assignment.
developers.vwo.com/reference provides REST API docs and SDK guides for all supported languages. API reference covers all endpoints with request/response examples. SDK guides cover initialization, variation assignment, goal tracking, and feature flags. Getting started requires a VWO account and SDK key. Documentation quality is good; actively maintained alongside VWO's product updates.
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
7.3 / 10.0
No alternatives captured yet.