Cryptograss:Moods/usage/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
m Merged, says GitHub: https://github.com/cryptograss/magenta/pull/235 |
#usage: #239 and an OpenRouter key limit (via update-page on MediaWiki MCP Server) |
||
| Line 28: | Line 28: | ||
kind: decision | kind: decision | ||
note: Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly. | note: Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly. | ||
- task: Merge magenta#239 (routers neither offered nor run), then redeploy hunter | |||
who: justin | |||
kind: merge | |||
link: https://github.com/cryptograss/magenta/pull/239 | |||
- task: Set a daily spend limit on the OpenRouter key (it has none) | |||
who: justin | |||
kind: config | |||
link: https://openrouter.ai/settings/keys | |||
</todo> | </todo> | ||
Revision as of 14:49, 28 October 2026
- ☐
- ☐
- ☐End-to-end tests of the cost path (Pi event to stored row to page), including routers
- ☐Daily check of the page's OpenRouter total against OpenRouter's billed total (/api/v1/key usage_daily)
- ☐Decide whether to backfill OpenRouter's billed cost onto past routed Pi calls (writes to the record)Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly.
- ☐
- ☐