byteplus/seed-2-0-pro-260328, served by Comfy Router from BytePlus.
Input: Text, Image · Output: Text
Quick start
Create a key in your Comfy workspace and export it asCOMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk and npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.
Model ID: byteplus/seed-2-0-pro-260328
Endpoint: POST https://api.comfy.org/v2/models/byteplus/seed-2-0-pro-260328
- Wait for the result
- Queue and collect later
The same body, sent to
POST https://api.comfy.org/v2/models/byteplus/seed-2-0-pro-260328/requests. Router answers 201 with a request_id as soon as the run is admitted, and the result is collected once it is ready, from this process or another one. Queued delivery walks through status, cancellation and collection.Schema
Input
Context-management strategies (
clear_thinking, clear_tool_uses) applied to keep the context window manageable.Unix timestamp (seconds, UTC) at which the stored response and cache expire. Range (creation_time, creation_time + 604800]. Default: creation_time + 259200 (3 days).
Additional output fields to include. Currently supported:
reasoning.encrypted_content (encrypted+compressed reasoning for manual multi-turn reuse).System/developer message prepended as the first instruction. Not compatible with
caching — if caching.type is enabled, setting instructions returns an error.Model ID or Endpoint ID. See https://docs.byteplus.com/en/docs/ModelArk/1330310 for the model list and https://docs.byteplus.com/en/docs/ModelArk/1099522 for Endpoint IDs. A direct v1 call to POST /proxy/byteplus/api/v3/responses MUST supply it — the proxy refuses any value outside its own allowlist, and an omitted one, with a 400. It is NOT in the Comfy Router input schemas’
required lists because Router fills it from the {model} path segment of /v2/models/byteplus/{model}, so a Router caller omits it.ID of the previous response, used to continue a multi-turn conversation. Insert ~100ms between requests to avoid failures.
minimal disables thinking entirely. With thinking.type = disabled, only minimal is allowed.Possible values: minimal, low, medium, highText-output format discriminated by
type. text returns natural language, json_object returns a free-form JSON object, json_schema constrains output to a caller-supplied JSON Schema.enabled: always reason before responding.
disabled: respond without additional reasoning.
auto: model decides per-query.Possible values: enabled, disabled, autoGET /v2/models/byteplus/seed-2-0-pro-260328/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
Context-management strategies that were actually applied during this response. Unlike the request-side
BytePlusResponseContextManagement (which configures strategies), this echoes the strategies the server invoked, with counts of what was cleared.Text-output format discriminated by
type. text returns natural language, json_object returns a free-form JSON object, json_schema constrains output to a caller-supplied JSON Schema.Examples
Input
Output
Before you ship
The SDKs create anIdempotency-Key and reuse it for automatic retries. For manual retries, reuse the original key. Router can hold the connection for up to 10 minutes.
When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider, and a 413 means the request body was larger than Router accepts. Download generated assets promptly because result URLs can expire.
Any size limit named in a field description above is the provider’s own bound on that field, quoted from the provider’s specification. Router applies a separate cap to the whole request body, which base64-encoded media counts against: see request body size.
This page documents one partner model called through Comfy Router. The same comfy-sdk / @comfyorg/sdk package also ships a second client, for running a whole ComfyUI workflow graph on Comfy Cloud: Comfy(api_key=...) / new Comfy({ apiKey }), with client.workflows, client.assets and client.jobs. See Comfy SDKs.
Headers
Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
Using the Router API
Model discovery, validation errors, retries, and billing.
Limitations
What Router does not do today, and what to use instead.