Cost defaults
Cost defaults let you set your own per-token AI prices so Waydev can estimate spend for AI tools that report token usage but no cost.
Every AI integration sends Waydev token counts, but not all of them send a dollar figure. Without cost defaults, spend for those tools shows as unavailable. Once you set your rates, Waydev prices their token usage for you.
Cost defaults never override a tool that reports its own cost. For those tools, Waydev always shows the real figure from the vendor.
The four token types
| Field | What it prices |
|---|---|
| Input tokens | Tokens sent to the model — your prompt |
| Output tokens | Tokens the model generates in reply |
| Cache read tokens | Tokens served from the model's prompt cache |
| Cache write tokens | Tokens written into the model's prompt cache |
How Waydev calculates cost
For each figure it prices — a tool, a team, a developer, a period — Waydev works through three cases in order:
- Reported — the integration sent a real cost. Waydev shows the vendor's figure and ignores your cost defaults.
- Estimated — no cost was reported, but tokens were recorded. Waydev prices those tokens using your cost defaults.
- Not available — no cost was reported and no tokens were recorded. No cost is shown.
Where your rates are used
- AI Impact → Token usage — Monthly spend, Cost per PR, the by-tool table, and the team, developer, and attribute breakdowns
- Vendor ROI — the per-developer cost column for OpenCode
Updated 40 minutes ago