Question: roadmap for official Kling and Volcengine Jimeng video providers?

[xucailiang]

Question

Would official direct integrations for Kling AI and Volcengine Jimeng video generation fit the OpenMontage provider roadmap?

OpenMontage already has strong coverage through gateways such as fal.ai, KIE.AI, MuAPI, Higgsfield, and HeyGen, but I could not find an existing issue or PR specifically tracking direct official-provider integrations for:

• Kling official API, separate from the current fal.ai-backed kling_video tool
• Volcengine Jimeng official API, separate from generic Seedance/gateway routes

This issue is mainly to check maintainer direction before anyone opens an implementation PR.

Official API references

Kling AI official API

Relevant docs:

• Authentication: https://kling.ai/document-api/api/get-started/authentication
• Text-to-video API: https://kling.ai/document-api/api/video/3-0-omni/text-to-video
• Concurrency rules: https://kling.ai/document-api/api/get-started/concurrency-rules
• Video pricing: https://kling.ai/document-api/pricing/base/video

Why it appears integration-ready:

• Official API domain is documented: https://api-singapore.klingai.com
• Authentication is simple Bearer API key auth: Authorization: Bearer <token>
• Text-to-video uses POST /v1/videos/text2video
• Task polling is documented via GET /v1/videos/text2video/{task_id}
• Callback URL support is documented
• Pricing and concurrency behavior are documented
• Current OpenMontage kling_video appears to use fal.ai, so an official provider could be exposed separately, e.g. kling_official_video, without replacing the gateway-backed route

Volcengine Jimeng official API

Relevant docs:

• Jimeng video generation 3.0 Pro API: https://www.volcengine.com/docs/85621/1777001
• Jimeng video pricing: https://www.volcengine.com/docs/85621/1544715

Why it appears integration-ready:

• Official API endpoint is documented: https://visual.volcengineapi.com
• Submission/query flow is documented through:
  • Action=CVSync2AsyncSubmitTask
  • Action=CVSync2AsyncGetResult
  • Version=2022-08-31
• Service identifier is documented, e.g. req_key=jimeng_ti2v_v30_pro
• The API supports text-to-video and first-frame image-to-video
• Outputs include task_id, status, and video_url
• Pricing and concurrency limits are documented
• Authentication uses Volcengine AK/SK request signing, with Region=cn-north-1 and Service=cv, which is more involved than Kling's Bearer key flow but still an official documented integration path

Possible direction

If this fits the roadmap, the least surprising shape might be two separate direct-provider tools rather than changing existing gateway-backed tools:

• kling_official_video
• jimeng_video or volcengine_jimeng_video

That would keep provider choice explicit and auditable, while preserving the existing gateway integrations.

[calesthio]

@xucailiang These will be valuable additions to OpenMontage. Would you be open to create a feature PR for adding these two to OpenMontage?

[xucailiang]

Thanks! Yes, I can work on this. I’ll start with the official Kling API provider first and keep it separate from the current fal.ai-backed kling_video tool. Jimeng needs Volcengine AK/SK signing, so I’ll handle that as a separate follow-up PR.

[yiyabo]

Hi @xucailiang, just following up on the Jimeng part — are you still planning to work on it?

I have relevant experience from two provider integration PRs (#240 DashScope, merged; #297 MiniMax Token Plan, in final review) and already have Volcengine API access configured (using Doubao TTS in OpenMontage). I am familiar with the BaseTool contract, idempotency key patterns, and the submit-poll-download flow that calesthio has been reviewing.

If you are not planning to pick up Jimeng in the near term, I would be happy to take it on. The Volcengine AK/SK signing is a bit involved, but I can start by researching the auth requirements and getting it running locally before submitting a PR.

[xucailiang]

Hi @yiyabo, thanks for following up. Yes, please feel free to take the Jimeng / Volcengine part.

I am currently working on the Kling official provider side, so Jimeng is open from my side.