dsh-peakrate

Configuration

Configuration lives in the profile's cordis.patch.yml:

- id: peakrate
  config:
    # provider id → catalog provider name
    providerAliases:
      my-gateway: DeepSeek
    # provider-scoped model patterns; first match wins
    modelMappings:
      - provider: my-gateway
        match: "^deepseek-v4"
        profile: deepseek-v4
      - provider: my-gateway
        match: "glm-5\\.3-flash"
        matchIsRegex: true
        profile: zai-glm-5-3-flash
    # fetch interval; 0 disables the background refresh
    refreshIntervalHours: 24
    catalogUrl: https://offpeakclock.com/pricing.json
    cachePath: ~/.dsh/peakrate/pricing.json

Option	Default	Description
enabled	true	Background refresh switch. Also editable in the coverage panel.
refreshIntervalHours	24	Hours between catalog refreshes. 0 disables it. Also editable in the panel.
catalogUrl	the public catalog	Remote catalog URL.
cachePath	~/.dsh/peakrate/pricing.json	On-disk cache of the last successful fetch.
providerAliases	built-in table	Extra provider id → catalog provider mappings. Yours win over the built-ins.
modelMappings	built-in table	Extra provider + model pattern → profile mappings. Yours are tried first.
customProfiles	[]	Additional profiles: override a bundled entry by id, or add a new one. They take part in badge judgement too.

modelMappings entries are prefix matches by default; set matchIsRegex: true for a regular expression. Invalid regexes do not throw — they simply never match.

customProfiles fully applies, badges included. The host serves its merged catalog over /peakrate/catalog, so a custom profile takes part in badge judgement exactly like a bundled one — either overriding a bundled entry by id, or adding a new one. Verified: pointing deepseek-v4 at a custom profile with peak: 9× changes both the served catalog and the badge to 9×.