An Agent Builder session is a stateful, conversational object. Unlike a one-shot API call, a session lives across multiple requests: youDocumentation Index
Fetch the complete documentation index at: https://docs.sequentum.com/llms.txt
Use this file to discover all available pages before exploring further.
start it, watch events stream, send follow-ups, and finish it to produce a real Agent.
Statuses
A session reports one of five statuses onGET /{sessionId}/status:
| Status | Meaning | What you can do |
|---|---|---|
processing | Agent Builder is actively working — loading the site, planning, executing steps, or testing. | stop, cancel |
ready | Builder is paused awaiting your input — typically after a ready_for_interaction event. | followup, finish, cancel |
completed | Session ended; the Agent was saved. Read-only. | (none — see Agents API) |
error | Session ended with an unrecoverable error. | (none) |
cancelled | You cancelled the session. | (none) |
status field of the GET /status response.
Endpoints
Watching progress
GET /events?lastEventIndex=N is the event stream — long-poll it. Pass lastEventIndex=-1 on the first call, then keep passing the index from each response. See Streaming events for the full event taxonomy and code examples.
Operating verbs
followup— send a new user message. Resumes building from areadystate.finish— save the in-progress agent. Session ends withcompletedstatus; the response carries the newagentId.stop— interrupt the current operation without ending the session. The session stays alive and can accept follow-ups.cancel— terminate the session entirely. No Agent is created.
cancelled event in the streaming endpoint — detect cancellation by polling GET /status and watching for status: "cancelled".