derive-client

1# Derive an API client from a recorded session
2 
3Driving a browser is the right tool for the first visit and the wrong tool for the hundredth. This skill records a site's network traffic once while you use it, then turns the captured requests into a standalone client (script, CLI, or library) that talks to the site's internal API directly.
4 
5The recording alone contains everything needed: agent-browser embeds text response bodies (JSON/HTML/JS) in the HAR by default, so endpoint shapes can be studied offline after the browser is closed.
6 
7## Workflow
8 
9```
101. Record     Start HAR capture, drive the flows you want in the client
112. Identify   Find the real API endpoints among the noise
123. Extract    Pull request shapes, response schemas, and auth material
134. Generate   Write the client, one function per flow
145. Verify     Call every endpoint for real before declaring done
15```
16 
17## 1. Record
18 
19```bash
20agent-browser network har start          # embeds text response bodies by default
21# ... drive the site: search, open a detail page, paginate, etc. ...
22agent-browser network har stop /tmp/site.har
23```
24 
25- Exercise **every flow the client should support**, and run each one at least twice with different inputs (two search terms, two detail pages). Diffing the recorded URLs reveals which parts are parameters.
26- If the site needs login, log in **before** starting the HAR so credentials don't land in the recording unnecessarily. The session cookies are exported separately in step 3.
27…