Start typing to search.
Ranks providers by how quickly the first generated token appears. Providers without enough recent data remain visible after ranked rows.
Together currently ranks first at 0.27 s via together.
| Rank | Provider / route | Time to first token | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Together together | Time to first token0.27 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route Weights & Biases wandb/fp4 | Time to first token0.28 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route Groq groq | Time to first token0.30 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Fireworks fireworks | Time to first token0.33 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Parasail parasail/fp4 | Time to first token0.47 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route NovitaAI novita/fp4 | Time to first token0.57 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route Phala phala | Time to first token0.62 s | Speed measurements
| Endpoint details
|
| #8 | Provider / route DeepInfra deepinfra/bf16 | Time to first token0.76 s | Speed measurements
| Endpoint details
|
| #9 | Provider / route DekaLLM dekallm/bf16 | Time to first token0.91 s | Speed measurements
| Endpoint details
|
| #10 | Provider / route SiliconFlow siliconflow/fp8 | Time to first token1.35 s | Speed measurements
| Endpoint details
|
| #11 | Provider / route Google Vertex google-vertex/us-central1 | Time to first token3.31 s | Speed measurements
| Endpoint details
|
| #12 | Provider / route Amazon Bedrock amazon-bedrock | Time to first token7.69 s | Speed measurements
| Endpoint details
|
| — | Provider / route Amazon Bedrock amazon-bedrock/eu-west-1 | Time to first tokenInsufficient recent data | Speed measurements
| Endpoint details
|
Endpoint data fetched .
gpt-oss-20b endpoint guide
12 of 13 gpt-oss-20b endpoints currently have the published data required for this ranking. Together leads at 0.27 s via together. 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.
Weights & Biases currently ranks second at 0.28 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.
gpt-oss-20b has 13 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.
