feat: doubao-seedance-2-0-260128支持按分辨率区分计费

[feitianbubu]

⚠️ 提交说明 / PR Notice

修复: #5266

sd2.0, 之前只根据是否包含视频url区分计费
新增了1080p分辨率后, 又增加了根据是否1080p区分计费

📝 变更描述 / Description

增加是否1080p计费配置, 与是否包含视频url配置成价格map
等后续将视频也支持表达式计费后可不再通过价格map写死 @Calcium-Ion

📸 运行证明 / Proof of Work

51/46=1.1087 比率正确

Summary by CodeRabbit

• Chores
  • Updated billing estimation logic for video input pricing. The system now factors in output resolution when calculating video input cost adjustments, providing more granular pricing accuracy based on both resolution and video presence in requests.

[coderabbitai]

Walkthrough

The Doubao billing estimator is updated to compute video-input discounts based on output resolution (1080p vs. non-1080p) and video presence. The pricing table replaces a fixed ratio map, and EstimateBilling now extracts resolution from metadata to apply resolution-aware discount calculation.

Changes

Doubao Video Input Pricing by Resolution

Layer / File(s)	Summary
Resolution-aware video pricing table relay/channel/task/doubao/constants.go	The pricing table is introduced with entries keyed by (resolution, hasVideo). The GetVideoInputRatio function signature changes from (modelName string) to (modelName, resolution string, hasVideo bool) and computes a multiplier relative to the configured base (no-video, non-1080p) price for each model. Missing base returns (0, false); missing specific entries default to (1.0, true). The strings import is added for case-insensitive resolution detection.
EstimateBilling resolution extraction relay/channel/task/doubao/adaptor.go	TaskAdaptor.EstimateBilling extracts resolution from metadata and calls GetVideoInputRatio(info.OriginModelName, resolution, hasVideo) with all three parameters. The function returns {"video_input": ratio} only when a valid ratio exists and is not 1.0.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• QuantumNous/new-api#1951: Updates to the Doubao adaptor and constants build on the Doubao Video support introduced in #1951.

Suggested reviewers

• seefs001
• Calcium-Ion

Poem

🐰 A table of prices, now resolution-wise,
Where 1080p and video are counted with eyes,
The estimator hops through metadata springs,
Finding the resolution that pricing now brings,
Multipliers dance where the base prices lay.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title accurately describes the main change: adding resolution-based billing differentiation (1080p vs non-1080p) for the doubao-seedance-2-0 model, which aligns with the code changes that refactored billing ratio calculation to accept and use resolution parameter.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

relay/channel/task/doubao/constants.go (1)

40-45: 💤 Low value

Document/validate the base-price ↔ ModelRatio coupling.

The multiplier is price/base where base is the hard-coded 480p/720p no-video price (46.0 / 37.0). Billing is only correct if the admin-configured ModelRatio equals that base. The comment notes this, but it's a silent assumption: if ModelRatio is set to any other value the resolution/video multipliers will be proportionally wrong. Consider surfacing this expectation in operator docs.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@relay/channel/task/doubao/constants.go` around lines 40 - 45,
GetVideoInputRatio assumes admin-configured ModelRatio equals the hard-coded
base price (videoPriceTable lookup using videoPriceKey{}), which silently breaks
billing if ModelRatio differs; update GetVideoInputRatio (and related
initialization) to validate that ModelRatio matches the expected base
(videoPriceTable[modelName][videoPriceKey{}]) and either compute multipliers
relative to the configured ModelRatio or emit a clear runtime warning/error when
they diverge; reference videoPriceTable, videoPriceKey{}, base and ModelRatio so
the code locates the check and handle the mismatch by logging an explicit error
or adjusting calculations to use the configured ModelRatio as the denominator.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@relay/channel/task/doubao/constants.go`:
- Around line 40-45: GetVideoInputRatio assumes admin-configured ModelRatio
equals the hard-coded base price (videoPriceTable lookup using videoPriceKey{}),
which silently breaks billing if ModelRatio differs; update GetVideoInputRatio
(and related initialization) to validate that ModelRatio matches the expected
base (videoPriceTable[modelName][videoPriceKey{}]) and either compute
multipliers relative to the configured ModelRatio or emit a clear runtime
warning/error when they diverge; reference videoPriceTable, videoPriceKey{},
base and ModelRatio so the code locates the check and handle the mismatch by
logging an explicit error or adjusting calculations to use the configured
ModelRatio as the denominator.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 80877c64-7592-44a0-a741-af98150f6ef9

📥 Commits

Reviewing files that changed from the base of the PR and between 00d23ab and 09fe119.

📒 Files selected for processing (2)

• relay/channel/task/doubao/adaptor.go
• relay/channel/task/doubao/constants.go

[huhu-tiger]

前端模型广场 显示还是没有区分计费

[zhuiyue132]

需要这个feat，尽快合并