Side-by-side comparison
Perceptron Mk1 vs Sonar
| Perceptron Mk1 | Sonar | |
|---|---|---|
| Provider | Perceptron | Perplexity |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 32,768 | 127,072 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | vision | vision |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 0.1500 | 1.0000 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 1.5000 | 1.0000 |
Frequently asked questions
Which is cheaper, Perceptron Mk1 or Sonar?
Perceptron Mk1 is cheaper than Sonar on a 50/50 input/output blend by about $0.175 per 1M tokens. Exact savings depend on your input-vs-output ratio — use the cost calculator on this page for a workload-specific estimate.
Which has a larger context window, Perceptron Mk1 or Sonar?
Sonar has the larger context window at 127k tokens versus 33k tokens for Perceptron Mk1. That means Sonar can ingest about 3.9x as much text per request.
What is the difference between Perceptron Mk1 and Sonar?
Perceptron Mk1 comes from Perceptron; Sonar comes from Perplexity. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.