Blog
Field notes from building telemeter.ai.
Evidence-backed implementation notes and architecture decisions — no manufactured benchmarks, customer stories, or trend commentary.
Architecture
Why the model prices live in git, not a database
The pricing behind every telemeter.ai tool is a git-versioned file, not a table in a database — and that choice buys provenance, history, and honesty for free.
Engineering
A tool isn't done when its page renders
Shipping a tool on telemeter.ai means wiring it through six surfaces at once — page, API, MCP, sitemap, docs, and the registry. Here's the checklist, and why it's a checklist.
Notes
EU-native by architecture, and what that actually constrains
"EU-native" is easy to put on a landing page and hard to mean. Treating it as an architecture constraint instead of a badge changes what you're allowed to build.
Architecture
A public API and an MCP server for a site with no login
telemeter.ai has no accounts, no dashboard, and no database of users — and a full REST API, an MCP server, and clean markdown for every page. Here's why building for agents came first.
Engineering
When a tool doesn't know, it should say so
Why telemeter.ai's free tools show 'pending' and 'unknown' instead of a confident wrong number — and the registry that makes that possible.
Notes
What this blog is, and is not
Evidence-backed implementation notes and architecture decisions — not manufactured benchmarks, customer stories, or trend commentary.