Jentic 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.
# 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.