Skip to main content
HTTP API connector An HTTP API described by an OpenAPI spec, not an MCP server. Calls go to the server address you enter when connecting and carry HTTP basic authentication with the username and key you enter when connecting.

​
What the skill can do

API connector: 1 actions, as they appear in the skill panel. 1 of them create, change or delete something in ClickHouse Query API; mark those under These actions need approval when you add the skill to an agent.
  • Query management (1): Click House Endpoint Service Execute Sqlquery Httppost

​
Connect ClickHouse Query API

In Xpander Chat, open the agent’s settings, click Add skill, and search for ClickHouse Query API. The connect dialog asks for a connection name and whether the connection is for the Organization (one shared account) or Personal (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person’s own sign-in; see whose credential a shared agent uses. ClickHouse Query API connects with an API key. Create the key in ClickHouse Query API, paste it into the dialog, and click Connect. The key goes to the vault; the agent references it and never sees the value. Calls go to {serverUrl}.

​
Give an agent the ClickHouse Query API skill

Once ClickHouse Query API is connected, any agent you can edit may be given the skill: open the agent’s settings, click Add skill, and choose ClickHouse Query API. Enable only the action groups the agent needs, and mark the actions that should wait for a named person’s sign-off under These actions need approval. Which skills exist for your organization, and who may add them, is decided by your admins; see Skills.