Skip to content

Update GreenPT: cached-token rates, compression variants, kimi-k3 - #3927

Open
Casburggraaf wants to merge 4 commits into
anomalyco:devfrom
Casburggraaf:update-greenpt-catalog
Open

Update GreenPT: cached-token rates, compression variants, kimi-k3#3927
Casburggraaf wants to merge 4 commits into
anomalyco:devfrom
Casburggraaf:update-greenpt-catalog

Conversation

@Casburggraaf

Copy link
Copy Markdown
Contributor

Refreshes the GreenPT catalog added in #3726. Four things changed on our side since that merged: prompt caching shipped, nine compression ids went GA, one model was withdrawn upstream, and a few list prices moved.

No entries are removed and nothing outside providers/greenpt/ is touched. Costs remain USD, converted from GreenPT's EUR list price at 1.14 USD/EUR; files whose price was re-verified for this update carry the later capture date in their top-of-file comment, untouched files keep the original one.

1. Cached prompt tokens (cost.cache_read)

GreenPT now bills prompt-cache hits at a reduced input rate. cost.cache_write is omitted rather than zeroed: cache writes are not charged at all.

entry EUR cached cache_read
glm-5.2 and all nine compression variants 0.275 0.3135
kimi-k3 0.825 0.9405
kimi-k2.6 0.22 0.2508
kimi-k2.7-code 0.165 0.1881
minimax-m2.5 0.055 0.0627

These are the only models that discount cache hits; every other GreenPT entry bills input at its normal rate and is left without the field.

2. Price corrections

Our upstream list prices were re-read from the gateway's own catalogue rather than its marketing page, which had been quoting higher figures:

entry field was now EUR
kimi-k2.6 input 0.828 0.7524 0.66
kimi-k2.6 output 4.389 4.275 3.75
kimi-k2.7-code input 0.941 0.9006 0.79
minimax-m2.5 input 0.188 0.1938 0.17

glm-5.2 prices are unchanged; it only gains cache_read. Untouched entries were deliberately not re-rounded, to keep the diff limited to real changes.

3. New: kimi-k3

GA on GreenPT at 3.762 / 18.81, cached 0.9405. Declared through base_model = "moonshotai/kimi-k3", inheriting the 1,048,576 context. GreenPT serves it with text and image input, so the inherited video modality is overridden away, consistent with how kimi-k2.6 is already declared here.

4. New: nine compression variants of glm-5.2

glm-5.2-{caveman,honey,ponytail} each in -lite, unsuffixed and -ultra. They are the same upstream model carrying a built-in output-compression ruleset: caveman compresses prose, ponytail compresses generated code, honey compresses both, and the suffix selects intensity. Same price per token (including the cached rate) and the same context; the saving comes purely from generating fewer output tokens.

All nine are declared through base_model = "zhipuai/glm-5.2", so their cost and limits cannot drift from the base entry.

5. Deprecated: kimi-k2.6-fast

Withdrawn by the upstream provider; GreenPT no longer serves the id and requests for it fail. Marked status = "deprecated" rather than deleted, so existing configurations still resolve. Its prices are untouched.

Reasoning controls

Unchanged from #3726 and applied to the new entries too: the documented effort enum stays limited to the GreenPT-hosted models whose control is documented first-party (gemma4, green-r, green-r-raw). kimi-k3 and all nine variants are pass-through endpoints whose accepted values we have not verified, so they declare reasoning_options = [].

Verification

bun validate is green. bun test shows no failures beyond the 3 pre-existing packages/sdk/src/snapshot.js module-resolution errors that also fail on a clean dev. Diffing the resolved catalog against the published models.dev/api.json confirms exactly the 10 additions, the 4 repriced fields, the 15 cache_read values and the one status change, with nothing else moved.

Evidence

Claim Source
Every cached rate, and which models discount cache hits https://docs.greenpt.ai/prompt-caching
The nine compression ids, their families and intensities https://docs.greenpt.ai/compression-models
Token prices, context windows, modalities https://docs.greenpt.ai/model-cards
Full price table including the cached-input column https://docs.greenpt.ai/pricing
reasoning_effort values on GreenPT-hosted models https://docs.greenpt.ai/chat-completion

GreenPT now bills prompt-cache hits at a reduced input rate on these models, so
each gains cost.cache_read. Cache writes are not charged, so cost.cache_write is
omitted rather than set to zero.

  glm-5.2         cache_read 0.3135
  kimi-k2.6       cache_read 0.2508
  kimi-k2.7-code  cache_read 0.1881
  minimax-m2.5    cache_read 0.0627

The same pass also picks up list-price corrections: kimi-k2.6 moves to
0.7524 / 4.275, kimi-k2.7-code input to 0.9006, and minimax-m2.5 input to
0.1938. glm-5.2's own prices are unchanged.

Rates: https://docs.greenpt.ai/prompt-caching and https://docs.greenpt.ai/pricing
Kimi K3 is generally available on GreenPT at 3.762 input, 18.81 output and
0.9405 for cached prompt tokens. GreenPT serves it with text and image input,
so the inherited video modality is overridden away.

https://docs.greenpt.ai/model-cards
GreenPT serves nine ids that are glm-5.2 carrying a built-in output-compression
ruleset: three families (caveman compresses prose, ponytail compresses generated
code, honey compresses both) at three intensities (-lite, unsuffixed, -ultra).

They are the same upstream model at the same price per token, including the same
cached rate, and return fewer output tokens. Each is declared through base_model
so cost and limits cannot drift from glm-5.2.

https://docs.greenpt.ai/compression-models
The upstream provider withdrew this model and GreenPT no longer serves the id,
so requests for it now fail. Marked deprecated rather than deleted so existing
configurations still resolve against the catalog.
@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

No actionable findings.

@rekram1-node

Copy link
Copy Markdown
Collaborator

Are you sure reasoning efforts arent supported at all here? No toggles either? Seems inaccurate to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants