Serverless

Access Wafer models through OpenAI-compatible and Anthropic-compatible APIs.

Access Wafer models through OpenAI-compatible and Anthropic-compatible APIs. Add credits, create an API key, and pay per token.

Get an API key

Sign in at app.wafer.ai to add credits and create an API key. Store your key securely.

Connect

Setting	Value
Base URL	https://pass.wafer.ai/v1
Authentication	Authorization: Bearer <YOUR_WAFER_API_KEY>

Anthropic-style clients can send the key as x-api-key: <YOUR_WAFER_API_KEY> instead.

Send a request

curl -sS "https://pass.wafer.ai/v1/chat/completions" \
  -H "Authorization: Bearer <YOUR_WAFER_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "GLM-5.3",
    "messages": [
      {"role": "user", "content": "Hello!"}
    ],
    "max_tokens": 128
  }'

Choose an API

Chat Completions is the primary API. Every model supports it, and it has the widest feature set. Responses and Messages are compatibility APIs for clients that already speak those formats.

API	Endpoint	Use it for
Chat Completions	POST /v1/chat/completions	New integrations and OpenAI SDK clients. Streaming, tools, structured outputs, vision, and reasoning.
Responses	POST /v1/responses	Clients built on the OpenAI Responses API, such as Codex. Stateless: no stored responses.
Messages	POST /v1/messages	Anthropic SDK clients and Claude Code.

To use an SDK, point the OpenAI SDK’s base URL at https://pass.wafer.ai/v1, or the Anthropic SDK’s base URL at https://pass.wafer.ai, and pass your Wafer API key.

Available models

List available models and their capabilities:

curl -sS "https://pass.wafer.ai/v1/models" \
  -H "Authorization: Bearer <YOUR_WAFER_API_KEY>"

Use a model’s id in your requests. See Models and Capabilities for context limits, per-API capability flags, reasoning efforts, and pricing.

Zero Data Retention

To require Zero Data Retention for a request, add Wafer-ZDR: required. See Zero Data Retention for supported models and requirements.

Reference

• Errors and Rate Limits: error format, error codes, retries, and 429 handling.
• Usage and Billing: token usage in responses, prompt caching, and billing.

Support

For help, contact [e-mail]. Include the request ID if available. Never share your API key.