Build and inspect an agent flow
Siliqun Rotor lets an application register a named flow and run it through the task endpoint. Flow registration validates the supplied graph. A run returns its path and decision result; the trace records the flow journal when tracing is enabled. Use Studio's Flow Designer to construct and inspect a flow before connecting it to an application.
Flow lifecycle
- Build a flow in Studio with declared decision, tool, guard, and response behavior that your application supports.
- Register it with
POST /v1/flows and retrieve registered names with GET /v1/flows. - Call
POST /v1/task with task: "act", a question, and either the registered flow name or an inline flow. - Inspect the returned outcome and path. The application enforces its own permissions and executes any approved external action.
Build and inspect in Studio
For a first Studio run, use the Studio first-decision guide. It follows the current screens: Connect tools (/connect-tools), Design (/design), and Test (/test). In Connect tools, import an OpenAPI description or MCP tools, paste a tools list, or declare a tool by hand. Design edits the project's flow and guards; Test runs a request against the project's tools and shows the run result. These screens work on the current project's saved configuration; they do not connect a tool to its real customer system or authorize an external action for your application.
Flows can be project-scoped on authenticated customer deployments. Keep customer tools and credentials in the project that owns them. A flow journal describes the engine path; it does not attest that an external tool action was safe or successful.
See the agent harness, SDK guide, and the trace view in Studio for the contract and inspection workflow.