Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| — | Provider / route Relace relace/fp8 | Estimated response timeInsufficient recent data | Speed measurements
| Endpoint details
|
Endpoint data fetched .
Relace Apply 3 endpoint guide
0 of 1 Relace Apply 3 endpoint currently have the published data required for this ranking. No endpoint currently has enough data to receive first place. 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.
Only 0 routes currently qualifies, so the rank alone provides limited choice. Review every visible endpoint for price, speed, uptime, context length, and route-specific configuration.
Relace Apply 3 has 1 published provider option, 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.
