Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
Mancer currently ranks first at 15.82 s via mancer/fp8.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Mancer mancer/fp8 | Estimated response time15.82 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route NextBit nextbit/bf16 | Estimated response time31.17 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
ReMM SLERP 13B endpoint guide
2 of 2 ReMM SLERP 13B endpoints currently have the published data required for this ranking. Mancer leads at 15.82 s via mancer/fp8. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The fastest ranking estimates a 500-token answer by adding the recent median first-token wait to 500 divided by median output throughput. It represents an example complete response, not a guarantee for every prompt or request size.
NextBit currently ranks second at 31.17 s. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.
ReMM SLERP 13B has 2 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.
