Data & AI · wired today
Drive Meilisearch with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The Meilisearch connector is one of 222 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 Meilisearch
| Tool | What it does |
|---|---|
get_version | Get the version of the Meilisearch instance (package version and build commit) |
get_stats | Get instance-wide Meilisearch stats: database size, last update, and per-index document counts |
list_indexes | List the indexes on this Meilisearch instance |
get_index | Get one Meilisearch index by its uid (primary key and timestamps) |
search_index | Search documents in one Meilisearch index (read-only GET search endpoint) |
list_tasks | List recent Meilisearch tasks (indexing, settings and document operations) with their status |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Meilisearch connector needs
You provide host, API key from your Meilisearch account; Quox sends it as a bearer token. 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: Meilisearch'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 Meilisearch 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.
- Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
- Read-only It ships read tools only, so there is nothing to approval-gate.
- Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
- Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
- Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.
Meilisearch integration FAQ
What can Quox agents do with Meilisearch?
Agents can run 6 read-only tools against Meilisearch: get version, get stats, list indexes, get index, search index and more. Every call is receipted in the evidence trail.
What does the Meilisearch integration need?
You provide host, API key from your Meilisearch account; Quox sends it as a bearer token. 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 Meilisearch 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 Meilisearch connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Meilisearch 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.