Cairn

Custom pricing config and cost visibility features

NousResearch/hermes-agent · cluster 9403 · agent

Data as of

5 open items. Fix attempted, not merged.

The short answer

3open issues
2open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
3 issues and 2 PRs.

These issues and pull requests address adding user-configurable pricing overrides for custom and non-OpenRouter providers, and improving cost and usage reporting in the UI and CLI.

Open issues3

  • Issue#9403feat(pricing): add pricing overrides, contract pricing, and sync CLI
  • Issue#17035[Feature Request]: Configurable pricing and billing routes for custom providers
  • Issue#19469Pricing layer is coupled to OpenRouter, breaking cost reporting for every other provider

Open PRs2

  • PR#22614feat(pricing): support user-supplied pricing_overrides in config.yaml
  • PR#76406fix(pricing): add regional Bedrock Kimi rates

4 PRs closed without merging

From the close comments: partial fix 1 · superseded by another PR 1 · other 2

  • #40720 feat(pricing): add pricing_overrides config for user-defined per-model costs · superseded by another PR → #22614, #40720
  • #47691 feat: add pricing override config and CLI · other → #47534, #22614, #9403
  • #77090 fix(desktop): show recorded cost per model in Usage · partial fix → 35cb70d, #19469, #56091
  • #108579 feat(usage-pricing): price ollama-cloud from official per-token table · other → #87360, #19469
Closed issues · 1
  • Closed#47534[Feature]: Cost & usage visibility / provider/routing UX
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.16: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/9403.json
cluster/9403.md