Start typing to search.
Ranks providers by how quickly the first generated token appears. Providers without enough recent data remain visible after ranked rows.
| Rank | Provider / route | Time to first token | Speed measurements | Endpoint details |
|---|---|---|---|---|
| — | Provider / route Relace relace/fp8 | Time to first tokenInsufficient 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 first-token ranking orders endpoints by the recent median time before output begins. This is useful for interactive applications, but it should be read alongside throughput because the first provider to start is not always the first to finish a long answer.
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.
