I was tired of importing 47KB of string utilities across three services just to slugify a URL,...
I was tired of importing 47KB of string utilities across three services just to slugify a URL, camelCase a property, and base64-encode the result.
So I built TextForge: 28 text transformations behind one REST endpoint.
The problem: Every service had its own copy of slugify, camelCase, base64, extractEmails, etc. Version drift, bundle bloat, inconsistent behavior.
The solution: One API, composable pipelines, predictable JSON.
curl -X POST https://textforge.co/v1/run \
The Problem If you've built anything with GPT-4, Claude, or Llama, you've probably run...
TL;DR We had a video feature built on S3 + MediaConvert + CloudFront + a hand-rolled...
A practical guide to building content pipelines with a single multi-tool API — RSS parsing, web extraction, sitemap crawling,…
I've written a lot of scrapers. The HTML parsing part is never the interesting part — and it's always...
Every small task used to mean a new tab. JSON formatter on one site, GST calculator on another, PDF...
TL;DR: I bundled 8 commonly-needed social media utilities into a single API — username availability,...
