What Does Your AI Use Actually Cost? — Nobox Inc.
A Relational Intelligence prototype by Nobox Inc.

What does your AI use
actually cost?

We hear a lot about the high environmental costs of AI use, but I couldn't quite connect them to my own behavior. I built this tool to contextualize the water, energy, labor, and content usage behind my AI conversations so I can make informed decisions about when and why I use it.

This is the first version — please share your findings, feedback, and ideas with me at thopkins@nobox.us so I can improve it.

1
2
3
4
Step 1 of 4 — Your usage profile

How do you use AI?

Answer a few questions to understand your own habits and/or run the prompt(s) below to get data from your chat history in Claude.

Which AI tools do you use?
Select all that apply.
How many days a week do you use AI?
On a typical active day, how many conversations do you start?
One thread = one conversation, regardless of length.
How long do your conversations typically run?
Be honest — most people underestimate this.
Do you use Projects or load background context?
Projects, custom instructions, or documents that give AI context about your work.
Do you upload documents, images, or files?
What do you primarily use AI for?
Select all that apply.
Before today, how much did you think about the environmental or social cost of AI?
Optional: calibrate with real data from Claude

Run either prompt in Claude, then paste the JSON result below. Your profile will update automatically with your real data.

Prompt 1 — Analyze your last 20 conversations

Paste into a fresh Claude conversation to get a history-based usage analysis.

Use the recent_chats tool to retrieve my last 20 conversations. Then analyze the full set and return ONLY a JSON object (no preamble, no markdown fences) with these fields: conversation_count, date_range_days, dominant_types (array from: task-sprint, deep-research, collaborative-production, quick-question, document-analysis, creative-writing, technical-coding), avg_length_estimate (short/medium/long/extended/mixed), tool_use_density (none/low/moderate/high/very-high), context_dependency (low/moderate/high/very-high), project_signals (boolean), topic_domains (array up to 4 strings), power_user_signals (array 2–4 specific observations), estimated_avg_tokens_per_conv (number), portrait (2–3 sentences second-person, specific and observational, not generic).

Prompt 2 — Analyze a single conversation

Paste at the end of any conversation to get its token breakdown.

Analyze this entire conversation and return ONLY a JSON object (no preamble, no markdown fences) with: token_estimate (total input+output tokens, accounting for full history re-sent each turn, 4 chars/token), conversation_profile (short/medium/long/extended), message_count (human turns only), avg_tokens_per_exchange, dominant_content_type (text-only/code-heavy/image-included/mixed), model_used, calculation (object with method, total_chars, input_tokens, output_tokens, total_tokens, notes).

Paste the JSON from either prompt. Make sure to remove any other text from the response before pasting.

No data is stored. Everything runs in your browser.