Granite Embedding English r2 vs GR00T N1.7 3B

This comparison does not currently contain a protocol-matched coding benchmark for both Granite Embedding English r2 and GR00T N1.7 3B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.

Neither model has a larger sourced context window in this comparison. Granite Embedding English r2 is 8K and GR00T N1.7 3B is —.

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Both models have the same recorded self-hosting status: supported. Granite Embedding English r2 is open weight; GR00T N1.7 3B is open weight.

Granite Embedding English r2 is not documented with image input; GR00T N1.7 3B is documented with image input. This reflects supported input modalities, not vision quality.

Neither has a larger sourced maximum output. Granite Embedding English r2 is — and GR00T N1.7 3B is —.

Granite Embedding English r2: none of these features are definitively sourced. GR00T N1.7 3B: image input. Feature support does not establish relative quality.

Granite Embedding English r2 has 0 sourced provider routes; GR00T N1.7 3B has 0, a tie.

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.