Algolia A/B Testing API
Browse all Algolia APIs★ Only Publicly Available OpenAPI DocumentAnalyticsProduct AnalyticsapiKey11 EndpointsREST
For Agents
Create, monitor, and stop search relevance A/B tests on Algolia indices through 11 dedicated endpoints with sample size estimation.
Use for: I need to create a new A/B test between two Algolia index variants, Estimate how long a planned Algolia A/B test will need to run, Retrieve the latest results for a running A/B test, List every A/B test on my Algolia application
Not supported: Does not run search queries, ingest events, or manage indices — use for creating, monitoring, stopping, and estimating Algolia A/B tests only.
Jentic publishes the only available OpenAPI specification for the Algolia A/B Testing API, keeping it validated and agent-ready. The A/B Testing API lets teams run controlled search relevance experiments on Algolia indices, comparing two index variants against live user traffic. Endpoints cover creating tests, listing them, retrieving variant performance, stopping tests, and estimating sample size and duration before launch. Authentication uses two headers: x-algolia-application-id and x-algolia-api-key.
Install Jentic One Beta
Connect the A/B Testing API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the A/B Testing API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with A/B Testing API.
Create a search relevance A/B test between two index variants with POST /2/abtests
List every active and historical A/B test on the application via GET /2/abtests
Retrieve detailed performance metrics for a specific A/B test by id
Stop a running A/B test before its scheduled end with POST /2/abtests/{id}/stop
Delete an A/B test record once analysis is finished
Estimate the required sample size and duration for a planned A/B test before launch
Use Cases
Patterns agents use A/B Testing API for, with concrete tasks.
★ Search relevance experiment for a marketplace
A search engineering team tests a new ranking formula by creating an A/B test in Algolia: variant A is the production index, variant B uses an updated custom ranking. They call POST /2/abtests with the variants and traffic split, then poll GET /2/abtests/{id} for click-through and conversion deltas. The team avoids shipping a regression to all users by gating the change on the test result.
POST /2/abtests with variant A=production, variant B=updated, and 50/50 traffic; poll GET /2/abtests/{id} every 24 hours for the result delta
Pre-launch sample size estimation
Before launching an experiment, a product analyst calls POST /2/abtests/estimate with the expected effect size and confidence level so the team can budget the test correctly. The endpoint returns the required sample size and duration; the analyst then schedules the actual A/B test only if the projected runtime fits the release plan.
POST /2/abtests/estimate with the effect size and traffic, then only call POST /2/abtests if the projected duration fits the release window
Automatic shut-off for underperforming experiments
An ops automation polls /2/abtests/{id} for each running test and calls POST /2/abtests/{id}/stop when the leading variant crosses a confidence threshold or when negative conversion impact exceeds a guardrail. This keeps experiments from running longer than necessary and protects revenue when a variant clearly hurts performance.
GET /2/abtests/{id} on a schedule, evaluate guardrail metrics, and call POST /2/abtests/{id}/stop when the threshold is breached
Agent-driven experiment lifecycle through Jentic
A Jentic agent receives an intent like 'check on my running search experiments' and calls GET /2/abtests followed by GET /2/abtests/{id} for any tests that are still active. The agent summarises the results without exposing the application id and api key, which stay in the Jentic vault.
Search Jentic for 'list Algolia A/B tests', execute GET /2/abtests, then GET /2/abtests/{id} for any running tests and return a summary
Key Endpoints
11 endpoints — jentic publishes the only available openapi specification for the algolia a/b testing api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/2/abtests
Create an A/B test
GET
/2/abtests
List all A/B tests
GET
/2/abtests/{id}
Retrieve A/B test details
DELETE
/2/abtests/{id}
Delete an A/B test
POST
/2/abtests/{id}/stop
Stop a running A/B test
POST
/2/abtests/estimate
Estimate sample size and duration
POST
/2/abtests
Create an A/B test
GET
/2/abtests
List all A/B tests
GET
/2/abtests/{id}
Retrieve A/B test details
DELETE
/2/abtests/{id}
Delete an A/B test
POST
/2/abtests/{id}/stop
Stop a running A/B test
POST
/2/abtests/estimate
Estimate sample size and duration
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Both x-algolia-application-id and x-algolia-api-key are stored encrypted in the Jentic credential vault and injected at execution time. The raw keys never enter the agent's prompt context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create an Algolia A/B test', 'list my A/B tests'), and Jentic returns the matching A/B Testing API operation with its input schema for direct execution.
Time to first call
Direct Algolia A/B Testing integration: 1-2 days for header auth, region routing, and result polling. Through Jentic: under an hour with search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using A/B Testing API through Jentic.
Why is there no official OpenAPI spec for the Algolia A/B Testing API?
Algolia does not publish a downstream-stable OpenAPI specification for direct agent use. Jentic generates and maintains this spec from Algolia's source bundles so AI agents and developers can call the A/B Testing API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Algolia A/B Testing API use?
The API requires two headers: x-algolia-application-id and x-algolia-api-key. The API key must have ACL permissions matching the requested endpoint. Jentic stores both values encrypted and injects the headers at execution time so neither key enters the agent's prompt context.
Can I create a new search A/B test through this API?
Yes. POST /2/abtests with the two variant index references, the traffic split, and the test name. The API returns the test id which you can use with GET /2/abtests/{id} to track results or POST /2/abtests/{id}/stop to end the test early.
What are the rate limits for the A/B Testing API?
Algolia documents a limit of 100 requests per minute per application for the A/B Testing API. Response headers include current rate-limit information; pace polling jobs to stay under that ceiling, especially when monitoring multiple tests at once.
How do I estimate the duration of a planned A/B test through Jentic?
Search Jentic for 'estimate algolia ab test duration', load the schema for POST /2/abtests/estimate, and execute it with the expected effect size and traffic share. Jentic returns the recommended sample size so an agent can decide whether to schedule the experiment.
Is the A/B Testing API available on every Algolia plan?
Algolia restricts A/B Testing to its Premium and Elevate plans. Confirm your plan in the Algolia dashboard before scripting against this API; calls from accounts without access return an authorisation error rather than a permission scope error.
GET STARTED