ceven

Bonsai

Monitors your search cluster health, automates the provisioning of new search spaces, and audits cluster configurations to prevent downtime.

Try Bonsai in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Bonsai integration

    • Describe the outcome and Ceven picks the right Bonsai calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Bonsai data, across all 3 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Bonsai access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Bonsai, when, and on whose behalf.
    • The agent pauses and asks when Bonsai is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Bonsai.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Bonsai action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Bonsai, and when to use it.

Get cluster details
Use this when you need to inspect the configuration, status, and health of a single cluster by its slug.
List spaces
Pull a list of all available spaces to see which server groups and geographic regions are available for your account.
Retrieve space details
Use this to get metadata for a specific space by its path before you provision a new cluster.
Create cluster
Provision a new search cluster in a specific space using a defined server group and cluster name.
Delete cluster
Remove a cluster by its slug. Use this for cleaning up ephemeral staging or test environments.
Update cluster
Change the server group or configuration of an existing cluster to scale resources up or down.
List clusters
Retrieve all clusters associated with the account to audit resource distribution across spaces.
Check cluster health
Pull the current health status of a cluster to identify if it is green, yellow, or red.
Get API keys
Retrieve the authentication credentials for a specific cluster to enable external application access.
Reset cluster password
Trigger a password reset for the cluster admin user when credentials are lost or rotated.
List available regions
Search for all global regions where Bonsai allows space creation to optimize for user latency.
Verify space path
Confirm a specific space path exists and is active before attempting a cluster deployment.
Get Bonsai Cluster Details
Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.
List Bonsai Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available to your account.

14 actions · scroll to see them all

Frequently asked questions

Ceven connects to your Bonsai account using a secure API key provided by your account administrator. This key is stored using industry standard encryption at rest and is never exposed to the end user or the large language model during prompt execution. When the agent needs to perform an action, it injects the key into the request header for the Bonsai API. You can rotate this key at any time within the Bonsai dashboard, which will require a quick update in the Ceven connection settings to restore service. This ensures that your infrastructure management remains secure and audit able at all times.
Yes, Ceven can be configured to scale clusters by using the update cluster action. You can build a workflow that monitors a specific metric, such as CPU usage or memory pressure, and triggers a server group upgrade when a threshold is hit. The agent will identify the current server group and select the next tier up based on your predefined rules. Because this involves infrastructure changes, we recommend adding a human in the loop approval step for production clusters to avoid unexpected costs or brief availability dips during the transition period.
Ceven is bound by the same API rate limits and account quotas imposed by Bonsai. One specific quirk is that cluster provisioning is an asynchronous process; the API will return a success response once the request is accepted, but the cluster may take several minutes to reach a ready state. If your workflow attempts to write data to the cluster immediately after creation, it will fail. We handle this by implementing a polling loop that checks the cluster health status until it returns a green state before proceeding to the next step in your workflow.
Ceven primarily manages the infrastructure layer of Bonsai, such as clusters, spaces, and server groups. To manage the actual indices, mappings, and documents within a cluster, the agent uses the standard Elasticsearch or OpenSearch API endpoints provided by your cluster slug. You will need to provide the cluster specific credentials to the agent. This allows the agent to perform complex tasks like creating index templates, running search queries, or deleting old indices based on a data retention policy you define in your workflow.
Absolutely. Ceven allows you to set fine grained permissions on a per integration basis. In the connection settings, you can toggle off the write and manage categories for the Bonsai integration. This restricts the agent to read only actions, meaning it can monitor health and list clusters but cannot create, update, or delete any infrastructure. This is a recommended setting for teams that want to use Ceven for observability and alerting without giving the AI the ability to modify the underlying search infrastructure.
Ceven treats spaces as the primary organizational unit for your clusters. The agent can list all spaces available to your account and retrieve the specific metadata for each one. When you ask the agent to deploy a cluster, you can either specify the space path explicitly or ask the agent to find the best space based on geographic region. This makes it easy to manage multi region deployments where you need search clusters close to your users in different parts of the world to keep latency low.
If you have a monitoring workflow active, Ceven will detect the status change via the check cluster health action. The agent can then initiate a series of recovery steps, such as alerting the on call engineer via Slack or checking the Bonsai service status page for known outages. Because the agent has access to the cluster details, it can include the exact cluster slug and the last known healthy state in the notification, which significantly reduces the mean time to resolution for your operations team.
Yes, Ceven supports both engines. Since Bonsai provides a unified management API for both Elasticsearch and OpenSearch clusters, the infrastructure actions like listing clusters or checking health work identically regardless of the engine. For data plane operations, the agent adapts its API calls to match the specific version and engine type of the cluster you are targeting. You can verify which engine a cluster is running by using the get cluster details action before sending data specific queries.

Alternatives to Bonsai

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Elastic Cloud logoElastic CloudAlgolia logoAlgoliaMongoDB Atlas Search logoMongoDB Atlas Search

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Bonsai and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free