ERNIE-4.5-0.3B-PT vs Sonar
Benchmark Performance
Available Benchmarks
Technical Differences
Side-by-Side Facts
| Field | ERNIE-4.5-0.3B-PT | Sonar |
|---|---|---|
| Developer | Baidu | Perplexity |
| Family | Ernie 4 5 0 3b Pt | Sonar |
| Model | ERNIE-4.5-0.3B-PT | Sonar |
| Version | ERNIE-4.5-0.3B-PT | Sonar |
| Lifecycle | active | active |
| Released | Unknown | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Text |
| Context window | 131,072 | 128,000 |
| Total parameters | 360,748,032 | Unknown |
| Active parameters | Unknown | Unknown |
| License | apache-2.0 | Unknown |
| Open weights | Yes | No |
| API available | Unknown | Yes |
| Self-hostable | Yes | No |
| Provider access | Unknown | Openrouter (Standard), Perplexity (Standard) |
| Capabilities | chat, generation | chat, citations, search |
11 comparable fields · 8 material differences · Pair passes the primary-source comparison gate
ERNIE-4.5-0.3B-PT Capabilities
Sonar Capabilities
Internal Comparison Graph
Related Comparisons
| A | Pair | B | Context |
|---|---|---|---|
SonarPerplexity | vs | Sonar Reasoning ProPerplexity | family variantstext |
SonarPerplexity | vs | Sonar ProPerplexity | family variantstext |
SonarPerplexity | vs | Sonar Deep ResearchPerplexity | family variantstext |
ERNIE-4.5-0.3B-PTBaidu | vs | ERNIE 5.1Baidu | family variantstext |
ERNIE-4.5-0.3B-PTBaidu | vs | ERNIE X1.1Baidu | family variantstext |
ERNIE 5.1Baidu | vs | SonarPerplexity | cross-developer peerstext |
ERNIE X1.1Baidu | vs | SonarPerplexity | cross-developer peerstext |
PaddleOCR-VL-1.5Baidu | vs | ERNIE-4.5-0.3B-PTBaidu | cross-developer peerstext |
ERNIE-4.5-0.3B-PTBaidu | vs | GLM-OCRZ.ai | cross-developer peerstext |
ERNIE-4.5-0.3B-PTBaidu | vs | cross-developer peerstext | |
ERNIE-4.5-0.3B-PTBaidu | vs | Phi-4-mini-instructMicrosoft | cross-developer peerstext |
ERNIE-4.5-0.3B-PTBaidu | vs | cross-developer peerstext |
Primary Evidence
Sources and Freshness
Questions
ERNIE-4.5-0.3B-PT vs Sonar FAQs
Is ERNIE-4.5-0.3B-PT or Sonar better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both ERNIE-4.5-0.3B-PT and Sonar, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, ERNIE-4.5-0.3B-PT or Sonar?+
Only Sonar has a directly sourced input price: $1.00 per million tokens. Only Sonar has a directly sourced output price: $1.00 per million tokens.
Which has a larger context window, ERNIE-4.5-0.3B-PT or Sonar?+
ERNIE-4.5-0.3B-PT has the larger sourced context window. ERNIE-4.5-0.3B-PT supports 131,072 and Sonar supports 128,000.
Which performs better in benchmarks, ERNIE-4.5-0.3B-PT or Sonar?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can ERNIE-4.5-0.3B-PT or Sonar be self-hosted?+
ERNIE-4.5-0.3B-PT is the only model in this pair currently marked as self-hostable. ERNIE-4.5-0.3B-PT is open weight; Sonar is not marked open weight.
Can ERNIE-4.5-0.3B-PT and Sonar understand images?+
ERNIE-4.5-0.3B-PT is not documented with image input; Sonar is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, ERNIE-4.5-0.3B-PT or Sonar?+
Neither has a larger sourced maximum output. ERNIE-4.5-0.3B-PT is — and Sonar is —.
Do ERNIE-4.5-0.3B-PT and Sonar support reasoning and tool use?+
ERNIE-4.5-0.3B-PT: none of these features are definitively sourced. Sonar: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, ERNIE-4.5-0.3B-PT or Sonar?+
ERNIE-4.5-0.3B-PT has 0 sourced provider routes; Sonar has 2, so Sonar has broader tracked availability.
Which offers better value, ERNIE-4.5-0.3B-PT or Sonar?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.