Glubean Blog

Product writing for the workflow behind Glubean

Essays, migration guides, and workflow notes about API behavior as executable assets: source-authored checks that survive local runs, CI, Cloud evidence, docs, and AI agents.

The API ecosystem quietly normalized fragmented workflows. AI made the gap more visible, not less. It is time to care about API tooling again.

API Tooling Didn't Get Better. We Just Lowered Our Expectations

API exploration usually dies as throwaway work. This post explains why I wanted the same file to survive exploration, verification, and CI.

Why I Replaced Postman with a TypeScript Workflow in VS Code

What this blog covers

Workflow shifts behind Glubean, not just feature announcements
Practical paths from Postman, cURL, scratch files, and ad hoc scripts
Notes on AI-assisted authoring, result files, traces, and source-first debugging

If you want the fastest path into the product instead of the essays, start with How Glubean Works or Start Here.