swfte
AccediParla con il nostro teamCrea con l'AI

01 Inference

Every model,one governed door.

Connect puts one API in front of 50+ model providers, routes every request by your rules, fails over when a provider is down and stops spending at the caps you set.

Build with AI Talk to our team

[ 01 ] InferenceRoute. Fail over. Cap spend.

01 In this layer

Models and the gateway in front of them.

  • Routing rules per workspaceAvailable
  • Failover across providersAvailable
  • Usage caps and audit eventsAvailable
  • Open-weight models on your infrastructureDesigned for

Connect

Model gatewaySelf-deployModel providersConnect in the EUConnect securityMCP GatewayApplication GatewayLLM ObservabilityiPaaS

Run models

Deploy modelsOpen-source model testingModel catalogue

Model directory

AI ModelsAI LeaderboardAI Pricing IndexAI Cost Calculator

03 SEE IT WORK

See Connect at work.

Universal keys

A key per person. Every provider they're allowed.

Issue keys from the Access page. By default a key reaches every provider your workspace has connected; narrow it when you need to. Secrets are shown once, rotate without downtime, and disappear when the person leaves.

See every screen

02 [ 01.A ]

A change of model is a setting, not a project.

One OpenAI-compatible API in front of 50+ model providers. Switch, route and fall back without rewriting the application.

Available

03 [ 01.B ]

When a provider fails, the work moves on.

Fallback chains move a request to the next model when a provider is down or rate-limited.

Available

04 [ 01.C ]

Open-weight models on infrastructure you control.

Run open and private models in your own environment behind the same gateway. Self-deploy is on request.

Designed for

[ 01.D – 01.O ] INSIDE CONNECT

Inside Connect, screen by screen.

Twelve chapters, each a real screen from the console, assembling as you scroll.

D1 [ 01.D ]Universal keys

A key per person. Every provider they're allowed.

Issue keys from the Access page. By default a key reaches every provider your workspace has connected; narrow it when you need to. Secrets are shown once, rotate without downtime, and disappear when the person leaves.

Available
  1. 01Issue
  2. 02Narrow
  3. 03Reveal once
  4. 04Rotate and revoke

D2 [ 01.E ]Providers and gateway

Bring your own keys. Or don't.

Connect providers with your own credentials, or run on Swfte credits. One base URL speaks the OpenAI, Anthropic and Responses protocols, and only routes you've allowed are exposed. Your own keys are never billed twice.

Available
  1. 01Connect a provider
  2. 02One endpoint, three protocols
  3. 03Who pays, on every request
  4. 04Only what you allow

D3 [ 01.F ]Models and fleet

Text, image, speech, video. Hosted or yours.

Filter the catalogue by what a model can do, deploy open models on your own GPU pools, and wire in MCP servers. Everything your workspace runs sits in one fleet view.

Available
  1. 01Every modality
  2. 02Your own GPUs
  3. 03Tools via MCP
  4. 04One fleet

D4 [ 01.G ]Routing

Decide where every request goes.

Draw the path on a canvas: conditions on spend, tokens, error rate or time of day, and an ordered chain of models for each branch. Then test a request against your draft and see exactly which rule fires, before anything is spent.

Available
  1. 01Request stream
  2. 02Conditions
  3. 03Model chains
  4. 04Test request

D5 [ 01.H ]Controls

Caps that hold. Labels that don't lie.

Cap spend and tokens for the workspace, a model, a person or a single key. Block, downgrade to a cheaper model, or just alert. Every setting says whether the gateway enforces it. If rules can't be read, credit-funded requests stop before a provider call.

Available
  1. 01Set a cap
  2. 02Hit the line
  3. 03Say what's enforced
  4. 04Fail closed

D6 [ 01.I ]People and seats

Licensed seats. A console for every role.

Team and Enterprise workspaces share licensed seats. Invite people with a role, watch the pool fill, add seats when needed. Owners get the whole console; members get a simple read-only view of their own keys, usage and limits.

Available
  1. 01Invite
  2. 02Seat pool
  3. 03Roles
  4. 04My access

D7 [ 01.J ]Analytics and reports

Slice usage by anything you call a team.

Define your own dimensions (Team, Department, Cost centre, Client) and put people in groups. Then pivot spend and tokens by person, group, key, provider, model or tool, drill in, compare periods, and export the exact view as CSV, Excel or an offline report.

Available
  1. 01Your dimensions
  2. 02Pivot anything
  3. 03Drill in
  4. 04Export and schedule

D8 [ 01.K ]Evaluation

Try models side by side before routing.

Send the same prompt, image or audio to two models and compare the answers, cost and latency. Save the cases that matter to you as test suites and rerun them whenever you change a rule or a model.

Available
  1. 01Compare
  2. 02Any input
  3. 03Suites
  4. 04Rerun

D9 [ 01.L ]Coding agents and SDKs

Point your tools at one URL.

Copy a setup snippet for Claude Code, Codex or your SDK, swap in your Swfte key, and requests go through your rules. Connect tags requests by tool, so you can see usage by tool, by person and by team.

  1. 01Paste
  2. 02Run
  3. 03Which tool works where
  4. 04See it by tool

D10 [ 01.M ]Built to be trusted

Safe defaults, honest screens.

Only the routes you allow are exposed. Secrets are shown once. When something can't be loaded, Connect says so instead of showing a number it made up, and it stops you acting on the wrong workspace.

  1. 01Deny by default
  2. 02Honest when it breaks
  3. 03Right workspace, every time
  4. 04Provider health

D11 [ 01.N ]Across industries

Same console. Your rules.

Whatever you build, the building blocks are the same: keys per person, caps per group, routes per workload, and reports in the shape your business already uses.

D12 [ 01.O ]Why Connect

Everything teams need to use AI with confidence.

One gateway, one console, the controls finance and security ask for, and a view people actually understand.

  1. 01Eight capabilities, one view
  2. 02A connected system
  3. 03Explore each piece

One key per person

Works across every provider your workspace has connected, narrowed when you need it.

Point your tools at one URL

Setup snippets for Claude Code, Codex and the major SDKs.

Licensed seats, live meter

See seats used, reserved and free.

Slice by anything

Your own dimensions: team, cost centre, client. Export the exact view.

Controls that tell the truth

Every setting says whether it's enforced, and unreadable rules fail closed.

A console for every role

Admins manage Access and Controls. Members get My access.

Bring your own keys

Use your provider accounts; your own keys aren't billed twice.

Test before you trust

Dry-run a request against draft rules and compare models side by side.

Build with AITalk to our team
GovernanceAll layersCompute

Frequently asked questions

Come funziona l'API universale?

Connect fornisce un singolo endpoint API compatibile con il formato OpenAI. Puoi passare tra oltre 50 modelli cambiando un singolo parametro.

Come fa il routing intelligente a far risparmiare?

Connect instrada automaticamente le richieste al modello più conveniente che soddisfa i tuoi requisiti di qualità. In media, i clienti risparmiano il 40% sui costi API.

Posso usare le mie chiavi API?

Sì! Puoi usare le tue chiavi di qualsiasi provider, o usare l'accesso condiviso di Swfte per una fatturazione semplificata.

Keep exploring

Guides

Other products

[ 06 ] One platform

Capability and control, in one platform.

Start with one layer and prove it. Add the next when you are ready. The controls come with you.

Build with AI Talk to our team

Deploy a model with Swfte Connect

One gateway, every provider, per-token cost visibility. Swap models without touching your code.

Get an API keyLearn more