Add infrastructure suite
Seed this agent with the Infrastructure Suite, a tagged 'infrastructure-suite' folder of ~17 real reliability scenarios (latency, audio quality, interruption, dead air, double-speak, ramble, stability) with the deterministic metric set attached, so you can run a one-click reliability sweep. Idempotent: re-adding tops up only the missing scenarios. Returns { ok, created, folder }.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Target agent as 'workspace-slug/agent-slug' (e.g. 'luke/support-bot').
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/add_infrastructure_suite" \ -H "Content-Type: application/json" \ -d '{ "agent": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Add dashboard plot POST
Add one plot (widget) to an Overview dashboard from a natural-language description. Given a dashboardId (from list_dashboards) and a description like 'success rate by agent', this maps the request to a valid plot spec, data field, chart type, aggregation and group-by, all constrained to the dashboard's supported columns, and saves it to the dashboard's grid. To narrow the calls a plot counts (for example only calls where the caller hung up), pass `filters`; the description alone never filters. The dashboard's time range sets the dates; the description does not. Use it to build out a dashboard conversationally instead of the manual Add-Plot modal. This charts our OWN historical call data; it never changes how an agent behaves. Persists immediately; one plot per call. One short AI call drafts the plot and is billed to the workspace as AI usage.
Add plugin POST
Add a PLATFORM PLUGIN as a finished HTTP tool, a paid third-party capability that runs on Vertical AI's account, not the customer's. The tool arrives fully authored: URL, headers, input schema, response handling and description are already written, and the API key resolves from a platform variable, so nothing needs setting up afterwards. Each call is metered to the workspace at the plugin's rate and itemised on the bill. Prefer this over hand-building an HTTP tool against Google Maps: a hand-built one needs a key pasted in as a secret variable and reproduces none of the tuned error handling.