Skip to content
GenAff
Create account

BYOK gateway / Phase 1

Your keys.
Your models.
One endpoint.

GenAff is an OpenAI-compatible gateway over the provider accounts you already pay for. Connect OpenAI, Anthropic or DeepSeek once, then point your code at one API shape.

Create an accountRead the quickstart
API shape
OpenAI-compatible
Credentials
Yours, encrypted
Markup
None
request path / phase 1
YOUR APPgk_live_…GENAFF/v1route + normalizeyour keys onlyopenaianthropicdeepseek

One OpenAI-compatible shape. Your provider credentials stay encrypted at rest.

request / response

Two planes, deliberately separated.

Your dashboard session and your gateway key are different credentials. The web app never handles a gk_live_ key, and your servers never receive your dashboard token.

/api/v1/*

Dashboard plane

Short-lived access token, provider connections, GenAff keys and usage.

Bearer <session JWT>

/v1/*

Gateway plane

Model discovery and chat completions from your own server or SDK.

Bearer gk_live_…

No silent fallback, no shared keys.

A failed model does not route to another provider. Provider credentials are encrypted at rest and are never returned by the API.

Connected providers

Read live from this deployment. Only providers with an adapter and passing contract tests appear here.

How connections work

What Phase 1 does not do.

We would rather name the boundary than ship a stub that pretends to work.

  • No managed inference. Your provider bills you directly.
  • No credits, subscriptions or mock purchases.
  • No streaming yet. Chat is request/response with stream: false.
  • No password reset. Contact support for account recovery.
  • One connection per provider. Replace the credential instead of adding another.
quickstart / models
export GENAFF_API_KEY="gk_live_YOUR_KEY"

curl https://api.genaff.cloud/v1/models \
  -H "Authorization: Bearer $GENAFF_API_KEY"

Replace the placeholder with a key you create in the dashboard. The web app never stores or proxies this key.