Undocumented API Mapper
Inspects browser traffic, maps request flows, payloads, auth edges, pagination, and hidden endpoints. Output is a stable client, notes, and a system another dev can maintain.
I build high-leverage technical systems: reverse engineering, web automation, scraping, API mapping, browser tooling, and custom apps for repetitive digital work. Websites are easy. The interesting work is making hidden flows legible, automating ugly workflows, and turning fragile manual tasks into sharp tools.
The technical lab of Offset Zero. Reverse engineering, automation, extraction, browser tooling, and custom systems for repetitive digital work.
Inspects browser traffic, maps request flows, payloads, auth edges, pagination, and hidden endpoints. Output is a stable client, notes, and a system another dev can maintain.
Turns repeated browser work into scripts, extensions, local dashboards, or controlled automations. Built for tasks too specific for SaaS and too annoying to keep doing by hand.
Extracts structured data from JS-heavy sites, directories, dashboards, and awkward public sources. Focus is not "scrape page"; it is clean output, repeatable runs, and failure visibility.
Finds public business pain, ranks buying signals, resolves websites/contact paths, and drafts compact reply angles. A lead machine built around proof instead of spam.
Tokenizer tools, prompt grids, local model consoles, eval helpers, and coding interfaces. Built for people who need control and feedback loops, not a shiny chatbot skin.
Small apps, dashboards, one-file tools, admin panels, and workflow UIs for repetitive work. Web apps and websites are table stakes; the value is in the system behind the interface.
Inspect requests, browser behavior, data shape, edge cases, and the exact point where the workflow stops being reliable.
A script, client, extractor, extension, sample output, or prototype that proves the technical path before scope gets heavy.
Add the boring but critical pieces: retries, logs, checkpoints, validation, config, and a clean handoff path.
Documented, handoff-ready, and editable by the next person who opens it. No black boxes.
Best fit: a site that hides data, a workflow trapped in browser tabs, an undocumented endpoint, a repetitive task, or an internal tool that needs to exist.
Send the target, what you need out of it, and what "working" means. Specific beats polished.