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 Crawler API, keeping it validated and agent-ready. The Crawler API drives Algolia's hosted web crawler — programmatically creating crawlers, updating their configuration, starting and pausing crawls, testing URL extraction, listing runs, downloading run logs, and managing registered domains. It is distinct from the standard Algolia search and ingestion APIs and uses its own credential pair. Authentication is HTTP basic auth with the Crawler user id and Crawler API key.
20 endpointsJentic publishes the only available OpenAPI specification for the Algolia Monitoring API, keeping it validated and agent-ready. The Monitoring API exposes real-time and historical infrastructure metrics for Algolia clusters - latency, indexing time, reachability, and incident reports - sourced from external probes that hit Algolia's servers continuously. It is intended for status pages, on-call dashboards, and SLO reporting, not for app-specific performance debugging. Premium and Elevate plan customers can access cluster-level metrics; status and incident endpoints are public.
14 endpointsJentic publishes the only available OpenAPI specification for the Algolia Ingestion API, keeping it validated and agent-ready. The Ingestion API powers Algolia's no-code data connectors, letting you create sources, destinations, and tasks that pull data from external systems into Algolia indices on a schedule. It exposes 61 endpoints for managing authentications, sources, destinations, transformations, tasks, and run observability. Use it to wire up CSV, BigQuery, Shopify, or custom-Docker connectors and to monitor every ingestion run.
61 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 endpointsJentic publishes the only available OpenAPI specification for the Algolia Personalization API, keeping it validated and agent-ready. The Personalization API manages personalization strategies and user profile data for Algolia search experiences. You define which facets and events count toward each user's affinity score, then read or delete the resulting per-user profile. Personalization is rate-limited to 40 calls per second per application.
9 endpointsJentic publishes the only available OpenAPI specification for the Algolia Query Suggestions API, keeping it validated and agent-ready. The Query Suggestions API manages the configuration of suggestion indices that Algolia generates from your search analytics, external suggestion lists, or facet values. You define which source indices contribute, which facets are eligible, and how often the suggestions index is rebuilt. The resulting suggestions index can then be queried like any other Algolia index to power autocomplete experiences.
12 endpointsJentic publishes the only available OpenAPI specification for the Algolia Recommend API, keeping it validated and agent-ready. The Recommend API serves product recommendations - related items, frequently bought together, trending items, looking similar - powered by models trained on Insights events. It also exposes a rules engine so merchandisers can pin, hide, or boost recommendations for specific objects. Eleven endpoints cover recommendations retrieval and rule management.
11 endpointsJentic publishes the only available OpenAPI specification for the Algolia Search API, keeping it validated and agent-ready. The Search API is Algolia's core surface - 78 endpoints covering query execution, indexing, synonyms, rules, dictionaries, API key management, clusters, vaults, and more. It serves single-index and multi-index queries, faceted filtering, browsing, batch object operations, and admin tasks like settings management and key rotation. The Search API is the foundation that the Recommend, Personalization, and Query Suggestions services build on.
78 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.