Space Bunny Alpha API: start with one request

Prepare an account and key

Create an OpenRouter account and generate your own key. Store OPENROUTER_API_KEY in a server-side environment variable. Do not put it in a public repository, browser code or a URL. Read the model listing and Stealth terms before use, especially if you plan to serve other users.

A minimal text request

Send a POST request to the endpoint below with Content-Type: application/json and an Authorization: Bearer header containing your server-side key. Use this request body.

https://openrouter.ai/api/v1/chat/completions

{
  "model": "stealth/space-bunny-alpha",
  "messages": [
    {
      "role": "user",
      "content": "Explain a hash table with an example."
    }
  ],
  "reasoning": {
    "effort": "low"
  },
  "max_tokens": 2048
}

Add capabilities when you need them

• Set reasoning.effort to adjust depth. Higher settings can increase latency and consume more of the output budget.
• Enable stream for SSE responses, handling chunks, error events and the completion marker.
• Add image_url or video_url content parts for media, checking provider format and URL support.
• Use response_format for JSON. For tool calling, your application must execute requested tools and send their results back.

Try a request in your terminal

This command uses Bash syntax for macOS or Linux. Set OPENROUTER_API_KEY in your current terminal first; keep your real key out of saved examples.

curl https://openrouter.ai/api/v1/chat/completions \
  -H "Authorization: Bearer $OPENROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"stealth/space-bunny-alpha","messages":[{"role":"user","content":"Reply with exactly HELLO."}],"max_tokens":256}'

For a completed text response, read choices[0].message.content. Check the HTTP status and any error payload before reading choices. With tools enabled, a message may contain tool_calls instead of a final text answer.

What to check when a request fails

• 401: check that the server-side key is present and belongs to the intended OpenRouter account. Never log the key.
• 402: check account credits, billing details and whether the model is available to your billing region. This is not a JSON-formatting or prompt problem.
• 429 or timeout: inspect rate-limit details and retry with bounded backoff. A stream can also fail after it has started, so handle error events.

Use OpenRouter's response body and documentation for the specific cause. This site does not supply API allowance to third-party integrations.

Free preview is not an availability guarantee

The model currently lists free token pricing, but keys remain subject to account limits and the provider can throttle or withdraw access. Handle 429 responses, timeouts, empty answers and interrupted streams without unbounded retries. Avoid sensitive material because the provider may retain inputs and outputs. Confirm the terms permit your intended public service.

Further reading