Provider: Nextbit
Provider: Nextbit
Use Respan Gateway to call Nextbit-hosted models (open-source LLMs served through Nextbit’s inference platform) while keeping unified observability (logs, cost, latency, reliability) in Respan.
Quick setup
Add credits (recommended)
Top up credits to pay through Respan. No Nextbit key required, Respan handles provider auth and billing.
Prefer to route through your own Nextbit account? See Use your own Nextbit key.
Send your first request
Pick the integration that matches your stack. The base URL is https://api.respan.ai/api and the only key needed is your RESPAN_API_KEY.
OpenAI SDK
Respan API
Nextbit is OpenAI-compatible. Point the OpenAI SDK at the Respan gateway and call any Nextbit model.
More integrations
Nextbit models work with every Respan gateway integration:
Switch models
Change the model parameter to call any supported model through the same client. Use the nextbit256/ prefix to disambiguate when routing across providers. Browse the full list on the Models page.
Use your own Nextbit key (BYOK)
Credits are the default path. If you’d rather bill Nextbit directly, attach your own provider key.
Global (UI)
Per-request (Code)
Override credentials per model (Optional)
Use credential_override when one model on a request should use a different Nextbit key than the default.
Log without proxying (Optional)
Already calling Nextbit directly? Send logs to Respan asynchronously to track cost, latency, and performance for those external calls.
See the logging guide for the full setup.