Access methods
The API base URL depends on how you access Poolside.Available endpoints
Poolside-hosted inference supports these endpoints:Authentication
Get an API key
Get the API key for your access method:- Poolside-hosted inference: Sign in to Poolside Platform, open the API Keys tab, and click New key.
- OpenRouter: Go to OpenRouter API keys, sign in, and create an API key.
- Self-managed Poolside inference: Use the API key configured for your model endpoint or inference gateway. If API key authentication is off, you do not need a key.
Send the API key
Poolside-hosted inference and OpenRouter require an API key. Send it as a Bearer token in theAuthorization header:
Authorization header.
API keys are secrets. Store them securely and never commit them to source control.
Make your first API call
This quickstart uses Poolside-hosted inference and thepoolside/laguna-s-2.1 model ID.
Prerequisites
- An API key from Poolside Platform
curl, Python, or Node.js
- cURL
- Python
- TypeScript
1
Set your API key
Export your API key as an environment variable. The cURL command below reads it from
$POOLSIDE_API_KEY.2
Make your first API call
Send a Poolside returns a JSON response containing the message:Poolside-hosted inference enables thinking by default, so the response can include
POST request to the Chat Completions endpoint:Response example
reasoning_content in addition to content. See OpenAI-compatible API examples to turn it off.To use OpenRouter instead, use
https://openrouter.ai/api/v1 as the base URL or SDK base_url/baseURL, pass your OpenRouter API key, and replace the model ID with an OpenRouter model ID.Use the API for CLI automation
For interactive Poolside Agent CLI access, see Log in to Poolside. For CLI automation against an OpenAI-compatible endpoint, configurePOOLSIDE_STANDALONE_BASE_URL, POOLSIDE_STANDALONE_MODEL, and POOLSIDE_API_KEY. If the endpoint does not validate API keys, use any non-empty value for POOLSIDE_API_KEY, such as local-test. See Automate tasks.
Next steps
- OpenAI-compatible API examples for generation controls, thinking control, streaming, and tool calling
- Supported models for model guidance, context windows, and modes
- Editors to use Poolside from editors and editor extensions
- Desktop apps to use Poolside from desktop apps