Quarterly experiment review
Priya Sharma, product manager at Acme Ltd, asked which experiments had concluded with a winner. Memtro listed them with hypothesis, winning variation and key takeaways, each linked to its results.
Which Eppo experiments are running, and which variation is winning?
Eppo connects Memtro to your experiments and feature flags. It reads experiments by status, tag and date with hypothesis, progress, winner and takeaways, and the diagnostic checks behind a missing result. It also reads flags with environments, variations and allocations, plus metrics and tags. When asked and granted, it can duplicate, refresh or delete an experiment, add a metric collection, create, edit, switch or archive a flag, manage allocations, and create or delete tags. With events on, Eppo tells Memtro when an experiment's status changes, and a job can start on it. Only Eppo admins can create the key.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Eppo tool, reads what it needs, and answers with the source cited.
These tools change something in Eppo. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Eppo, choosing the same kinds; the tab shows Eppo's own steps. Each event can start a job, with the event as its input. Eppo signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Eppo is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which experiments are running, and who is winning?
Why does the checkout experiment have no results?
Which feature flags are on in production?
Which metrics are certified, and what is their guardrail cutoff?
Turn the new-pricing flag off in staging.
Priya Sharma, product manager at Acme Ltd, asked which experiments had concluded with a winner. Memtro listed them with hypothesis, winning variation and key takeaways, each linked to its results.
At BigCo, a job starts when Eppo reports an experiment's results pipeline finished. On a failure, it reads the experiment's diagnostic checks and gives Dan Fletcher, the data lead, the failing check and its error.
The teams that lean on Eppo most, a question each of them asks, and what they connect beside it.
A record in Eppo is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Eppo, open Admin, API Keys and create a REST API key, not an SDK key. Only Eppo admins can create one, and they set its permissions.
In Memtro, open Connections → Eppo and paste the REST API key.
An administrator grants the actions by name, such as turning flags on or off, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added under Admin, Integrations in Eppo.
Ask which experiments are running and who is winning.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Eppo tools are the same everywhere.
Only when you ask, and only what it has been granted: duplicate an experiment under a new name; refresh an experiment's results (runs queries on your data warehouse); delete an experiment; add a metric collection to an experiment; create a feature flag; rename a feature flag or change its description or tags; turn a feature flag on or off in an environment; add a targeting allocation to a feature flag; archive an allocation of a feature flag; archive a feature flag; create a tag; delete a tag. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
REST API key. In Eppo, open Admin, API Keys and create a REST API key, not an SDK key. Only Eppo admins can create one, and they set its permissions.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Eppo, choosing the same kinds; the tab shows Eppo's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time