anthropic/claude-fable-5-2, served by Comfy Router from Anthropic.
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: anthropic/claude-fable-5-2
Endpoint: POST https://api.comfy.org/v2/models/anthropic/claude-fable-5-2
- Wait for the result
- Queue and collect later
The same body, sent to
POST https://api.comfy.org/v2/models/anthropic/claude-fable-5-2/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
Conversation turns. See Anthropic Messages API docs for the full content-block taxonomy.
Either a string shorthand or an array of content blocks (text, image, document, tool_use, tool_result, …).
On the Comfy Router route
POST /v2/models/anthropic/{model}, stream is INERT: Router SETTLES it to false before dispatch and always returns the completed message as one JSON document. On the v1 POST /proxy/anthropic/v1/messages route, true makes the response a text/event-stream of Anthropic message events instead of a single JSON body. Send stream false or omit it on Router; the text/event-stream half of the /proxy/ operation’s 200 has no Router counterpart.Top-level system prompt. Either a string or an array of content blocks; both reach Anthropic unchanged.
GET /v2/models/anthropic/claude-fable-5-2/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
The reply’s content blocks, in order. Present on every completed message; empty when the turn produced nothing.
The block kind.
text is the one that carries text; thinking, redacted_thinking, tool_use, server_tool_use and the tool-result blocks are the others Anthropic sends today, and the list is open.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.