Time to the first governed call
Adapters for each SDK and provider come first. Your first tool rule runs after them.
Keep the SDK you use. Change the base URL and the key, and the rules apply from the next call.
Routing model calls is a sprint. Deciding every tool call, scanning every boundary and proving it afterwards is the project. Here is what building it involves, and what Verosek gives you instead.





Four systems to build, wire together and keep running.
One layer. Change the base URL and the key.
In-house gateways start as a proxy. Production adds the rest, one requirement at a time.
Pick what your agents do. Each choice adds the components your team would build and keep running; Verosek ships all of them as one layer.
What your team would build
With 4 systems, add the glue: retries between the systems, one identity across them, and someone on call for all of it.
Book a call12 components to build and run. With 3 systems, add the glue: retries between the systems, one identity across them, and someone on call for all of it.
9 components to build and run. With 2 systems, add the glue: retries between the systems, one identity across them, and someone on call for all of it.
3 components to build and run. One system today; the glue arrives with the second.
0 components to build and run. None of these yet? Then a thin proxy will do for now. Come back when your agents start calling tools.
An adapter for every SDK and provider
An adapter per SDK and per provider, with streaming and tool-call deltas translated both ways.
Three SDKs, unchanged
OpenAI, Anthropic and Gemini SDKs work unchanged against OpenAI, Anthropic, Google, Azure, Ollama and any OpenAI-compatible server. Errors come back in the caller's own SDK shape.
Middleware for every tool
Middleware that knows which tools each agent may call, and with which arguments.
Per-key, per-tool rules
A call the request did not offer is refused and never run. Tools the gateway runs obey per-key, per-tool rules for SQL, NoSQL, key-value, search, documents, filesystem, API, messaging and more. Watch mode shows what a rule would have blocked before it enforces, data-flow rules flag or stop untrusted tool results that try to choose where data goes, and a tool Verosek runs is held back if its definition changes.
A query parser you maintain
A query parser, or string matching that misses the cases that matter.
Decided from the parsed query
SQL is decided from the parsed query: operations, tables, flagged columns, row bounds and read-only mode.
A scanner wired to each boundary
A PII library, an injection classifier and a secrets scanner, each wired to each boundary.
Four boundaries, with Shield on
With Shield on: prompt injection and jailbreaks, personal data and secrets in inputs, outputs, tool arguments and tool results, and hidden instructions in tool results. Rules block; model checks flag.
Logs your auditor has to trust
Request logs, written by the system being audited.
A sealed trace for every request
Every request is a trace of typed steps, scrubbed of secrets and personal data and sealed with HMAC-SHA256. On a self-hosted deployment, an auditor you give the verification key checks it offline with one CLI command, and decisions also go to a signed log a third party can check with public keys. EU AI Act and NIST AI RMF reports come from the stored traces.
A failure mode for every dependency
A failure mode chosen for every dependency, or a silent pass when one breaks.
Fails closed
A check that cannot run answers 503 with Retry-After, never a pass. A request the audit trail cannot record is refused before anything runs. Text let through unread is named in a response header.
A vault and an OAuth flow per server
A vault, an OAuth flow per server, and rotation.
100 connectors, credentials sealed
100 connector templates, with OAuth and PKCE where the server needs it. Credentials are encrypted at rest with AES-256-GCM and never returned.
Fallbacks you keep in step
Fallbacks, retries and limits per deployment, kept in step across instances.
Weighted routing with fallback
Weighted choice across your deployments, fallback by priority, cooldown after failures, per-deployment limits, and a residency rule checked against every candidate before any call.
Key lifecycle and tenant scoping
Key lifecycle, roles and tenant scoping on every query.
Hashed keys, scoped per organisation
Virtual keys are stored only as hashes and carry their models, budget, rate limits and expiry. A block takes effect on every instance from the next request. Each organisation reads only its own data, with admin, auditor and user roles.
High availability in the request path
High availability, migrations and upgrades for a service in the request path.
Several instances, one leader
Several instances behind a load balancer on one Postgres and one Redis, with fleet jobs on an elected leader. Migrations run as a one-off before a new version starts.
Your backlog, forever
Every provider and protocol change lands in your backlog.
Lands in the gateway
Changes land in the gateway, not in your application.
Already built part of it? Keep it. Verosek routes to any OpenAI-compatible server, so your existing gateway can sit behind it while Verosek decides the tool calls and keeps the record.
Build a thin proxy if you call one provider, your agents touch no real systems and nobody will audit them. Buy when agents call tools on production systems, you run more than one provider or SDK, or someone will ask you to prove what an agent did. That second list is where in-house gateways grow into platform teams.
Mostly engineering time: adapters for each SDK, rules for every tool call, scanning at each boundary, a sealed audit trail and a credentials vault, then people to keep it current as providers and protocols change. The scope picker on this page shows which of those systems your agents would need.
You can, and the move takes two values. What you cannot get back is a record of the calls made before it. Verosek does the routing as well, with budgets, rules, scanning and the record on one key. If you want to keep your proxy for now, Verosek routes to any OpenAI-compatible server, so it can stay behind it.
Two values in the SDK you already use: the base URL, and the API key, which becomes a Verosek virtual key. Your OpenAI, Anthropic and Gemini calls keep their shape.
An app that runs its own tools leaves by changing two values. Tools Verosek ran for you go back to your own code or MCP client.
Yes. Shield checks can run in log-only or flag mode against live traffic before they enforce, and tool rules can run in watch mode, which records what a rule would have blocked. You switch a check or a rule to enforce once it stops flagging real work.