Space Bunny

SPACE BUNNY INTEGRATIONS

Bring a million-token context to the tools you already use.

Space Bunny works with clients that accept an OpenAI-compatible endpoint. Keep the integration small: base URL, API key and model ID, then let your application control context and permissions.

Open the API guideTry the Playground
server.envserver environment
export OPENAI_BASE_URL="https://spacebunny.app/api/v1"
export OPENAI_API_KEY="$SPACE_BUNNY_API_KEY"
export OPENAI_MODEL="stealth/space-bunny-alpha"

THREE WAYS TO START

Choose the surface that matches the job.

Evaluate in the browser, call the model from an SDK, or point a compatible coding agent at the same server-side endpoint.

Browser Playground

Try long-context prompts, visual input and reasoning levels before you write integration code.

OpenAI-compatible SDKs

Reuse the client pattern you already know and keep the Space Bunny request behind your own server.

Coding agents

Configure an agent that accepts a custom provider, then use Space Bunny for repository-scale reading and planning.

SETUP

Keep the adapter boring.

Most integration problems come from an exposed key, an incorrect base URL or a model ID copied from a different route.

01

Set the base URL

Use the Space Bunny API base URL for an OpenAI-compatible chat-completions client.

02

Use the documented model ID

Start with stealth/space-bunny-alpha and keep the model name in one server-side configuration value.

03

Limit what the agent can do

Expose only the tools and repository context needed for the current task. Your application remains the authority for side effects.

CLIENT EXAMPLE

A compatible client does not need a new mental model.

The endpoint accepts the familiar message shape. Add reasoning, multimodal parts, JSON or tools as explicit request fields.

client.py
from openai import OpenAI

client = OpenAI(
    base_url="https://spacebunny.app/api/v1",
    api_key=SPACE_BUNNY_API_KEY,
)

answer = client.chat.completions.create(
    model="stealth/space-bunny-alpha",
    messages=[{
        "role": "user",
        "content": "Review this repository boundary.",
    }],
    extra_body={"reasoning": {"effort": "high"}},
)

BEFORE YOU CONNECT A TOOL

Compatibility describes the wire format, not authorization.

A coding agent or SDK may request a tool, but it cannot grant itself access. Validate the call in your application before reading, writing, deploying or sending anything externally.

Use a server-side key
Expose only approved tools
Scope repository paths and sensitive files
Require approval for writes and deployments

BUILD WITH THE SAME REQUEST

Start with a client you already understand.

Test the model in the Playground, then copy the request shape into your SDK or compatible coding agent.

Open the API guideTry the Playground