Data & AI · wired today
Drive Elasticsearch with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The Elasticsearch connector is one of 205 executable connectors and gives agents 6 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Elasticsearch
| Tool | What it does |
|---|---|
cluster_health | Get Elasticsearch cluster health: green/yellow/red status, node counts and shard allocation |
cluster_stats | Get Elasticsearch cluster statistics: index count, document count, store size, node count and versions |
list_indices | List the indices on the cluster with health, status, shard counts and document counts |
get_index | Get one index's aliases, mappings and settings |
count_documents | Count the documents in one index, optionally matching a Lucene query string |
search | Search one index with a Lucene query string and return the matching documents |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Elasticsearch connector needs
You provide host, username, password from your Elasticsearch account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Elasticsearch's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Elasticsearch instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.
Elasticsearch integration FAQ
What can Quox agents do with Elasticsearch?
Agents can run 6 read-only tools against Elasticsearch: cluster health, cluster stats, list indices, get index, count documents and more. Every call is receipted in the evidence trail.
What does the Elasticsearch integration need?
You provide host, username, password from your Elasticsearch account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Elasticsearch credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Elasticsearch connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Elasticsearch instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.