Quickstart
Send your first request through the AI Gateway.
The Gateway authenticates, applies your routing and limit policies, calls the selected provider, records structured usage, and returns the response.
REST API
The AI Gateway exposes an OpenAI-compatible chat completions endpoint, plus endpoints for prompt resolution, usage queries, and control-plane operations.
| Area | Endpoint | Purpose |
|---|---|---|
| Chat | POST /v1/chat/completions | Route a request to a model |
| Prompts | GET /v1/prompts/{name} | Resolve the active prompt version |
| Usage | GET /v1/usage | Query structured usage records |
| Budgets | GET /v1/budgets | Inspect budget consumption |
| Audit | GET /v1/audit | Read audit events |
Full request and response shapes live in the API Reference.
Authentication
Requests use a bearer token issued by SchneeAI. Tokens carry a service, tenant, and user identity — so limits, logs, and access controls always reflect the caller. Never expose tokens in client-side code; route AI calls through your backend.
Examples
- Chat endpoint — minimal request with
model: "auto"and a single user message. - Named prompt — call the Gateway with a registered prompt name and variables.
- Budget-aware call — pass a feature tag so spend lands on the right budget.
SDKs (coming soon)
Go and TypeScript SDKs are on the roadmap. Today, integrate with any HTTP client — the REST API is the source of truth and SDKs will follow its shape.
Stay in the loop
New endpoints, breaking changes, and release notes land on the changelog first. Email hello@schneeai.com with “Subscribe” in the subject and we’ll add you to the announcements list.