Agent Builder turns natural language into a working extraction Agent. You describe the data you want; Agent Builder plans, navigates, parses, and validates — then hands you a real, versioned Agent you can run, schedule, or share. This is the default authoring path in Sequentum Cloud. From here, you’ll typically run the Agent via the API. Reach for the Editor only when Agent Builder can’t yet handle a corner case (custom scripts, complex navigation, niche commands).Documentation Index
Fetch the complete documentation index at: https://docs.sequentum.com/llms.txt
Use this file to discover all available pages before exploring further.
How it works
Test
The plan is executed against the live site. Agent Builder reports back: pages visited, records extracted, anything blocked.
Iterate
Send a follow-up — “include image URLs” or “skip out-of-stock items” — and Agent Builder revises.
Two ways to use it
Control Center UI
Click “New agent → Build with AI.” Best for one-off agents and exploration.
API
Build agents programmatically. Best when agent creation is part of a pipeline or product feature you ship to your own users.
Session lifecycle
A Builder session is a stateful object with five statuses —processing, ready, completed, error, cancelled. You start a session with a prompt, watch events stream as Agent Builder plans and tests, and end with completed (Agent saved) or cancelled. At launch the experience is single-shot — describe the agent comprehensively in your first prompt and it’s built and ready to run.
See Sessions for the full state machine.
What’s next
- Quickstart — build your first agent in 5 minutes.
- Sessions — the state machine, in detail.
- API reference: Start a session — kick off a session programmatically.
- API reference: Start a run — once the Agent exists, this is how you operate it.