Perplexity: Decider Flash V1.2 vs Respan: Span-01
A side-by-side comparison of Perplexity: Decider Flash V1.2 ($0.04 / 1M tokens) and Respan: Span-01 ($0.07 / 1M tokens) using current USD prices and capabilities from the api14 catalog. Both run through the same OpenAI-compatible API.
Specifications
| Perplexity: Decider Flash V1.2 | Respan: Span-01 | |
|---|---|---|
| Provider | Perplexity | Respan |
| Input | $0.04 / 1M tokens | $0.07 / 1M tokens |
| Context window | 262,144 | - |
| Max output | 235,929 | - |
| Input | text, image | text |
| Output | decisions | decisions |
| Tool calling | ||
| Structured output | ||
| Reasoning control | ||
| Added | Oct 16, 2026 | Sep 26, 2026 |
Key differences
- Perplexity: Decider Flash V1.2 is 50% cheaper on input tokens.
- A request with 1,000 input and 500 output tokens costs $0.000035 with Perplexity: Decider Flash V1.2 and $0.000070 with Respan: Span-01.
In depth
Perplexity: Decider Flash V1.2 is a decisions model from Perplexity, released on 2026-10-16. Respan: Span-01 is a decisions model from Respan, released on 2026-09-26. Both are built for the same broad job, producing decisions as their output rather than free-form prose, so the choice between them comes down to inputs, context and price rather than to the kind of result they return.
The clearest split is in what each model accepts. Decider Flash V1.2 takes text and image input, so you can send a screenshot, a diagram or a scanned page alongside your instructions and have it factored into the decision. Span-01 takes text only. Decider Flash V1.2 also lists a context length of 262144 tokens, while Span-01 has no context length listed, so if you are working with long documents or long histories, Decider Flash V1.2 is the one with a stated capacity to plan around. Neither model lists supported parameters, and neither is flagged as the only one offering tools, structured output or reasoning, so those dimensions do not separate them. On price, Decider Flash V1.2 is the cheaper of the two on input; output pricing is not meaningfully different or is unknown, so treat the two as comparable there.
For practical work, reach for Decider Flash V1.2 when your input is not purely text, when you need to hand over a large amount of material in one call, or when input cost matters most because you are sending a lot of tokens per request. Reach for Span-01 when your input is plain text, your prompts are short to moderate, and you want a straightforward decisions call without carrying image handling through your pipeline. If you are unsure, start with Decider Flash V1.2, since it covers everything Span-01 does on the input side and adds image support and a stated context window.
Calling either model through api14 works the same way, because the API is OpenAI-compatible. You point your existing OpenAI client at the api14 base URL, send your request to the chat completions endpoint with your api14 key, and set the model field to the id you want. The only change between the two is that string: use "perplexity/pplx-decider-flash-v1.2" for Decider Flash V1.2 and "respan/span-01" for Span-01. Your message structure, headers and response parsing stay as they are, so you can switch models by editing one line or by passing the id in as a variable.
Span-01 remains the better pick in one situation the facts support: when your input is text only and you do not need a large stated context window, it is a perfectly reasonable default, and it was released earlier, so it may already be the model your existing prompts and evaluation set were tuned against. There is no capability listed here that Span-01 has and Decider Flash V1.2 lacks, so that choice is about fit with your current setup rather than about anything Span-01 does that the other cannot.
Switch with one string
Both models use the same endpoint and request shape. Change the model value from "perplexity/pplx-decider-flash-v1.2" to "respan/span-01" and prompts, streaming and tools keep working.
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api14.com/api/v1",
apiKey: process.env.API14_API_KEY,
});
const result = await client.post("/decisions", { body: {
"model": "respan/span-01",
"state": "Customer: I was charged twice for my order and want my money back.",
"questions": {
"team": {
"type": "choice",
"instructions": "Which team should handle this message?",
"criteria": {
"billing": "Payments, refunds, invoices",
"support": "Product questions and bugs",
"sales": "Pricing and new purchases"
}
},
"urgent": {
"type": "noul",
"instructions": "Does this need a reply today?",
"criteria": {
"true": "Money, outage or legal risk",
"false": "Can wait"
}
}
}
} });
console.log(result.answers);
More comparisons
- LiquidAI: d1 Latest vs LiquidAI: d1-ultra Latest
- LiquidAI: d1 Latest vs Baseten: Joey 1
- LiquidAI: d1 Latest vs LiquidAI: d1.1
- LiquidAI: d1 Latest vs Morph: Reflex
- LiquidAI: d1-ultra Latest vs Baseten: Joey 1
- LiquidAI: d1-ultra Latest vs LiquidAI: d1.1
- LiquidAI: d1-ultra Latest vs Morph: Reflex
- Baseten: Joey 1 vs LiquidAI: d1.1