Serverless inference5 models · OpenAI and Anthropic compatible

Open model inference,
engineered for production

An OpenAI-compatible API you migrate to by changing three settings. Every request traceable, every cent explainable, upstream failures handled without you.

POST /v1/chat/completions · req_01JQ8N4W7X2KExample request
Request
{
  "model": "deepseek-ai/DeepSeek-V4.1-Flash",
  "messages": [{ "role": "user",
    "content": "Summarise this contract" }],
  "stream": true
}
Route
  1. 1route-aTimed out at 800 ms · not billed
  2. 2route-bServed · switched before the first byte
First token186ms
Throughput212tok/s
Total1.24s
Cost, line by line
Input · 1,204 tokens × $0.15 / M$0.000181
Output · 386 tokens × $0.60 / M$0.000232
Failed attempt on route-a$0.000000
Charged$0.000412

Teams building on GridPort

  • Northwind
  • Lumora
  • Parallax Labs
  • Helioform
  • Quanta Bio
  • Orbitpay
  • Velaworks
  • Kitefin
  • Monolith Data
  • Brightwave
  • Cinder & Co
  • Tessellate

Model ecosystem

01Models live5

From 3 publishers, one catalog and one price source.

02Gateway overhead target<50ms

Design target for the time the gateway adds on top of the upstream first token. Measured latency per model is on each model page.

03SLA uptime99.9%

Monthly, for the serverless API, backed by service credits.

04Deprecation notice30d

By email and in a response header, before any model retires.

Why GridPort

Compatible is the floor, not the point

The real friction in migrating is parameter differences. The real friction in debugging is an upstream you cannot see. Both are built into the product.

gateway streamsample data
ModelRequest IDTTFTCostStatus
ObservabilityEvery request, accounted for

Latency, tokens, cost and every routing attempt are recorded per request and kept for 90 days. Nothing about a bill is a mystery you have to reconstruct.

req_01JQ8N4W7X2K502
upstream_timeout

This was not a problem with your request.

Replay in PlaygroundRouting trail
DebuggingRequest-level debugging

Every request carries a Request ID. The failure reason, the suggested fix, the routing trail across attempts, tokens and cost sit in one drawer, and replay in the Playground.

production-backendsk-tf-…a41c
2 modelsIP allowlist$50 / month
Budget this month$38.20 / $50
ControlFine-grained keys and budgets

Model allowlists, IP allowlists, key budgets, project budgets and three-stage balance alerts. Every block returns a specific error code; a non-streaming request already running completes, and a stream stops at its next funding segment.

DeepSeek V4 FlashLast hour · sample data
First token p50
186ms
Throughput
212tok/s
Success rate
99.8%

Sample chart: first-token latency stayed near 186 ms over the last hour; when an upstream slowed down, the route was switched before the first byte.

HealthTransparent speed and health

Model pages show first-token latency, throughput and success rate from the past hour. A failing route is switched before the first byte, and the switch is written to the headers.

Migration

Three lines change.
Your code keeps running.

The official OpenAI SDK works unpatched, and the migration assistant walks you through what to change. Parameters the platform does not know are ignored and named in the x-tf-ignored-params response header instead of failing the call. A parameter that needs a capability the model lacks, such as tools on a model without tool calling, is refused with 400 unsupported_parameter.

  1. 01/Point base_url at the platform
  2. 02/Swap in a platform API key
  3. 03/Change model to a platform model ID
import os
from openai import OpenAI

client = OpenAI(
    base_url="https://gridport.ai/v1",    api_key=os.environ["GRIDPORT_API_KEY"],)
stream = client.chat.completions.create(
    model="deepseek-ai/DeepSeek-V4.1-Flash",    messages=[{"role": "user", "content": "Hello"}],
    stream=True,
)
for chunk in stream:
    if chunk.choices and chunk.choices[0].delta.content:
        print(chunk.choices[0].delta.content, end="", flush=True)
print()
Enterprise

Dedicated endpoints, custom models and compliance controls, enabled on request

Execution regions are written into the contract, and only routes with proof of location count. How it works →

  • Dedicated endpoints
  • Custom models
  • SSO
  • Audit logs
  • Zero data retention
  • Data residency
  • Bank transfer & contract credit
Contact sales

Your first call in ten minutes

Sign up, create a key, copy the sample, get a response. There is no one you need to talk to.