Side-by-side comparison
Weaver (alpha) vs Cogito v2.1 671B
| Weaver (alpha) | Cogito v2.1 671B | |
|---|---|---|
| Provider | Mancer | Deep Cogito |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 8,000 | 128,000 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | json_mode | json_mode |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 0.7500 | 1.2500 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 1.0000 | 1.2500 |
Frequently asked questions
Which is cheaper, Weaver (alpha) or Cogito v2.1 671B?
Weaver (alpha) is cheaper than Cogito v2.1 671B on a 50/50 input/output blend by about $0.375 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, Weaver (alpha) or Cogito v2.1 671B?
Cogito v2.1 671B has the larger context window at 128k tokens versus 8k tokens for Weaver (alpha). That means Cogito v2.1 671B can ingest about 16.0x as much text per request.
What is the difference between Weaver (alpha) and Cogito v2.1 671B?
Weaver (alpha) comes from Mancer; Cogito v2.1 671B comes from Deep Cogito. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.