Two ways to author an Agent
Agent Builder
Default path. Describe the site and fields in plain language; Sequentum plans, builds, tests, and hands you a runnable Agent.
The Editor
Advanced path. Hand-author the command tree for complex navigation, custom scripts, or niche commands.
What an Agent contains
Every Agent combines:- Commands — the navigation and extraction instructions: open pages, click, fill forms, paginate, parse fields, and export data.
- Output schema — the fields and record shape the Agent emits.
- Runtime settings — optional browser, proxy, anti-blocking, and execution properties.
Lifecycle
1
Build
A new Agent starts as a draft while it is being built or edited.
2
Save
Publishing the draft creates the first saved version. The Agent receives an integer
agentId and versionNumber 1.3
Create versions
Each later save creates a new
versionNumber. The highest-numbered version is active unless you restore an earlier one.runId, status, outputs, and diagnostics.
Run an Agent
Once an Agent is saved, you can:- Start it manually in Control Center.
- Call
POST /agent/{agentId}/startfrom your application. - Attach a Schedule for recurring runs.
- Expose it to LLM workflows through MCP.
Identifiers
These are the IDs you’ll see most often when working with Agents:agentId
Unique identifier for the Agent. It appears in Agent detail screens, run-start responses, and Agent API paths.
versionNumber
Saved version of an Agent. It increments on each save and is used when restoring an earlier version.
runId
Identifier for a single execution of an Agent. Each run has its own status, outputs, diagnostics, and lifecycle.
Related API references
Start a run
Trigger an Agent and optionally return records synchronously.
List agents
Find the Agents available in a Space.
Restore a version
Roll an Agent back to an earlier saved version.
Run lifecycle
Understand run status, outputs, stopping, and failures.