Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Algolia / Algolia Monitoring API
Algolia Monitoring API logo

Algolia Monitoring API

Browse all Algolia APIs
62
AI ReadinessAI-Aware (B-)62/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring ObservabilityapiKey14 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Pull Algolia cluster status, latency, indexing time, and incident data so agents can monitor service health and trigger alerts. Read-only.

Use for: Check whether my Algolia cluster is currently up, Retrieve open incidents for a specific cluster, Get the average search latency for the past hour, List all servers in my Algolia infrastructure

Not supported: Does not handle search execution, index management, or app-level analytics - use the Algolia Search and Insights APIs for those. Use this API for cluster health and infrastructure monitoring only.

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

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Algolia Monitoring API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Algolia Monitoring 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Falgolia.com%2Falgolia-monitoring-api" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Falgolia.com%2Falgolia-monitoring-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Algolia Monitoring API.

Check the operational status of Algolia clusters via /1/status and /1/status/{clusters}

Retrieve current and historical incidents per cluster via /1/incidents and /1/incidents/{clusters}

Query latency metrics for any cluster the application is on via /1/latency/{clusters}

Read indexing time metrics to detect ingestion slowdowns via /1/indexing/{clusters}

Inspect reachability probe results from multiple geographic regions via /1/reachability/{clusters}/probes

Pull infrastructure metrics like CPU, RAM, and SSD usage for premium-tier accounts via /1/infrastructure/{metric}/period/{period}

Use Cases

Patterns agents use Algolia Monitoring API for, with concrete tasks.

★ Internal status page driven by Algolia metrics

Build an internal status page that polls /1/status and /1/incidents on a schedule and surfaces any open incidents alongside latency from /1/latency. Because /1/status and /1/incidents do not require auth, the polling job can be a cheap unauthenticated cron without managing API keys.

GET /1/status and /1/incidents every 60 seconds and post any non-operational state to the on-call Slack channel

On-call latency alerting

Poll /1/latency/{clusters} every minute, compare the rolling p95 to a threshold, and page on-call when search latency degrades. Combined with /1/indexing/{clusters} this catches both query-side and ingestion-side slowdowns before users notice.

GET /1/latency/c1-prod every 60 seconds, raise a PagerDuty incident if p95 latency exceeds 200 ms for 3 consecutive samples

Capacity planning for premium-tier accounts

On Premium and Elevate plans, query /1/infrastructure/{metric}/period/{period} for CPU, RAM, and SSD usage trends. Combine the data with /1/inventory/servers to see which servers are nearing saturation and decide whether to provision a larger cluster.

GET /1/infrastructure/cpu_usage/period/day and /1/inventory/servers to identify any server above 75 percent CPU

Agent-driven health checks before high-stakes operations

Before triggering a large reindex or migration, an AI agent can call the Monitoring API through Jentic to verify cluster status and current latency. If the cluster shows incidents or elevated indexing time, the agent can pause the operation and notify a human.

Search Jentic for 'check Algolia cluster status', load getStatus, and execute - abort the reindex plan if any cluster reports degraded state

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for the algolia monitoring api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/1/status

Get overall Algolia cluster status

GET

/1/incidents

List incidents across all clusters

GET

/1/latency/{clusters}

Latency metrics per cluster

GET

/1/indexing/{clusters}

Indexing time per cluster

GET

/1/reachability/{clusters}/probes

Reachability probe results

GET

/1/infrastructure/{metric}/period/{period}

Infrastructure metric over a time period

GET

/1/status

Get overall Algolia cluster status

GET

/1/incidents

List incidents across all clusters

GET

/1/latency/{clusters}

Latency metrics per cluster

GET

/1/indexing/{clusters}

Indexing time per cluster

GET

/1/reachability/{clusters}/probes

Reachability probe results

GET

/1/infrastructure/{metric}/period/{period}

Infrastructure metric over a time period

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Algolia Monitoring API

- AI-Aware (B-)
62/100
55
Foundational Compliance
68
Developer Experience & Jentic Compatibility
48
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
55

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4
89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

68

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
24%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

48%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

48

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
52%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

41%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Algolia Monitoring API by hand means sending its API key, targeting the status.algolia.com host, and polling cluster status, latency, and incident reads yourself. Through Jentic you install once, import the Algolia Monitoring API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Monitoring API puts the cluster and metric names in the URL path (/1/latency/{clusters}, /1/indexing/{clusters}, /1/infrastructure/{metric}/period/{period}), so a rule can pin your agent to one cluster or metric. This API is read-only, so you choose which of these health reads the agent may call.

Credential isolation

Your Algolia API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check Algolia cluster status' or 'read cluster latency', and Jentic returns the matching Algolia Monitoring operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Statuspage API

→

General-purpose status page hosting and incident communication

Choose Statuspage when you want a managed public status page rather than building your own from raw metrics.

Alternative

UptimeRobot API

→

External uptime monitoring with HTTP and ping checks

Choose UptimeRobot for synthetic uptime checks of any HTTP endpoint, not just Algolia clusters.

Complementary

Algolia Search API

→

Run searches against the clusters Monitoring observes

Use Search for actual queries; use Monitoring to track the health of the cluster serving them.

Complementary

New Relic API

→

Application observability layered on top of infrastructure metrics

Use New Relic alongside the Monitoring API to correlate Algolia cluster health with end-to-end application traces.

FAQs

Specific to using Algolia Monitoring API through Jentic.

Why is there no official OpenAPI spec for the Algolia Monitoring API?

Algolia does not publish a standalone OpenAPI specification for the Monitoring API. Jentic generates and maintains this spec so that AI agents and developers can call the Monitoring API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Algolia Monitoring API use?

Infrastructure endpoints require X-Algolia-Application-Id and X-Algolia-API-Key headers and are limited to Premium and Elevate plans. Status and incidents endpoints are public and require no auth. Through Jentic, the Monitoring API key is stored in the vault and injected only when calling the protected endpoints.

Can I get historical latency data with the Monitoring API?

Yes. /1/latency/{clusters} returns recent latency samples and /1/infrastructure/{metric}/period/{period} returns metrics aggregated over the requested period. Historical depth depends on plan tier.

What are the rate limits for the Algolia Monitoring API?

The spec does not declare explicit rate limits. Algolia recommends polling intervals no faster than once per minute for /1/status and /1/latency to avoid throttling on large fleets.

How do I monitor cluster status from an agent through Jentic?

Search Jentic for 'check Algolia cluster status', load the getStatus operation, and execute. For protected endpoints like /1/infrastructure, Jentic injects the Monitoring API key so the agent never handles it directly.

Does this API show metrics specific to my application?

No. Metrics reflect the overall Algolia infrastructure status for the clusters your application sits on, not the performance of your specific app ID. Use the Search API analytics for app-level query metrics.

Can I limit what my agent is allowed to do with the Algolia Monitoring API?

Yes. Because you run Jentic One yourself, your own rules decide which Monitoring operations and credentials the agent may use. The Algolia Monitoring API puts cluster and metric names directly in the URL path (/1/latency/{clusters}, /1/indexing/{clusters}, /1/infrastructure/{metric}/period/{period}), so a rule can pin the agent to a single cluster or metric. Since every operation is read-only, you simply choose which health reads such as status, incidents, latency, or infrastructure the agent is allowed to call.

GET STARTED

Start building with Algolia Monitoring API

Explore with Jentic One
View OpenAPI Document