Migrate from OpenAI to GPU Flow in 15 minutes

GPU Flow speaks the same protocol as OpenAI. If your code already uses the OpenAI SDK, migrating means changing two lines (the base URL and the API key) and picking an equivalent model from the catalogue. Nothing else changes: messages, streaming, function calling and parameters all work the same.

In return, your data is processed in Spain (never leaving the EU), you invoice in euros and you start with 50 € of free credit. This guide takes you from the first curl to production.

Create your account and API key

Sign up with email or Google: you get 50 € of free credit, no card. The API key is created from the user dashboard and copied right there, because it is shown only once. It is never sent by email.

Change the base URL and API key

Point the OpenAI client at api.gpuflow.ai/v1 with your new key. The rest of your code stays untouched.

python

# Antes / Before
client = OpenAI(api_key=os.environ["OPENAI_API_KEY"])

# Después / After
client = OpenAI(
    base_url="https://api.gpuflow.ai/v1",
    api_key=os.environ["GPUFLOW_API_KEY"],
)

Pick the equivalent model

GPU Flow serves 17 open-source models. Swap your OpenAI model for the equivalent in the catalogue based on your case: fast and cheap, or maximum capability.

if you used	use	for
gpt-4o-mini	qwen-3.5-9b	Fast chat, high volume, low cost
gpt-4o	deepseek-v4-pro, glm-5.3-nvfp4	Demanding reasoning and code
o-series	deepseek-v4-pro + reasoning.effort	Long chains of thought

Streaming, tools and reasoning: same as before

Streaming responses (stream: true) and tools (function calling) work with the same OpenAI format. You can also control the reasoning budget with reasoning.effort ("low", "medium", "high" or "none").

python

resp = client.chat.completions.create(
    model="deepseek-v4-pro",
    messages=[{"role": "user", "content": "..."}],
    stream=True,
    extra_body={"reasoning": {"effort": "high"}},
)

Using the Anthropic SDK? That too

If your stack uses the Anthropic SDK, point baseURL at api.gpuflow.ai and use /v1/messages with the same models. No need to maintain two integrations.

What to keep in mind

You consume against your prepaid euro balance: if it runs out, the API returns 402 and you top up from the dashboard. Under heavy spikes it may return 429 or 503 with a Retry-After header; retry with backoff. Exact model names and prices are on the pricing page and in the documentation.

Try it with 50 € free

Create your account, change the base URL and run the first curl against any catalogue model. No card, with your data in Europe.

start free read the documentation