Genflos AI Gateway

Store your provider keys, mint one key for your agent, point it at your gateway.

Genflos AI Gateway

pooled spend $0

Flow — how your data becomes a key

Vault secrets, provider APIs and cookie daemons feed the model pool. A key scopes that pool with a budget and grants; calls made with it show up as spend. Click any box to edit that pool.

Vault secrets
Provider APIs
Models pool
Key config
scope
budget · grants
Minted keys
Usage / spend
Tip: click a key in the output box to trace the path it uses.

Flow accounts — Google Veo cookie pool

Each account is a Google login's cookies.jar the daemon rotates over. Auto uses whichever has the most credits; Priority walks your order top-first, auto-skipping dead/empty accounts. Adding "account":"<alias>" to a request always overrides both.

In Priority, drag a card by its ⋮⋮ grip to set the order jobs walk top-first. pin example drops "account":"<alias>" into the sample below.

    
              
    How do I get the cookies? (once per account, ~1 min)
    1. In Chrome or Firefox, log in to labs.google/fx/tools/flow with the Google account you want to pool.
    2. Install a cookie-export extension that saves Netscape format — e.g. “Get cookies.txt LOCALLY” (Chrome Web Store or Firefox Add-ons). It runs on your machine; nothing is uploaded anywhere.
    3. With the Flow page open and logged in, click the extension → Export. It downloads a cookies.txt.
    4. Come back here: type an alias (any nickname for this account), click Upload cookies.txt (or paste the file’s text into the box), then hit Validate & add.

    What happens next: the gateway saves the jar into the pool and checks it against Google live. On success it shows that account’s email + credit balance and the account joins the pool immediately — no restart. A bad or expired export is flagged on screen, never silently saved.

    After it’s in: leave the mode on Auto and jobs route to whichever account has the most credits. Switch to Priority and drag to reorder — jobs walk your list top-first, skipping any account that’s out of credits or de-authed. For a one-off, hit a row’s pin example to drop "account":"<alias>" into the box above; that hard-override wins over the pool on that single request. Google cookies expire every few weeks; when an account stops working, re-export and re-add it under the same alias.

    Studio — Azure GPT Image 2

    Persistent gallery. Drag to upload. Pin refs to the right rail for quick @ (no scroll). Type @ → pick a ref; inserts @"Image name" and attaches pixels. / · Enter. Delete is forever.

    Start creating or drop media
    Quality
    Count (max 10)
    Parallel cap: 4 at a time
    Aspect
    Maps to Azure 1024² / 1536×1024 / 1024×1536

    Higgsfield accounts — subscription OAuth pool

    Each account is a Higgsfield login captured once via Clerk. The gateway stores the OAuth token and refreshes it forever — no re-login. Auto uses the first available; Priority walks your order. Add "account":"<alias>" to a request to override.

    In Priority, drag a card by its ⋮⋮ grip to set the order jobs walk top-first.

      Add an account

      1. A Higgsfield/Clerk login opened in a new tab — log in as the account you want to add.
      2. After login your browser lands on a “can’t reach localhost:8765” page — that’s expected.
      3. Copy that page’s full address bar (it contains ?code=…&state=…) and paste it below. That’s it — email & workspace fill in automatically.

      Quick test

      A quick check that the pool works. Type any Higgsfield model and a prompt — the gateway runs it through one of your pooled logins and shows the result below. Your agents call the same thing over the API; they already know the model names.

      Connect an agent

      Your gateway endpoint
      LLM
      $0
      Media
      $0
      Pooled
      $0
      when (SGT)kindkeyprovidermodelstatuscost

      Vault — your provider secrets

      These are your upstream keys (fal, Azure, higgsfield…). Agents never get these — you give them a key from the Keys tab instead.

      Sealed with AES-256-GCM under a per-tenant key. Only masked values ever come back.
      providerlabelkindsecretstatus

      Keys — what you hand to an agent

      Click a model to scope the key. personal keys can use cookie tools like flow; leave it off for normal API keys. algoscroll lets the key call /v1/algoscroll/* (not live yet).
      aliasspend / budgetmodelsflags

      Add an LLM API

      Goes straight into the router — callable seconds later with any gateway key scoped to it. The key is stored encrypted.
      modelupstreambase URL

      Add a generation / REST API — paste, draft, test, save

      
              
      The upstream key goes in the field above — never inside the recipe. Save unlocks once a test call comes back OK.

      Custom providers

      namekindcost/callsecretcall it as

      Provider balances

      Live where a balance API exists. Providers with none never show a guessed number.

      Routing policy

      This is the fallback every model's route list uses unless a route is pinned (:pin=<provider>).

      Model routes

      Drag a row by its grip (or use the arrows) to set the try-order. Toggle a route off to pull it out of rotation without deleting it. serving now marks the route your current policy would actually pick.

      Models you can call

      modelkindprovideraccess

      Connect an agent in 30 seconds

      Give your agent two things: the key and this endpoint. It reads everything else from /llms.txt.
      Example call (swap in your key):
      Agent docs:

      Raw llms.txt (what the agent fetches)