Agent mode

Fully autonomous browser interaction. The AI browses, captures, and writes the client end-to-end.

Agent mode hands the steering wheel to the AI. Describe the goal in plain English and the agent drives a browser through MCP while reverse-engineering the API in real time.

Agent mode capturing a job board autonomously — Agent mode: autonomous capture and codegen in one flow.

When to use it

You want full automation, no manual browsing required.
The site exposes a stable, predictable flow (public job boards, docs sites, marketing APIs).
You're scripting captures from another agent, a cron job, or CI.

Running interactively

reverse-api-engineer
# switch to agent mode with Shift+Tab
> click on the first job listing

Running non-interactively

reverse-api-engineer agent \
  --prompt "capture the public jobs api" \
  --url https://example.com/jobs \
  --json | jq

The --json flag makes the command emit a single JSON document on stdout (see Scripted usage for the schema and exit codes).

Agent providers

Pick the provider in /settings then "agent provider".

Playwright MCP browser automation with your configured SDK. Combines browser control and real-time reverse-engineering in a single workflow. Use --headless when running on machines without a display.

Reasoning model

The agent's reasoning model is the same as your configured SDK model. See Model selection to change it.