DOCUMENTATION / QUICKSTART
From zero
to a request.
A short guide to integrating a compatible API gateway.
01 / CONFIGURE
Start with your endpoint.
Obtain a base URL, API key, and supported model identifier from your gateway operator. Include the API version path in the base URL if required.
export BASE_URL="https://YOUR_GATEWAY_HOST/v1"
export API_KEY="YOUR_API_KEY"
export MODEL_ID="YOUR_MODEL_ID"Replace all placeholders. Keep credentials in server-side environment variables. Never embed a secret key in browser code.
02 / REQUEST
Send something simple.
Download the starter and run the Python example after setting the variables. It uses the standard library and a 60-second timeout.
python3 chat.pyThe sample uses a chat-completions request shape. Confirm that your upstream supports it and adjust the schema when needed. No callable inference endpoint is published by this documentation site.
Download examples ↗03 / RESPONSES
Make failure predictable.
- 401 / 403
- Check the key, permissions, and account scope.
- 429
- Respect rate limits and Retry-After when supplied.
- 5xx / timeout
- Use bounded retries and consider whether repeating a request may duplicate work or charges.
- Streaming / SSE
- Enable only when supported upstream. Parse events incrementally and handle disconnects explicitly.
04 / VERIFY
Check what you download.
Compare the downloaded file with the published SHA-256. The checksums describe a release snapshot, not a live service status.
sha256sum pansla-starter-1.0.0.zip
# Windows PowerShell
Get-FileHash .\pansla-starter-1.0.0.zip -Algorithm SHA256SHA256SUMS.txt ↗