TokenWatch started before the WebMCP challenge as a practical LLM pricing calculator. I kept running into the same operational problem: "Which model is cheapest?" is meaningless without modeling a real workload—token volume, input versus cached mix, output ratios, provider differences, and hard constraints like Zero Data Retention.

I come to this without an engineering or coding background. My background is in commercial banking, where cost structure, margin impact, and decision defensibility matter far more than technology for its own sake. I built TokenWatch using modern AI coding tools to make model-pricing decisions clear and legible for business operators, not just developers reading API rate cards.

During the submission period, I implemented a comprehensive WebMCP layer across TokenWatch's text, media, and benchmark calculators. Instead of an agent blindly guessing from a rendered table or web search, it operates the exact same live calculator the user sees. The agent can configure token mix, apply ZDR or benchmark thresholds, inspect ranked results, compare candidates, explain why a model won, and generate an auditable share link.

The key challenge was reliability. Rather than brittle click-emulation, TokenWatch exposes clean tools tied to the calculator's state engine. Every tool references stable {provider, id} identities rather than changing table ranks, and state modifications immediately return fresh view snapshots so human and agent stay perfectly synchronized.

Built With

Share this project:

Updates

Submission history