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.
11 endpointsJentic 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.
11 endpointsJentic publishes the only available OpenAPI specification for the Algolia Insights API, keeping it validated and agent-ready. The Insights API captures user interaction events - clicks, conversions, views, and add-to-carts - that feed Algolia's Recommend, Personalization, Dynamic Re-Ranking, and analytics features. It exposes event ingestion, user-token deletion for GDPR compliance, and a small set of utility endpoints. Send events from your search UI to unlock relevance tuning that learns from real user behavior.
7 endpointsStep 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 | shStep 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.