NextBit

NextBit

EU
3 models available

Data handling can vary by model and deployment. The privacy badge above shows the more conservative of the provider-wide fallback and the policies for routes on this page; each model page shows the policy for that specific route.

Models served by NextBit

ModelContextInput /MOutput /MCache read /MTTFTThroughput
262k$0.09/M$0.31/M$0.05/M0.3s76 tps
262k$0.09/M$0.31/M$0.05/M0.3s76 tps
41k$0.10/M$0.23/MN/A1.4s45 tps
Context
262k
Input /M
$0.09/M
Output /M
$0.31/M
Cache read /M
$0.05/M
TTFT
0.3s
Throughput
76 tps
Context
262k
Input /M
$0.09/M
Output /M
$0.31/M
Cache read /M
$0.05/M
TTFT
0.3s
Throughput
76 tps
Context
41k
Input /M
$0.10/M
Output /M
$0.23/M
Cache read /M
N/A
TTFT
1.4s
Throughput
45 tps

Prices are per million tokens. TTFT is the observed time to first token. Selectable routes include the applicable provider-selection markup; fixed routes show the standard model price. Availability and pricing refresh continuously; each model page shows the live provider comparison.

Using NextBit via the API

Call a model served by NextBit using its displayed model ID, including the provider suffix when selection is supported.

cURL

curl https://nano-gpt.com/api/v1/chat/completions \
  -H "Authorization: Bearer $NANOGPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "google/gemma-4-26b-a4b-it:nextbit",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

For models with provider selection, append :nextbit to the model ID, set "provider": "nextbit" in the request body, or send an X-Provider: nextbit header. Explicit provider selection adds a route-specific markup over that provider's base price; the prices in the table above already include it. Models without provider selection use the displayed model ID without a provider suffix or selection surcharge.

See the API documentation for provider preferences, price-aware routing, and error behavior.