API protocol

Kling-style asynchronous media API

Direct answerKling text-to-video and image-to-video fields, states and artifacts depend on the actual channel. Tuzi-specific paths cannot be assumed to work here. Check marketplace endpoints and the installed task plugin contract before integration.

Updated · Reviewed

Scope

Kling text-to-video and image-to-video fields, states and artifacts depend on the actual channel. Tuzi-specific paths cannot be assumed to work here. Check marketplace endpoints and the installed task plugin contract before integration.

Select an endpoint and model

There is no complete OpenFox integration example for this protocol yet. Consult the API directory and do not turn a provider or Tuzi example into an OpenFox request by changing its hostname.

The marketplace owns exact model IDs, endpoint support, group access and prices. Similar model names do not establish identical parameters or permissions. Provider documentation explains capabilities, not whether a model is enabled or priced on this site. Complete examples and route-only references are labeled separately.

Prepare credentials and requests

Manage model keys on the Keys page and account credentials in Profile. Browser sessions, model keys and personal access tokens serve different purposes. Examples read placeholder credentials from server environment variables and contain no real account data. Confirm parameters for the chosen endpoint and channel; example values are not defaults. The API origin is https://api.openfox.vip.

Validate results and handle failures

Check HTTP status and business results together. Text requires complete output, images require actual decoding, and tasks require a successful terminal state and valid artifacts. A task identifier alone is not completion. Bound read-only retries and never automatically repeat creation. After a timeout preserve the request ID and inspect usage logs to avoid duplicate work or charges.

Pricing and maintenance

This guide does not promise fixed prices, quotas, retention periods or provider discounts. Use current marketplace prices and account permissions. An administrator must confirm new prices or unlisted models. Examples are generated from the OpenFox OpenAPI definitions; contract changes must update fields, result checks and failure handling together. Source review is not upstream business verification; this migration makes no paid model calls.

Use cases

  • Submit text-to-video and image-to-video through Kling-style paths
  • Retrieve normalized site task status and output URLs
  • Extend the integration to Kling image, audio, and advanced video actions

API protocols

  • /api/pricing

FAQ

Where can I confirm models and prices?

Use the current marketplace model IDs, endpoints and group prices.

Can I reuse another gateway endpoint directly?

No. Verify OpenFox routes, plugin contracts and authentication requirements.

Is source review a successful business test?

No. No paid calls were made; upstream availability depends on channels and permissions.

Official sources

  1. Kling AI Open Platform Overview Official
  2. Kling AI API Quick Start Official
  3. OpenFox API Official