---
title: "Discussion on \"Cost & Latency Tracking — What the Token Counts Were Telling Me All Along\" | Hashnode"
description: "Discussion on \"Cost & Latency Tracking — What the Token Counts Were Telling Me All Along\". Every module up to this point used the same streaming events without ever reading two fields that were there the entire time. message_start and message_delta carry token usage on every single stream —"
url: "https://hashnode.com/posts/cost-latency-tracking-what-the-token-counts-were-telling-me-all-along/6a349018aaf238351becba9c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Cost & Latency Tracking — What the Token Counts Were Telling Me All Along](https://blog.davidhahn.co/cost-latency-tracking-what-the-token-counts-were-telling-me-all-along?utm_source=hashnode&utm_medium=feed)

Every module up to this point used the same streaming events without ever reading two fields that were there the entire time. message\_start and message\_delta carry token usage on every single stream —

Jun 19 · 6 min read · blog.davidhahn.co  
Read the article

## Written by

[David Hahn](https://hashnode.com/@davidhahn)

@davidhahn · Chicago, USA

  
[View profile](https://hashnode.com/@davidhahn)

10+ years in software engineering, with deep expertise in frontend. Now going deep on LLMs — streaming, RAG, tool use, and everything in between.

Senior engineer with deep roots in React, TypeScript, and production-scale UI — including 4 years at Apple. Now focused on applied AI engineering: working hands-on with LLM APIs, RAG pipelines, agents, and the full stack of tooling that modern AI products are built on. Writing here to document the build, share what's non-obvious, and connect with teams working on hard AI problems.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
