Cost tracking across runs in LangChain - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does LangChain track API call costs across multiple runs?

Consider a LangChain application that uses an OpenAI model. How does LangChain keep track of the total cost of API calls when the application runs multiple times?

A LangChain uses environment variables to store cumulative cost data between runs.

B LangChain writes cost data to a local file after each run and reads it back on the next run.

C LangChain resets cost tracking after each run and does not accumulate costs automatically.

D LangChain stores cost data in a persistent memory object that accumulates costs across runs.

💡 Hint

Think about whether LangChain automatically saves cost data between separate program executions.

LangChain tracks costs during a single run in memory but does not persist cost data across separate runs automatically. To track costs across runs, you need to implement your own persistence.

❓ state_output

intermediate

What is the total cost after two runs with LangChain's built-in cost tracker?

You run a LangChain app twice. Each run makes 3 API calls costing $0.02 each. LangChain's cost tracker resets on each run. What is the total cost reported after the second run?

A $0.12

B $0.00

C $0.04

D $0.06

💡 Hint

Calculate cost per run and consider if costs accumulate across runs automatically.

Each run costs 3 calls × $0.02 = $0.06. Since LangChain resets cost tracking each run, after the second run the reported cost is $0.06, not cumulative $0.12.

🔧 Debug

advanced

Why does the LangChain cost tracker show zero after restarting the app?

You use LangChain's cost tracker to monitor API usage. After restarting your app, the cost tracker shows zero. What is the most likely reason?

A The cost tracker only tracks costs in memory and does not persist data between runs.

B The API key was invalidated, so no calls were made after restart.

C LangChain automatically clears cost data on restart for security reasons.

D The cost tracker requires manual reset after each run to show costs.

💡 Hint

Consider how LangChain stores cost data internally.

LangChain's cost tracker keeps data in memory only. Restarting the app clears memory, so cost data resets to zero.

🧠 Conceptual

advanced

How to implement persistent cost tracking across LangChain runs?

You want to track total API costs across multiple LangChain runs. Which approach best achieves this?

A Save cost data to a database or file after each run and load it at start.

B Rely on the API provider's dashboard to track costs externally.

C Store cost data in a global variable inside the LangChain library.

D Use LangChain's built-in persistent cost tracker that auto-saves data.

💡 Hint

Think about how to keep data between separate program executions.

LangChain does not persist cost data automatically. Saving cost info externally (database or file) and loading it on start is the correct way to track costs across runs.

📝 Syntax

expert

What error occurs when accessing cost data before any API calls in LangChain?

Given this snippet:
from langchain.callbacks import get_openai_callback with get_openai_callback() as cb: print(cb.total_cost)
What happens if no API calls are made inside the with block?

A Raises AttributeError because total_cost is undefined.

B It prints 0.0 without error.

C Raises RuntimeError because no API calls were tracked.

D Prints None because total_cost is not set.

💡 Hint

Consider default values of cost tracking attributes before usage.

The total_cost attribute initializes to 0.0 even if no API calls occur, so printing it outputs 0.0 without error.