Quick answer
This Cost per user processing runs locally and does not upload; browser extensions can still read the page. Cost per user = total token cost / active users; segment by usage intensity.
Why it matters
Local processing reduces upload risk but is not absolute security.
Power users raise cost.
Step by step
- Measure input, output and retry tokens per user/task.
- Separate cache, batch, embeddings and fine-tuning costs.
- Use 30 days of real requests for cost per user, then margin.
- Model prices change; baseline from official pricing pages and record the date.
Common mistakes
- Estimating from input tokens only; output often costs more.
- Forgetting retries, failures and tool calls.
- Assuming cache hits by default.
- Using stale prices for long-term margin.
Checklist
- Input/output/cache/retry tokens are tracked separately.
- Batch/async fit and latency requirements are clear.
- Embeddings/fine-tuning/image/audio are separate.
- Cost per user and margin use real usage.
- Price date and fallback model are documented.
Key facts
- Power users raise cost.
- Segment by task.
- Compare with revenue.
FAQ
Does Cost per user processing upload my files?
This Cost per user processing runs locally and does not upload; browser extensions can still read the page. Cost per user = total token cost / active users; segment by usage intensity.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: Nops