I write production software — automations, API integrations, and libraries other people can build on.
A lot of my work is getting systems to talk to services that never published an interface: working
out undocumented endpoints and auth flows, handling TLS and browser fingerprinting, then wrapping
what I learn into something reusable. ezhttp came directly out of that. The rest of my time goes
to automation and to the infrastructure underneath AI agents.
I pick the language to fit the problem — Go for concurrency and a single tight binary, TypeScript for services and pipelines, Python where the data tooling already lives. Whatever the stack, the same things matter: typed boundaries, real test suites, and as few dependencies as I can get away with.
|
Built straight on |
Provider-agnostic LLM runtime. Tool schemas are derived from Go structs by reflection, so a plain typed function becomes a model capability. Agents compose — any agent can be handed to another as a tool. Parallel dispatch, context compaction under token pressure, and typed lifecycle events carrying token usage and per-model cost. |
Portable capabilities for coding agents: a codebase indexer, a browser-automation driver and a research CLI, packaged as skills that carry between machines. |
| API reverse engineering | Undocumented endpoints, auth flows, TLS and browser fingerprinting, anti-bot surfaces |
| Automation | Browser automation, structured scraping, data pipelines, internal tooling |
| Libraries & services | Dependency-light packages, typed public APIs, tested and documented |
| Agent infrastructure | Tool-calling loops, parallel dispatch, context management, multi-agent composition |
| LLM systems | Retrieval, judge models and quality gating, tracing, per-request cost attribution |
Happy to talk about API work, automation, or anything agent-shaped. Reach me at 0xbitshot@gmail.com.
~ 0xACE3
