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.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.