P
Peekr Cloud
DemoAcme Agents

Costs

Cost intelligence

Where the money goes.

Demo

Spend (30d)

$18.84

all LLM calls

Spend (24h)

$18.84

247 queries

Cost / query

$0.076

vs 7 days ago

Projected / mo

$565.24

30d daily avg × 30

Daily spend · 30 days

$18.84 total
$0$4.71$9.42$14.13$18.84Jun 22Jun 29Jul 6Jul 13MonTue

Attribution · last 24h

By operation

anthropic › messages › create336 calls
$17.75
94%
2.5k
avg
openai › chat › completions › create195 calls
$1.09
6%
876
avg
Cost Avg tokens / call

By tenant

TenantQueriesLLM callsCost / queryTotal cost
acme
claude-opus-4-7
117278$0.080
$9.4150%
globex
claude-opus-4-7
79151$0.070
$5.5329%
soylent
claude-opus-4-7
51102$0.077
$3.9021%

By model · last 24h

ModelRequestsPromptOutputTotal tokensp50Cost
claude-opus-4-7265537.6k105.1k642.7k1507ms
$15.95
claude-sonnet-4-67198.7k100.8k199.5k1504ms
$1.81
gpt-4o135126.7k30.0k156.7k1173ms
$1.08
gpt-4-mini6010.1k3.9k13.9k1435ms
$0.0038
Total$18.84

Savings opportunities

up to $180.32/mo identified
Cascaderag.answermedium effort

"rag.answer" fans out into 45 "openai.chat.completions.create" calls per trace

1 trace in 24h · up to 45 "openai.chat.completions.create" calls in one trace (avg 45) · ~$33/mo on these calls

Fan-out
45×
1 trace
NowAfter fix

45× openai.chat.completions.create

~1 batched call

Seen in 1 trace in the last 24h

One "rag.answer" produces ~45 "openai.chat.completions.create" calls — almost always a per-retrieved-item LLM call. Batch them into one request, or cap the loop. 45 completions for a single answer is a retrieval/ranking bug, not a model problem.

fix.py
# One operation made N LLM calls in a single trace.
# Batch the per-item calls into one request:
inputs = [c.text for c in retrieved[:TOP_K]]   # e.g. TOP_K = 8
client.embeddings.create(model="text-embedding-3-small", input=inputs)

# Or collapse a per-chunk loop into a single completion:
context = "\n\n".join(c.text for c in retrieved[:TOP_K])
client.chat.completions.create(messages=[{"role": "user", "content": context}])
Model swapsupport_botlow effort

Route short support_bot queries to gpt-4o-mini

110 of 124 support_bot calls in 24h were under 600 input tokens on claude-opus-4-7.

Save / mo
$74
99% on feature
Now:claude-opus-4-7110 calls/24hgpt-4o-mini

Short prompts don't need a frontier model. Add a length check at the dispatcher: if tokens_input < 600, use gpt-4o-mini; otherwise fall back. Quality drop is typically negligible at this length.

fix.py
# Route short prompts to cheaper model
model = "gpt-4o-mini" if tokens < 600 else "gpt-4o"
client.chat.completions.create(model=model, ...)
Fine-tunesupport_bothigh effort

Fine-tune for support_bot (high-volume on premium model)

124 support_bot calls in 24h, 100% on premium models.

Save / mo
$74
75% on feature

At this volume a fine-tuned smaller model typically reaches ≥95% of frontier quality on a constrained task. Sample 5k spans, fine-tune gpt-4o-mini, A/B against current. Training cost recovers in ~5 days at current spend.

fix.py
# Export training data from Peekr spans
# then fine-tune gpt-4o-mini on your task