Test and publish an agent

Run a draft with test inputs, read what it did, publish a version, and call the published agent from other systems.

A draft cannot be called from outside. You test it, and when the test is good you publish it as a version. Callers get the newest published version unless they ask for another. Test an agent# You need jobs.create in the workspace, and the setup checklist must be complete. If something is missing, a line under the agent's name says what, for example No robot with Python is available., and Test agent is unavailable. Open the agent and select Test agent. With unsaved changes the button is Save and test: it saves first. In Inputs, enter the test input as JSON. The dialog starts with every property of the input schema and an empty value. Select Start test run. The run page opens. The run is Pending with Waiting for a robot with Python. until a Robot claims it. Then each step appears as it finishes, and the run ends as Completed with the agent's Output. Select a step to see its Input, Output and Details. For a vector store search this is the query and the documents it found; for a model call, the tools the model asked for and the token usage. To test again with the same inputs, select Run again on the run page. Read more about the run page in Runs and approvals. Publish a version# After a test of the current draft, the builder shows Publish version. Select Publish version. VeloPhex freezes the draft and runs the publish checks. Read the checks. Each one has a green tick or a red cross with the reason: Check Passes when candidate_status The version is still a candidate (not revoked or already published). definition_valid The definition is valid. tools_resolvable Every tool still resolves to what it was when the version was frozen. no_forbidden_tools No tool is in the agent's blockedTools. binding_allowed The workspace's AI policy allows the model. dataset_gate Only when the agent has an evaluation gate: the newest evaluation of this version on the gate dataset scores at least the minimum. See Evaluations. Select Publish version. The button is unavailable while a check fails. The agent's badge changes to Version 1 (2, 3, and so on for later versions). The Versions tab lists every version with its Status: Test for a test run's snapshot, Release candidate, Published or Revoked, and the Draft revision it was made from. The Agents list shows each agent's published version, or Draft if it has none. A version records the exact process package, model and price it used. If a tool's process gets a new package version, test and publish the agent again. Call a published agent# Other systems start a run of the published version through the API, with a personal access token or another bearer token and jobs.create in the workspace. Invoke an agentHTTPCopyPOST /api/v1/tenants/{tenantId}/workspaces/{workspaceId}/agents/invoice-triage-agent/runs?wait=60 Authorization: Bearer <your access token> Idempotency-Key: 7d1c0b9e-2f3a-4c55-9b8e-1f0a2d3c4b5a Content-Type: application/json { "inputs": { "invoiceNumber": "INV-2026-0416", "vendor": "Litware Inc", "amount": 980, "currency": "EUR" } } wait (0 to 60 seconds) holds the request until the run ends. A run that ended answers 200 with its output; a run still going answers 202 with a Location header to poll. Send an Idempotency-Key header. Sending the same key again returns the same run, so a retry after a lost answer never starts a second run. To run an older published version, add "version": <number> to the body. An agent with no published version answers 409 agent_not_published. The run appears on the Runs page with the kind Invoke. When a run ends, VeloPhex publishes the webhook event com.velophex.agent.run.completed. See Audit and webhooks. Next steps# Runs and approvals Evaluations

Test an agent

Publish a version

Call a published agent

Next steps