{ "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": 330, "ranked": true, "rankOf": 722, "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-09T01:12:53.419230727Z", "lastOk": true, "lastStatus": 401, "lastMs": 155, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 145, "p95ms24h": 196, "samples24h": 63, "samples30d": 63, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 13, "ok": 13 } ] }, "vendorStatus": { "page": "https://status.optimizely.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T01:07:46.033408603Z" }, "updatedAt": "2026-10-09T01:12:53.419230727Z" } }, "answer": "Statsig scores 72.3 (BB) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 6 of 7 scored categories.", "b": { "slug": "statsig", "name": "Statsig", "vendor": "Amplitude, Inc.", "vendorUrl": "https://www.statsig.com", "kind": "http-api", "category": "product-analytics", "summary": "Statsig is a hosted platform for feature flags, experiments and product analytics, run by Amplitude, Inc. since May 2026. Agents reach it through the Console API, which has a public OpenAPI spec, and an official hosted MCP server.", "url": "https://www.anchorterminal.com/tools/statsig", "markdownUrl": "https://www.anchorterminal.com/tools/statsig.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/statsig.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/statsig.json", "repo": "https://github.com/statsig-io/statsig-server-core", "license": "Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.statsig.com/v3/mcp", "packages": [ { "registry": "npm", "name": "@statsig/statsig-node-core" }, { "registry": "npm", "name": "@statsig/js-client" }, { "registry": "pypi", "name": "statsig-python-core" }, { "registry": "npm", "name": "@statsig/siggy" } ], "auth": "mixed", "authNotes": "Self-serve. The Console API takes a Console API key in the `STATSIG-API-KEY` header, created in project settings as read-only or read and write. The MCP server uses OAuth with PKCE and dynamic client registration, which issues a personal Console API key carrying the user's role, or takes a Console key in the `statsig-api-key` header. OAuth needs the organisation owner to allow personal keys for the role. Flag evaluation and event logging take a client or server SDK key.", "pricing": "freemium", "pricingNotes": "Free Developer plan with no card, covering 2 million events and 50,000 session replays a month. Pro is $150 a month with 5 million events, then $0.05 per 1,000 events. Enterprise is by contract. Flag and config checks are unlimited on every plan, and API and MCP calls are not billed. An agent can start on the free plan without a contract (https://www.statsig.com/pricing, checked 2026-10-08).", "priceSummary": "$150 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": null, "npmWeekly": 4157066, "pypiWeekly": 893619, "asOf": "2026-10-08" }, "docsUrl": "https://docs.statsig.com/console-api/introduction", "llmsTxt": "https://docs.statsig.com/llms.txt", "openapi": "https://api.statsig.com/openapi/20240601.json", "registryName": "com.statsig/statsig-mcp-server", "capabilities": [ "analytics.experiments", "analytics.flags", "analytics.query", "analytics.events" ], "tags": [ "official", "hosted", "mcp", "oauth", "openapi", "llms-txt", "free-tier", "no-card", "status-page", "soc2", "eu-region" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 72.3, "grade": "BB", "agentReady": true, "rank": 94, "ranked": true, "rankOf": 722, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 81, "payments": 40, "reliability": 79, "schema": 82, "security": 74, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.", "bestFor": "An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.", "strengths": [ "Hosted MCP server with 18 default tools and a discovery layer that replaced 93 tools on the V1 server", "MCP access set per project and per role as no access, read only or read and write, with a confirmation on updates", "Public OpenAPI 3.0 spec with 325 operations, plus llms.txt and a Markdown copy of every docs page", "Free Developer plan with no card and 2 million events a month, and a public overage price of $0.05 per 1,000 events on Pro", "Audit logs kept indefinitely and readable through the API and the `log_read` MCP tool" ], "weaknesses": [ "Console API errors carry only `status` and `message`, and the spec documents no 429 response", "No idempotency keys were found, and most MCP update tools replace the whole resource", "The project Console API key reads and writes everything in a project unless created read-only", "The privacy notice is Amplitude's, last updated 31 August 2026, and doesn't name Statsig", "The 99.95 per cent SLA needs Enterprise premium support and covers the Console user interface" ], "agentNotes": [ "Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools", "Call `get_context` first to learn the project, your permissions and the review settings", "Read the resource before `gate_update`, `experiment_update` or `dynamic_config_update`. They replace the whole resource, so resend every field you want kept", "Use `discover_tools` for partial edits, and fetch a fresh `operationHandle` when one expires", "On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.3 } ], "editorialScores": { "ergonomics": 71, "maintenance": 81, "payments": 40, "reliability": 79, "schema": 82, "security": 74, "transparency": 64 }, "provenanceScore": 85 }, "connect": { "claudeCode": "claude mcp add --transport http statsig https://api.statsig.com/v3/mcp", "config": { "mcpServers": { "statsig": { "url": "https://api.statsig.com/v3/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.experiments", "tool": "https://letme.dev/statsig" }, "area": "business", "unitPrices": [ { "item": "Pro plan", "unit": "month", "usd": 150, "note": "5 million events and 100,000 session replays included" }, { "item": "Metered event", "unit": "tx", "usd": 0.00005, "note": "Pro plan, above 5 million a month" } ], "provenance": { "legalEntity": "Amplitude, Inc.", "domain": "statsig.com", "domainRegistered": "1998-12-29", "endpointOnVendorDomain": true, "terms": "https://www.statsig.com/terms", "privacy": "https://amplitude.com/privacy", "statusPage": "https://status.statsig.com", "changelog": "https://www.statsig.com/updates", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The self-service subscription agreement at statsig.com/terms, effective 4 August 2025, names Amplitude, Inc. as the party called Statsig. The enterprise terms (effective 18 February 2026) and the DPA do the same.", "statsig.com/privacy redirects to amplitude.com/privacy, a notice last updated 31 August 2026 that covers Amplitude, Inc. and its affiliates and doesn't name Statsig. It says it does not apply to end-user data that customers send to the product.", "statsig.com/legal/subprocessors redirects to amplitude.com/subprocessor-list, last updated 13 May 2026, which marks the providers used for Statsig-branded services.", "The MCP server answers at api.statsig.com. The Console API answers at statsigapi.net, a second domain the vendor's docs name.", "www.statsig.com/.well-known/security.txt returns 404.", "RDAP for statsig.com gives a registration date of 1998-12-29." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/statsig.json", "live": { "slug": "statsig", "probe": { "target": "https://api.statsig.com/v3/mcp", "method": "get", "lastAt": "2026-10-09T01:12:58.132186235Z", "lastOk": true, "lastStatus": 401, "lastMs": 46, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 42, "p95ms24h": 70, "samples24h": 83, "samples30d": 83, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 70 }, { "date": "2026-10-09", "probes": 13, "ok": 13 } ] }, "vendorStatus": { "page": "https://status.statsig.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T01:07:52.798039484Z" }, "pages": [ { "url": "https://www.statsig.com/updates", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:30:46.247718302Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3bba7a8e7236" }, { "url": "https://www.statsig.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:30:41.954344318Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d0e8593f7c0e" }, { "url": "https://www.statsig.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:30:44.722171717Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "dc465dc5a41d" } ], "updatedAt": "2026-10-09T01:12:58.132186235Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Optimizely", "b": "Amplitude, Inc.", "name": "Vendor" }, { "a": "https://exp.mcp.opal.optimizely.com/mcp", "b": "https://api.statsig.com/v3/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "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 hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC", "name": "Licence" }, { "a": "7", "b": "18", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.statsig/statsig-mcp-server", "name": "MCP registry" }, { "a": "2026-09-18", "b": "2026-09-28", "name": "Last release" }, { "a": "no date given", "b": "2025-08-04", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-08-31", "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": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "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": "4.2M npm/wk, 894k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Statsig scores 72.3 (BB) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Optimizely Experimentation or Statsig?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Optimizely Experimentation and Statsig need an API key?" }, { "answer": "Yes. Optimizely Experimentation has a hosted endpoint at https://exp.mcp.opal.optimizely.com/mcp and Statsig at https://api.statsig.com/v3/mcp.", "question": "Can an agent call Optimizely Experimentation and Statsig without installing anything?" } ], "goodFor": [ { "aheadOn": null, "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, 79 against 73", "Schema \u0026 documentation, 82 against 74", "Security \u0026 auth, 74 against 66", "Payments \u0026 pricing, 40 against 0" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "goodFor": "An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.", "slug": "statsig", "watchFor": "Console API errors carry only `status` and `message`, and the spec documents no 429 response" } ], "job": { "capability": "analytics.experiments", "name": "Analytics experiments" }, "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-statsig.json", "title": "Amplitude vs Statsig", "url": "https://www.anchorterminal.com/compare/amplitude-vs-statsig" }, { "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-statsig.json", "title": "Fullstory vs Statsig", "url": "https://www.anchorterminal.com/compare/fullstory-vs-statsig" }, { "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-statsig.json", "title": "Mixpanel vs Statsig", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-statsig" }, { "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-statsig.json", "title": "Pendo vs Statsig", "url": "https://www.anchorterminal.com/compare/pendo-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-statsig.json", "title": "PostHog vs Statsig", "url": "https://www.anchorterminal.com/compare/posthog-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/heap-vs-statsig.json", "title": "Heap vs Statsig", "url": "https://www.anchorterminal.com/compare/heap-vs-statsig" }, { "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/growthbook-vs-statsig.json", "title": "GrowthBook vs Statsig", "url": "https://www.anchorterminal.com/compare/growthbook-vs-statsig" }, { "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/launchdarkly-vs-optimizely.json", "title": "LaunchDarkly vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.json", "title": "LaunchDarkly vs Statsig", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-statsig" } ], "scores": [ { "by": 6, "edge": "statsig", "key": "reliability", "name": "Reliability", "optimizely": 73, "statsig": 79, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "statsig", "key": "schema", "name": "Schema \u0026 documentation", "optimizely": 74, "statsig": 82, "weight": 13 }, { "by": 3, "edge": "statsig", "key": "ergonomics", "name": "Agent ergonomics", "optimizely": 68, "statsig": 71, "weight": 13 }, { "by": 8, "edge": "statsig", "key": "security", "name": "Security \u0026 auth", "optimizely": 66, "statsig": 74, "weight": 14 }, { "by": 40, "edge": "statsig", "key": "payments", "name": "Payments \u0026 pricing", "optimizely": 0, "statsig": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "statsig", "key": "maintenance", "name": "Maintenance \u0026 community", "optimizely": 78, "statsig": 81, "weight": 7 }, { "by": 0, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "optimizely": 75, "statsig": 75, "weight": 7 } ], "summary": "Statsig scores 72.3 (BB) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 6 of 7 scored categories. Both do analytics experiments.", "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.", "statsig": "Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/optimizely-vs-statsig", "json": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.md", "slim": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.min.md" }, "markdown": "Statsig scores 72.3 (BB) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 6 of 7 scored categories. Both do analytics experiments.\n\n- Optimizely Experimentation: grade B, 62.6/100, rank #330 of 722. Markdown https://www.anchorterminal.com/tools/optimizely.md · JSON https://www.anchorterminal.com/api/v1/tools/optimizely.json\n- Statsig: grade BB, 72.3/100, rank #94 of 722. Markdown https://www.anchorterminal.com/tools/statsig.md · JSON https://www.anchorterminal.com/api/v1/tools/statsig.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\nWatch for: No price is published. The plans page says every plan is individually packaged and leads to a demo request\n\n### Statsig (BB)\n\nGood for: An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.\n\nAhead on:\n- Reliability, 79 against 73\n- Schema \u0026 documentation, 82 against 74\n- Security \u0026 auth, 74 against 66\n- Payments \u0026 pricing, 40 against 0\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: Console API errors carry only `status` and `message`, and the spec documents no 429 response\n\n\n## Score by category\n\n| Category | Weight | Optimizely Experimentation | Statsig | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 79 | Statsig +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 82 | Statsig +8 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 71 | Statsig +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 74 | Statsig +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 40 | Statsig +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 81 | Statsig +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 75 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.6 · B** | **72.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Optimizely Experimentation | Statsig |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Optimizely | Amplitude, Inc. |\n| Hosted endpoint | `https://exp.mcp.opal.optimizely.com/mcp` | `https://api.statsig.com/v3/mcp` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\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 hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |\n| Tools exposed | 7 | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.statsig/statsig-mcp-server` |\n| Last release | 2026-09-18 | 2026-09-28 |\n| Terms last updated | no date given | 2025-08-04 |\n| Privacy policy last updated | no date given | 2026-08-31 |\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 | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 460k npm/wk, 86k PyPI/wk | 4.2M npm/wk, 894k PyPI/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**Statsig.** Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.\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### Statsig\n\n1. Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools\n2. Call `get_context` first to learn the project, your permissions and the review settings\n3. Read the resource before `gate_update`, `experiment_update` or `dynamic_config_update`. They replace the whole resource, so resend every field you want kept\n4. Use `discover_tools` for partial edits, and fetch a fresh `operationHandle` when one expires\n5. On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes\n\n## Questions\n\n### Which is better for AI agents, Optimizely Experimentation or Statsig?\n\nStatsig scores 72.3 (BB) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 6 of 7 scored categories.\n\n### Do Optimizely Experimentation and Statsig need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Optimizely Experimentation and Statsig without installing anything?\n\nYes. Optimizely Experimentation has a hosted endpoint at https://exp.mcp.opal.optimizely.com/mcp and Statsig at https://api.statsig.com/v3/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/optimizely-vs-statsig.json, and with the fewest tokens: https://www.anchorterminal.com/compare/optimizely-vs-statsig.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"optimizely\", \"b\": \"statsig\"}`. From a terminal: `anchor compare optimizely statsig`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/optimizely.json and https://www.anchorterminal.com/api/v1/tools/statsig.json\n\n## Other comparisons with Optimizely Experimentation or Statsig\n\n- [Amplitude vs Optimizely Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-optimizely.md)\n- [Amplitude vs Statsig](https://www.anchorterminal.com/compare/amplitude-vs-statsig.md)\n- [Fullstory vs Optimizely Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-optimizely.md)\n- [Fullstory vs Statsig](https://www.anchorterminal.com/compare/fullstory-vs-statsig.md)\n- [Mixpanel vs Optimizely Experimentation](https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.md)\n- [Mixpanel vs Statsig](https://www.anchorterminal.com/compare/mixpanel-vs-statsig.md)\n- [Optimizely Experimentation vs Pendo](https://www.anchorterminal.com/compare/optimizely-vs-pendo.md)\n- [Pendo vs Statsig](https://www.anchorterminal.com/compare/pendo-vs-statsig.md)\n- [PostHog vs Statsig](https://www.anchorterminal.com/compare/posthog-vs-statsig.md)\n- [Heap vs Statsig](https://www.anchorterminal.com/compare/heap-vs-statsig.md)\n- [GrowthBook vs Optimizely Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-optimizely.md)\n- [GrowthBook vs Statsig](https://www.anchorterminal.com/compare/growthbook-vs-statsig.md)\n- [Optimizely Experimentation vs PostHog](https://www.anchorterminal.com/compare/optimizely-vs-posthog.md)\n- [LaunchDarkly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.md)\n- [LaunchDarkly vs Statsig](https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.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 Statsig", "url": "" } ], "description": "Statsig scores 72.3 (BB) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 6 of 7 scored categories. Both do analytics experiments. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Optimizely Experimentation B 62.6", "Statsig BB 72.3", "scores" ], "h1": "Optimizely Experimentation vs Statsig", "image": "https://www.anchorterminal.com/assets/og/compare-optimizely-vs-statsig.png", "path": "/compare/optimizely-vs-statsig", "published": "2026-10-01", "section": "tools", "title": "Optimizely Experimentation vs Statsig for AI agents, B 62.6 vs BB 72.3", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/optimizely-vs-statsig" }, "tokens": { "markdown": 2300, "slim": 730 }, "version": 1 }