Tasks enqueued with POST /api/agent/jobs
(same account as below). Data is kept in server memory until restart.
Sign in from the main page (same browser), then return here. The page uses your saved session token.
Status
Task
Target URL
Started (UTC)
No HTTP jobs yet for this account.
Job detail
HTTP API
Run an agent task without WebSockets: enqueue with POST /api/agent/jobs (response 202), then poll GET /api/agent/jobs/{job_id} until status is completed or failed. List your jobs with GET /api/agent/jobs — you are viewing this list now (requires sign-in).
Base URL for this page:
Get a token (login)
Verify session
Create job
Poll result
Poll structured data only
Query structured_data_only=true on GET /api/agent/jobs/{job_id} for only the parsed JSON from the assistant (same idea as schedule Webhook payload: only structured_data). Queued/running: HTTP 202 with null. Completed: 200 with the JSON value or null.
Protected routes use Authorization: Bearer <access_token> — same JWT as /api/auth/login or the main page after Sign in. Each job is only visible to the user who created it. Treat copied commands like passwords if they contain a real token. Step-by-step (construction) mode is only available over the WebSocket protocol.
Optional output_json_schema (string) steers the model’s fenced JSON output (same idea as “Structured JSON output” on the main demo).
For free-navigation agent mode, set target_url to __agent__ (same as the in-app agent).
