Introduction
One OpenAI-compatible API to open models on Merius's own GPUs. Authenticate, point your client at the base URL, and call any model.
The Merius API speaks the OpenAI HTTP schema end to end: the same endpoints, the same request and response bodies, the same streaming format. You do not install a Merius SDK or learn a new client — any OpenAI-compatible library works once you point it at our base URL and pass a Merius API key.
Under that familiar surface, every request runs on hardware we own and operate: B200/B300 (NVIDIA Blackwell) GPUs in EU and US datacenters. You get transparent per-token pricing, EU data residency on request, and no prompt or completion retention.
Already using the OpenAI SDK?
Skip ahead to Authentication and Quickstart — the only lines that change are your base URL and key.
What you get
OpenAI-compatible
Drop-in /chat/completions, /completions, and /models endpoints. Keep your SDK and request
shape; change one line.
Open models, our GPUs
Open models served on owned B200/B300 hardware — not resold cloud capacity.
Streaming, tools, JSON
Server-sent-event streaming, function calling, and structured outputs, all in the OpenAI format you already use.
EU + US, zero retention
EU-only routing on request, GDPR-compliant, no prompt or completion storage.
Make your first request
Three steps and you are calling a model:
- Create a Merius account and generate an API key in the dashboard.
- Point your OpenAI client at the Merius base URL (the one line that changes).
- Call
/chat/completionswith any model slug we serve.
curl https://api.merius.ai/v1/chat/completions \
-H "Authorization: Bearer $MERIUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "z-ai/glm-5.1",
"messages": [{"role": "user", "content": "Hello"}]
}'The Quickstart shows the same call in Python and TypeScript. Authentication covers creating and storing keys.