Skip to content

Scenario Overview - Publish Models ​

This scenario helps model providers publish models as services that can be tried and called.

Applicable Roles ​

  • Model Provider
  • Operator when preconfiguration or review is required

Scenario Goals ​

  • Publish a model service that users can discover, try, and call.
  • Configure protocol, billing, rate limits, publication scope, and review data.

Scenario Flow ​

Main path: Prepare publication → Configure and test the model → Submit for review → Publish and verify calls

StageKey Result
1. Prepare publicationMeta Models, sources, templates, tags, and currency are available
2. Configure and testModel information, protocol, billing, and rate limits pass validation
3. Submit for reviewThe request enters review and comments can be tracked
4. Verify publicationIntended users can discover, try, and call the model

Before You Start ​

  • Complete model-publishing preconfiguration.
  • Choose platform-hosted deployment or BYOK. For BYOK, prepare the external endpoint, model ID, protocol, headers, and key.
  • Define billing and rate-limit policies.
  1. Publish Models Preconfiguration
  2. Choose the guide for the target model type
  3. Model Publishing Approval
  4. Model Experience and API Calling

Document Index ​

DocumentDescription
Publish Public ModelsChoose platform-hosted deployment or BYOK, then complete model information, protocol testing, billing, rate limits, and approval submission
Publish Text ModelsPublish a text model through the text model publishing flow
Publish Multimodal ModelsPublish a multimodal conversation model and configure compatible protocols and billing
Publish Embedding ModelsPublish an embedding model through an embeddings-compatible protocol
Publish Image ModelsPublish an image model with image-specific billing and response parsing
Publish Speech ModelsPublish a speech model with audio protocol and character-based billing
Publish Video ModelsPublish an asynchronous video model with callback and result parsing
My ModelsReview the model publishing entry, fields, and operations

Completion Checklist ​

Purpose: These are the scenario exit criteria. Use them to decide whether the outcome is observable and reviewable and whether you can continue to the next scenario. They do not repeat the procedure; if any item fails, return to the relevant feature guide and follow its troubleshooting section.

CheckPass Criteria
1Protocol testing passes and model source and request parameters work.
2Billing, rate limits, publication area, and publication time match the plan.
3Review status and comments are visible after submission.
4Intended users can find, try, and call the published model.

Troubleshooting ​

SymptomCheck First
Meta-model or source cannot be selectedOperator preconfiguration, state, and account visibility
Protocol test failsEndpoint, headers, source model ID, protocol, and response parsing
Review cannot be submittedRequired fields, billing, rate limits, publication area, and test state
Published model is not visibleReview state, publication time, public/private scope, and tenant permission