chore: update stepfun pricing#2905
Merged
rekram1-node merged 1 commit intoJun 29, 2026
Merged
Conversation
I'll start by inventorying the stepfun provider directory and finding the Narev provider mapping in parallel.
The Narev provider_id is `stepfun`, matching the directory. Let me read all the model TOML files and fetch Narev prices in parallel.
Now let me analyze the data. I have Narev pricing for two models. Let me check the metadata file for `step-3.7-flash` since that provider TOML uses `base_model`.
Now I have a complete picture. Let me analyze the Narev pricing against the catalog:
**Narev pricing (per token → per million tokens):**
| Model | input | output | cache_read |
|---|---|---|---|
| `step-3.5-flash` | 1e-7 → 0.1 | 3e-7 → 0.3 | 2e-8 → 0.02 |
| `step-3.7-flash` | 2e-7 → 0.2 | 1.15e-6 → 1.15 | 4e-8 → 0.04 |
**Comparison with catalog:**
- `step-3.5-flash`: catalog has input=0.1, output=0.3, cache_read=0.02 → **all match, no change**
- `step-3.7-flash`: catalog has input=0.19, output=1.13, cache_read=0.04 → **input and output differ, needs update**
- `step-2-16k`: no Narev pricing → skip
- `step-1-32k`: no Narev pricing → skip
- `step-3.5-flash-2603`: Narev pricing is null (enterprise only) → skip
Only `step-3.7-flash.toml` needs updating. Since it uses `base_model` and inherits `last_updated` from the metadata file, I'll add `last_updated` to the provider TOML to reflect the cost change (today: 2026-06-29).
Let me verify the edit:
The edit is correct. Let me verify my conversions one final time against the raw Narev values:
- `step-3.7-flash` prompt: `2e-7` × 1,000,000 = **0.2** ✓ (was 0.19)
- `step-3.7-flash` completion: `0.00000115` × 1,000,000 = **1.15** ✓ (was 1.13)
- `step-3.7-flash` input_cache_read: `4e-8` × 1,000,000 = **0.04** ✓ (unchanged)
## Summary
**Provider checked:** `stepfun` (Narev `provider_id`: `stepfun` — exact match)
**Files changed (1):**
- `providers/stepfun/models/step-3.7-flash.toml` — updated `input` 0.19 → 0.2 and `output` 1.13 → 1.15 (per Narev prompt `2e-7`/token and completion `1.15e-6`/token). `cache_read` (0.04) was already correct. Added `last_updated = "2026-06-29"` to the provider TOML since it uses `base_model` and inherits `last_updated` from the metadata file (which is out of scope to edit).
**Files skipped (4):**
- `step-3.5-flash.toml` — Narev pricing (input 0.1, output 0.3, cache_read 0.02) exactly matches the catalog; no change needed.
- `step-3.5-flash-2603.toml` — Narev returns `pricing: null` ("enterprise plans only"); skipped per scope rules.
- `step-2-16k.toml` — no matching Narev model/pricing row; could not map safely.
- `step-1-32k.toml` — no matching Narev model/pricing row; could not map safely.
**Could not map safely:** `step-2-16k` and `step-1-32k` have no public Narev pricing entries, so they were left unchanged.
oskarkocol
commented
Jun 29, 2026
| input = 0.19 | ||
| output = 1.13 | ||
| input = 0.2 | ||
| output = 1.15 |
Contributor
Author
There was a problem hiding this comment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Inspired by: Aiden's #2902