{ "data": { "a": { "slug": "optimizely", "name": "Optimizely Experimentation", "vendor": "Optimizely", "vendorUrl": "https://www.optimizely.com", "kind": "http-api", "category": "product-analytics", "summary": "Optimizely Experimentation is a hosted platform for A/B tests, feature flags and personalisation, covering Web Experimentation and Feature Experimentation. Agents reach it through a hosted MCP server with seven tools and through REST APIs.", "url": "https://www.anchorterminal.com/tools/optimizely", "markdownUrl": "https://www.anchorterminal.com/tools/optimizely.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/optimizely.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/optimizely.json", "repo": "https://github.com/optimizely/javascript-sdk", "license": "Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://exp.mcp.opal.optimizely.com/mcp", "packages": [ { "registry": "npm", "name": "@optimizely/optimizely-sdk" }, { "registry": "pypi", "name": "optimizely-sdk" } ], "auth": "mixed", "authNotes": "Sales-led. Access needs a subscription. The MCP server uses OAuth 2.0 through Opti ID with PKCE and dynamic client registration, and needs an account with Opal enabled and linked to a Feature Experimentation or Web Experimentation instance. The REST APIs take a personal access token, created under Profile then API Access, in the `Authorization: Bearer` header, or OAuth 2.0 for a registered application. Tokens and MCP sessions act with the user's role.", "pricing": "paid", "pricingNotes": "No price is published. The plans page says every plan is individually packaged and leads to a demo request. No free plan, trial or sandbox was found, so an agent cannot start without a contract. MCP use does not consume Opal credits (https://www.optimizely.com/plans/, checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the v2 Swagger spec or the plans page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": 460480, "pypiWeekly": 85924, "asOf": "2026-10-08" }, "docsUrl": "https://docs.optimizely.com/experimentation-strategy/docs/optimizely-experimentation-mcp-server-overview", "llmsTxt": "https://docs.optimizely.com/llms.txt", "openapi": "https://api.optimizely.com/v2/swagger.json", "capabilities": [ "analytics.experiments", "analytics.flags", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "openapi", "llms-txt", "closed-source", "sales-led", "enterprise", "webhooks", "status-page", "sla", "soc2", "iso27001", "bug-bounty" ], "lastRelease": "2026-09-18", "graded": true, "anchor": { "graded": true, "score": 62.6, "grade": "B", "agentReady": false, "rank": 383, "ranked": true, "rankOf": 842, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 78, "payments": 0, "reliability": 73, "schema": 74, "security": 66, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.", "bestFor": "An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.", "strengths": [ "Hosted MCP server with seven tools for querying, managing and implementing flags and experiments, released on 29 April 2026", "MCP sign-in is OAuth 2.0 with PKCE and dynamic client registration, and the server sees only what the user's account can see", "Public Swagger 2.0 spec for the Optimizely API with 93 operations, each with a description, plus llms.txt and a Markdown copy of every docs page", "Rate limits are published with numbers, 120 requests a minute on the Feature Experimentation API and 100 a minute on the Optimizely API", "Change history is readable through the REST API, and change approvals route flag changes to reviewers since 6 August 2026" ], "weaknesses": [ "No price is published. The plans page says every plan is individually packaged and leads to a demo request", "No free plan or trial was found, and the MCP server needs an account with Opal enabled", "No 429 response, `Retry-After` header or idempotency key was found in the spec or the pages read", "The REST OAuth flow has one scope, `all`, described as full access to the account", "The spec for the Feature Experimentation API at `/flags/v1` answers 401 without a token, and the MCP server is not in the official MCP registry" ], "agentNotes": [ "Connect to https://exp.mcp.opal.optimizely.com/mcp and complete OAuth in a browser. The session is time-limited, so expect to sign in again", "Call `exp_get_schemas` before `exp_execute_query`, and `exp_get_entity_templates` before `exp_manage_entity_lifecycle`, to learn the fields each entity needs", "Confirm the project and environment with the user before any create or update. Changes go to live Optimizely data", "Use the Visual Editor for Web Experimentation variation code. The MCP server does not write custom HTML, CSS or JavaScript", "Over REST, stay under 2 requests a second on `/flags/v1`, 100 a minute on `/v2` and 20 a minute on the results endpoints" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.6 } ], "editorialScores": { "ergonomics": 68, "maintenance": 78, "payments": 0, "reliability": 73, "schema": 74, "security": 66, "transparency": 63 }, "provenanceScore": 86 }, "connect": { "http": "curl -H \"Authorization: Bearer YOUR_ACCESS_TOKEN\" \"https://api.optimizely.com/v2/projects\"", "claudeCode": "claude mcp add --transport http optimizely-exp https://exp.mcp.opal.optimizely.com/mcp", "config": { "mcpServers": { "optimizely-exp": { "type": "http", "url": "https://exp.mcp.opal.optimizely.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.experiments", "tool": "https://letme.dev/optimizely" }, "area": "business", "provenance": { "legalEntity": "Optimizely North America Inc.", "domain": "optimizely.com", "domainRegistered": "2010-01-11", "endpointOnVendorDomain": true, "terms": "https://www.optimizely.com/legal/terms/", "privacy": "https://www.optimizely.com/legal/privacy-notice/", "statusPage": "https://status.optimizely.com", "changelog": "https://docs.optimizely.com/feature-experimentation/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Online Software Subscription Agreement 2025-11, published 10 November 2025, names Optimizely North America Inc as the contracting entity for customers in the USA, Canada, Mexico, Australia, New Zealand, APJ and the rest of the world, Optimizely AB for the Nordics, UK, Ireland, EU, UAE and Saudi Arabia, and Optimizely GmbH for DACH.", "The API, SDK and MCP terms, version 2026-08 published 26 August 2026, are a PDF linked from https://www.optimizely.com/legal/api-sdk-mcp-terms/ and form part of the subscription agreement.", "The privacy notice, V 2026-07 published 1 July 2026, says it does not apply to customer data, which Optimizely processes under the subscription agreement and the Data Processing Agreement (V 2026-01).", "The MCP server answers at exp.mcp.opal.optimizely.com and the REST APIs at api.optimizely.com.", "www.optimizely.com/.well-known/security.txt and www.optimizely.com/security.txt both return 404.", "RDAP for optimizely.com gives a registration date of 2010-01-11." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/optimizely.json", "live": { "slug": "optimizely", "probe": { "target": "https://exp.mcp.opal.optimizely.com/mcp", "method": "get", "lastAt": "2026-10-09T09:26:59.70297379Z", "lastOk": true, "lastStatus": 401, "lastMs": 221, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 145, "p95ms24h": 165, "samples24h": 151, "samples30d": 151, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 101, "ok": 101 } ] }, "vendorStatus": { "page": "https://status.optimizely.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:26.486937647Z" }, "updatedAt": "2026-10-09T09:26:59.70297379Z" } }, "answer": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing.", "b": { "slug": "woopra", "name": "Woopra", "vendor": "Woopra, Inc.", "vendorUrl": "https://www.woopra.com", "kind": "http-api", "category": "product-analytics", "summary": "Woopra is a hosted customer journey and product analytics service from Woopra, Inc., an Appier affiliate. Its HTTP tracking API records events and visitor properties, and its REST API returns saved reports, profiles and raw session logs.", "url": "https://www.anchorterminal.com/tools/woopra", "markdownUrl": "https://www.anchorterminal.com/tools/woopra.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/woopra.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/woopra.json", "repo": "https://github.com/Woopra/js-client-tracker", "license": "Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC", "transports": [ "http" ], "remoteUrl": "https://www.woopra.com/rest/3.10", "packages": [ { "registry": "npm", "name": "woopra" }, { "registry": "npm", "name": "@woopra/browser-tracker" } ], "auth": "mixed", "authNotes": "Self-serve. REST calls use HTTP Basic with an App ID and Secret Key that each user generates on the Access Keys tab of the members area. Tracking calls need only the project name unless the owner enables Secure Tracking, which adds a generated ID and secret sent by HTTP Basic. No OAuth, scopes or partner approval were found in the docs.", "pricing": "paid", "pricingNotes": "Pro starts at $999 a month for 5 million events, with a 30-day trial that an agent's owner can start without a contract. Overage fees apply past the event quota, at rates the pricing page does not state. Enterprise is quoted. Whether the trial signup asks for a card was not established (https://www.woopra.com/pricing, checked 2026-10-09).", "priceSummary": "$999 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs or on the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 415, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.woopra.com", "llmsTxt": "https://docs.woopra.com/llms.txt", "capabilities": [ "analytics.query", "analytics.events", "analytics.funnels" ], "tags": [ "hosted", "closed-source", "llms-txt", "basic-auth", "no-oauth", "free-trial", "status-page", "rate-limits", "export", "sales-led" ], "lastRelease": "2026-03-16", "graded": true, "anchor": { "graded": true, "score": 44.4, "grade": "E", "agentReady": false, "rank": 779, "ranked": true, "rankOf": 842, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 9, "payments": 30, "reliability": 80, "schema": 45, "security": 22, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.", "bestFor": "An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.", "strengths": [ "Rate limits are published per project at 300 calls a minute, 600 an hour and 3,000 a day, and limited calls return 429", "Report endpoints take `limit`, `offset`, a `snapshot` ID for consistent paging past 1,000 records, and `timeframe_from` and `timeframe_to` overrides", "status.woopra.com (Statuspage) lists no incidents for August, September or October 2026 across Data Processing, Data Collection and the front-end application", "`/logs/export` returns raw sessions as line-separated JSON, and `/logs/import` loads them in bulk and returns a batch ID to poll", "The terms of service (10 December 2025) name nine sub-processors with addresses and countries, and say the customer owns the tracking data" ], "weaknesses": [ "Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference", "`/track/ce` and `/track/identify` accept data with only the project name unless the owner turns on Secure Tracking", "No API changelog, deprecation policy or SLA was found. The terms promise commercially reasonable efforts on availability", "Server SDKs are old. The Node, Python, Java and Rails repositories were last committed to in 2017, and npm `woopra` is 1.0.2", "The terms of service forbid using any robot, spider, scraper or other automated means to access the Site, a term defined to include the Services", "Most REST operations document no response schema, and the `/profiles` page repeats the `/trends` description" ], "agentNotes": [ "Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id`", "Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/`", "Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule", "Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree", "Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later", "When reading `/logs/export`, delete the profile named in each `type: \"delete\"` line. The following lines log its data again under `new_id`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.4 } ], "editorialScores": { "ergonomics": 45, "maintenance": 9, "payments": 30, "reliability": 80, "schema": 45, "security": 22, "transparency": 45 }, "provenanceScore": 77 }, "connect": { "http": "curl \\\n--user \u003cApp Id\u003e:\u003cSecret Key\u003e \\\n\"https://www.woopra.com/rest/3.10/trends?project=mybusiness.com\u0026start_day=2017-4-12\u0026end_day=2017-5-19\u0026report_id=83mYcoe6jX\"" }, "letme": { "capability": "https://letme.dev/analytics.query", "tool": "https://letme.dev/woopra" }, "area": "business", "unitPrices": [ { "item": "Pro, 5 million events a month", "unit": "month", "usd": 999, "note": "starting price, overage fees apply" } ], "provenance": { "legalEntity": "Woopra, Inc.", "domain": "woopra.com", "domainRegistered": "2007-02-23", "endpointOnVendorDomain": true, "terms": "https://www.woopra.com/tos", "privacy": "https://www.woopra.com/privacy", "statusPage": "https://status.woopra.com", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-09", "notes": [ "The terms of service (last updated 10 December 2025) are a contract with Woopra, Inc., its subsidiaries and affiliated companies including Appier, and cover the website and the subscription services in one document. They give 600 California St, Fl 11, San Francisco, CA 94108 as the legal address.", "The privacy policy (last updated 1 August 2025) covers customers and site visitors and says it does not apply to end-user data that Woopra processes for customers. It names Appier Netherlands B.V. as EU representative. No public DPA was found, and the GDPR page says a copy is sent on request.", "The REST and tracking endpoints answer under https://www.woopra.com/rest and https://www.woopra.com/track, on the vendor's own domain. robots.txt on that host disallows both paths, and we sent no request to either.", "www.woopra.com/.well-known/security.txt timed out twice with no bytes received, so its presence is unknown.", "status.woopra.com is an Atlassian Statuspage site. Its address was not linked from the pages we read and was tried directly.", "No changelog for the API was found. docs.woopra.com/changelog returns 404, and the browser tracker's CHANGELOG.md stops at v5.3.0 of 15 September 2021.", "RDAP for woopra.com gives a registration date of 2007-02-23 and Spaceship, Inc. as registrar." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/woopra.json", "live": { "slug": "woopra", "probe": { "target": "https://www.woopra.com/rest/3.10", "method": "get", "lastAt": "2026-10-09T09:27:10.692276613Z", "lastOk": false, "lastStatus": 500, "lastMs": 74, "lastNote": "server error", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 0 } ], "outages": [ { "start": "2026-10-09T07:40:43.906309049Z", "end": "0001-01-01T00:00:00Z", "note": "HTTP 500 server error" } ] }, "vendorStatus": { "page": "https://status.woopra.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:39.197039798Z" }, "updatedAt": "2026-10-09T09:27:10.692276613Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Optimizely", "b": "Woopra, Inc.", "name": "Vendor" }, { "a": "https://exp.mcp.opal.optimizely.com/mcp", "b": "https://www.woopra.com/rest/3.10", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0", "b": "Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC", "name": "Licence" }, { "a": "7", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-18", "b": "2026-03-16", "name": "Last release" }, { "a": "no date given", "b": "2025-12-10", "name": "Terms last updated" }, { "a": "no date given", "b": "2025-08-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "460k npm/wk, 86k PyPI/wk", "b": "415 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, Optimizely Experimentation or Woopra?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Optimizely Experimentation and Woopra need an API key?" }, { "answer": "Yes. Optimizely Experimentation has a hosted endpoint at https://exp.mcp.opal.optimizely.com/mcp and Woopra at https://www.woopra.com/rest/3.10.", "question": "Can an agent call Optimizely Experimentation and Woopra without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 74 against 45", "Agent ergonomics, 68 against 45", "Security \u0026 auth, 66 against 22", "Maintenance \u0026 community, 78 against 9", "Transparency \u0026 trust, 75 against 61" ], "also": null, "goodFor": "An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.", "slug": "optimizely", "watchFor": "No price is published. The plans page says every plan is individually packaged and leads to a demo request" }, { "aheadOn": [ "Reliability, 80 against 73", "Payments \u0026 pricing, 30 against 0" ], "also": null, "goodFor": "An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.", "slug": "woopra", "watchFor": "Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference" } ], "job": { "capability": "analytics.query", "name": "Analytics query" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely.json", "title": "Amplitude vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-woopra.json", "title": "Amplitude vs Woopra", "url": "https://www.anchorterminal.com/compare/amplitude-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-optimizely.json", "title": "Countly vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/countly-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-woopra.json", "title": "Countly vs Woopra", "url": "https://www.anchorterminal.com/compare/countly-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-optimizely.json", "title": "Fullstory vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/fullstory-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-woopra.json", "title": "Fullstory vs Woopra", "url": "https://www.anchorterminal.com/compare/fullstory-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-woopra.json", "title": "GrowthBook vs Woopra", "url": "https://www.anchorterminal.com/compare/growthbook-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.json", "title": "Mixpanel vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-woopra.json", "title": "Mixpanel vs Woopra", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-pendo.json", "title": "Optimizely Experimentation vs Pendo", "url": "https://www.anchorterminal.com/compare/optimizely-vs-pendo" }, { "json": "https://www.anchorterminal.com/compare/pendo-vs-woopra.json", "title": "Pendo vs Woopra", "url": "https://www.anchorterminal.com/compare/pendo-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-woopra.json", "title": "PostHog vs Woopra", "url": "https://www.anchorterminal.com/compare/posthog-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/statsig-vs-woopra.json", "title": "Statsig vs Woopra", "url": "https://www.anchorterminal.com/compare/statsig-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/heap-vs-woopra.json", "title": "Heap vs Woopra", "url": "https://www.anchorterminal.com/compare/heap-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-optimizely.json", "title": "GrowthBook vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/growthbook-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-posthog.json", "title": "Optimizely Experimentation vs PostHog", "url": "https://www.anchorterminal.com/compare/optimizely-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.json", "title": "Optimizely Experimentation vs Statsig", "url": "https://www.anchorterminal.com/compare/optimizely-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.json", "title": "LaunchDarkly vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely" } ], "scores": [ { "by": 7, "edge": "woopra", "key": "reliability", "name": "Reliability", "optimizely": 73, "weight": 16, "woopra": 80 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 29, "edge": "optimizely", "key": "schema", "name": "Schema \u0026 documentation", "optimizely": 74, "weight": 13, "woopra": 45 }, { "by": 23, "edge": "optimizely", "key": "ergonomics", "name": "Agent ergonomics", "optimizely": 68, "weight": 13, "woopra": 45 }, { "by": 44, "edge": "optimizely", "key": "security", "name": "Security \u0026 auth", "optimizely": 66, "weight": 14, "woopra": 22 }, { "by": 30, "edge": "woopra", "key": "payments", "name": "Payments \u0026 pricing", "optimizely": 0, "weight": 10, "woopra": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 69, "edge": "optimizely", "key": "maintenance", "name": "Maintenance \u0026 community", "optimizely": 78, "weight": 7, "woopra": 9 }, { "by": 14, "edge": "optimizely", "key": "transparency", "name": "Transparency \u0026 trust", "optimizely": 75, "weight": 7, "woopra": 61 } ], "summary": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing. Both do analytics query.", "verdicts": { "optimizely": "Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.", "woopra": "Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/optimizely-vs-woopra", "json": "https://www.anchorterminal.com/compare/optimizely-vs-woopra.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/optimizely-vs-woopra.md", "slim": "https://www.anchorterminal.com/compare/optimizely-vs-woopra.min.md" }, "markdown": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing. Both do analytics query.\n\n- Optimizely Experimentation: grade B, 62.6/100, rank #383 of 842. Markdown https://www.anchorterminal.com/tools/optimizely.md · JSON https://www.anchorterminal.com/api/v1/tools/optimizely.json\n- Woopra: grade E, 44.4/100, rank #779 of 842. Markdown https://www.anchorterminal.com/tools/woopra.md · JSON https://www.anchorterminal.com/api/v1/tools/woopra.json\n\n## Which one, for what\n\n### Optimizely Experimentation (B)\n\nGood for: An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.\n\nAhead on:\n- Schema \u0026 documentation, 74 against 45\n- Agent ergonomics, 68 against 45\n- Security \u0026 auth, 66 against 22\n- Maintenance \u0026 community, 78 against 9\n- Transparency \u0026 trust, 75 against 61\n\nWatch for: No price is published. The plans page says every plan is individually packaged and leads to a demo request\n\n### Woopra (E)\n\nGood for: An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.\n\nAhead on:\n- Reliability, 80 against 73\n- Payments \u0026 pricing, 30 against 0\n\nWatch for: Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference\n\n\n## Score by category\n\n| Category | Weight | Optimizely Experimentation | Woopra | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 80 | Woopra +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 45 | Optimizely Experimentation +29 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 45 | Optimizely Experimentation +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 22 | Optimizely Experimentation +44 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 30 | Woopra +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 9 | Optimizely Experimentation +69 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 61 | Optimizely Experimentation +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.6 · B** | **44.4 · E** | |\n\n## Facts side by side\n\n| Fact | Optimizely Experimentation | Woopra |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Optimizely | Woopra, Inc. |\n| Hosted endpoint | `https://exp.mcp.opal.optimizely.com/mcp` | `https://www.woopra.com/rest/3.10` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0 | Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC |\n| Tools exposed | 7 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-18 | 2026-03-16 |\n| Terms last updated | no date given | 2025-12-10 |\n| Privacy policy last updated | no date given | 2025-08-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 460k npm/wk, 86k PyPI/wk | 415 npm/wk |\n\n## Verdicts\n\n**Optimizely Experimentation.** Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.\n\n**Woopra.** Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.\n\n## Before you call either\n\n### Optimizely Experimentation\n\n1. Connect to https://exp.mcp.opal.optimizely.com/mcp and complete OAuth in a browser. The session is time-limited, so expect to sign in again\n2. Call `exp_get_schemas` before `exp_execute_query`, and `exp_get_entity_templates` before `exp_manage_entity_lifecycle`, to learn the fields each entity needs\n3. Confirm the project and environment with the user before any create or update. Changes go to live Optimizely data\n4. Use the Visual Editor for Web Experimentation variation code. The MCP server does not write custom HTML, CSS or JavaScript\n5. Over REST, stay under 2 requests a second on `/flags/v1`, 100 a minute on `/v2` and 20 a minute on the results endpoints\n\n### Woopra\n\n1. Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id`\n2. Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/`\n3. Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule\n4. Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree\n5. Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later\n6. When reading `/logs/export`, delete the profile named in each `type: \"delete\"` line. The following lines log its data again under `new_id`\n\n## Questions\n\n### Which is better for AI agents, Optimizely Experimentation or Woopra?\n\nOptimizely Experimentation scores 62.6 (B) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing.\n\n### Do Optimizely Experimentation and Woopra need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Optimizely Experimentation and Woopra without installing anything?\n\nYes. Optimizely Experimentation has a hosted endpoint at https://exp.mcp.opal.optimizely.com/mcp and Woopra at https://www.woopra.com/rest/3.10.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/optimizely-vs-woopra.json, and with the fewest tokens: https://www.anchorterminal.com/compare/optimizely-vs-woopra.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"optimizely\", \"b\": \"woopra\"}`. From a terminal: `anchor compare optimizely woopra`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/optimizely.json and https://www.anchorterminal.com/api/v1/tools/woopra.json\n\n## Other comparisons with Optimizely Experimentation or Woopra\n\n- [Amplitude vs Optimizely Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-optimizely.md)\n- [Amplitude vs Woopra](https://www.anchorterminal.com/compare/amplitude-vs-woopra.md)\n- [Countly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/countly-vs-optimizely.md)\n- [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md)\n- [Fullstory vs Optimizely Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-optimizely.md)\n- [Fullstory vs Woopra](https://www.anchorterminal.com/compare/fullstory-vs-woopra.md)\n- [GrowthBook vs Woopra](https://www.anchorterminal.com/compare/growthbook-vs-woopra.md)\n- [Mixpanel vs Optimizely Experimentation](https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.md)\n- [Mixpanel vs Woopra](https://www.anchorterminal.com/compare/mixpanel-vs-woopra.md)\n- [Optimizely Experimentation vs Pendo](https://www.anchorterminal.com/compare/optimizely-vs-pendo.md)\n- [Pendo vs Woopra](https://www.anchorterminal.com/compare/pendo-vs-woopra.md)\n- [PostHog vs Woopra](https://www.anchorterminal.com/compare/posthog-vs-woopra.md)\n- [Statsig vs Woopra](https://www.anchorterminal.com/compare/statsig-vs-woopra.md)\n- [Heap vs Woopra](https://www.anchorterminal.com/compare/heap-vs-woopra.md)\n- [GrowthBook vs Optimizely Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-optimizely.md)\n- [Optimizely Experimentation vs PostHog](https://www.anchorterminal.com/compare/optimizely-vs-posthog.md)\n- [Optimizely Experimentation vs Statsig](https://www.anchorterminal.com/compare/optimizely-vs-statsig.md)\n- [LaunchDarkly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Optimizely Experimentation vs Woopra", "url": "" } ], "description": "Optimizely Experimentation scores 62.6 (B) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing. Both do analytics query. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Optimizely Experimentation B 62.6", "Woopra E 44.4", "scores" ], "h1": "Optimizely Experimentation vs Woopra", "image": "https://www.anchorterminal.com/assets/og/compare-optimizely-vs-woopra.png", "path": "/compare/optimizely-vs-woopra", "published": "2026-10-01", "section": "tools", "title": "Optimizely Experimentation vs Woopra for AI agents, B 62.6 vs E 44.4", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/optimizely-vs-woopra" }, "tokens": { "markdown": 2450, "slim": 730 }, "version": 1 }