Skip to content

Publish a Model (Embedding) ​

Target Outcome ​

The embedding model passes protocol testing, is published to the intended scope, and returns vectors with the expected dimensions.

Applicable Roles ​

  • Model Provider

Before You Start ​

  • Prepare the model source, model identifier, API credential, and embedding endpoint.
  • Confirm the input format, vector dimensions, billing unit, and rate-limit policy.

Procedure ​

  1. From the platform home page, select My Models in the left navigation.
  2. Open My Publications. Use Public Models / Private Models to switch publication areas, or open Overview and My Aggregations when needed.
  3. Select Publish Model in the upper-right corner.
  4. Select a publication area:
    • Publish to Private Area makes the model visible only within the team or tenant and keeps it out of the public catalog.
    • Publish to Public Area lists the model in the public catalog for all tenants and allows independent pricing and rate limits.
  5. Select Publish to Public Area to open Step 1.

Choose the publication area

Step 1: Basic Information ​

  • Under Model Source / Meta-Model Information:
    • Select a meta-model, such as text-embedding-v1.
    • Select a model source, such as Alibaba - China.
    • Enter the request URL, such as https://dashscope.aliyuncs.com.
    • Enter the API key in the protected field, such as sk-***.
    • Enter the exact upstream Model Source ID, such as text-embedding-v1.

Model source and meta-model information

  • Confirm that Model Type is Embedding Model.

Confirm the model type

  • Under Request Headers, keep the default Authorization: Bearer <key> template and add only headers required by the upstream service.

Configure request headers

  • Under Model Parameters:
    • Set the input modality to Text.
    • Embedding models have no output-modality option because the output is a vector.
    • Set maximum context and maximum input, such as 8192K. Leave maximum output empty when the embedding service does not use output tokens.

Configure model parameters

  • Under Supported Protocols and Default Parameters, select OpenAI-Embeddings, run the connectivity test, enter the endpoint, and configure inputs such as Encoding Format and Input. Embedding models use synchronous calls with a fixed response structure and therefore have no callback or result-parsing section.

Test the official native protocol

  • Enter the public Custom Identifier and description.

Complete basic information

  • Select Publish Immediately or Scheduled Publication.

Choose the publication method

  • Select Next to open Step 2.

Step 2: Billing Configuration ​

  • Select Token Billing or Free.
  • For token billing:
    • Enable Show Price Comparison when a reference price should be displayed.
    • Enter the input sale price and optional original price. Embedding models do not use output-price, cache, or tier configuration.
    • Optionally configure a free quota, eligible-user count, and total amount.

Configure billing

  • Select Next to open Step 3.

Step 3: Rate-Limit Configuration ​

  • Select Enable Rate Limiting or Disabled.
  • Configure default limits:
    • RPM: requests per minute, or Unlimited.
    • TPM: tokens per minute, or Unlimited.

Configure rate limits

  • Select Save Only or Submit for Review.

Parameter Reference - Embedding Model ​

FieldTypeExampleDescription
Meta-ModelSelecttext-embedding-v1Required; base meta-model
Model SourceSelectAlibaba - ChinaRequired; upstream Model Provider
Request URLURLhttps://dashscope.aliyuncs.comRequired; model-service base URL
API KeyPasswordsk-***Required; protected upstream credential
Model Source IDTexttext-embedding-v1Required; exact upstream model name
Model TypeSingle selectEmbedding ModelRequired; no subtype
Request HeadersKey-value pairsAuthorization: Bearer <key>Optional; authentication and custom headers
Input ModalityMulti-selectTextRequired; accepted input type
Output ModalityNot applicableNoneEmbedding output is a vector
Maximum ContextNumber8192KRequired; context-token limit
Maximum InputNumber8192KRequired; input-token limit
Maximum OutputNumberEmptyEmbedding models do not use output-token limits
Supported ProtocolMulti-selectOpenAI-EmbeddingsRequired; test connectivity before continuing
EndpointURLhttps://dashscope.aliyuncs.com/compatible-mode/v1/embeddingsRequired; protocol endpoint
Input ParametersParameter listEncoding Format / InputOptional; protocol inputs and required-state settings
Custom IdentifierTexttext-embedding-v1Required; model identifier shown to users
DescriptionTextText embedding...Optional; model description
Publication MethodSingle selectImmediate / ScheduledRequired; publication time
Billing MethodSingle selectToken Billing / FreeRequired; billing method
Show Price ComparisonSwitchOn / OffOptional; displays an original reference price
Input Sale PriceNumber7 Credits/1M tokensRequired for paid models
Original PriceNumber14 Credits/1M tokensOptional; input reference price
Free QuotaSwitchOn / OffOptional; configures free usage quota
Rate LimitingSingle selectEnabled / DisabledOptional; controls invocation limits
RPMNumber / Unlimited2 requests/minuteOptional; request limit per minute
TPMNumber / Unlimited100 tokens/minuteOptional; token limit per minute

Completion Checklist ​

Purpose: These are the exit criteria for the current feature task. Use them to decide whether the result is observable and reviewable and whether you can continue to the next step in the scenario. They do not repeat the procedure; if any item fails, follow the troubleshooting section below.

CheckPass Criteria
1Protocol connectivity passes and the model source and identifier are accurate.
2Publication or review status is correct.
3A controlled call returns vectors with the expected dimensions and the call log is traceable.

Troubleshooting ​

SymptomCheck First
Protocol test failsEndpoint, credential, model identifier, request body, and source network access
Vector response is invalidInput format, dimensions, response mapping, and selected protocol

User Manual ​

Review complete My Models fields and publication-result validation