Loading...
Loading...
REST API Status
ABTestResult is now built around the local MCP server. If you want to use ABTestResult inside Claude, Codex, Cursor, VS Code, or another assistant, the right path is MCP, not REST.
MCP runs on the user's machine, exposes the statistical tools directly to the assistant over stdio, and avoids pushing experiment data through a hosted API layer. It is the cleaner integration model for agentic workflows and the one we actively support.
This is the recommended and actively supported integration path.
Runs locally on the same machine as the assistant.
Keeps test inputs and outputs out of a hosted API round-trip.
Avoids API key distribution for normal assistant workflows.
Maps naturally to tool-calling agents and local automation.
The MCP server runs where the assistant runs. That keeps analysis close to the user, avoids an extra hosted dependency, and fits the way modern local agent tooling actually works.
Assistants can call ABTestResult as tools instead of stitching together raw HTTP requests. That makes integration simpler, more reliable, and easier to reason about.
For the main assistant use case, there is no reason to route sensitive experiment data through a public API surface. MCP removes that default exposure.
The old REST API documentation was intentionally removed. We do not want to direct new users toward the wrong integration model when the MCP server is the better fit for AI assistants, local automations, and agent-driven analysis.
If you came here expecting endpoint docs, that is deliberate: the recommended setup is now the MCP server. It is ready for agentic workflows, easier to operate, and more secure because it runs locally instead of depending on a remote API boundary for the default use case.
For most users, there is nothing to request here. Go straight to the MCP setup page and wire ABTestResult into your assistant locally.
The same ABTestResult calculations remain available. The difference is the access model: use them locally through MCP instead of building on the public REST surface.