Platform · Gateway

Repoint one URL. Govern every call.

An OpenAI-compatible gateway between your agents and every model and tool they use. Each call is checked against your rules before it runs. No app changes, and your keys stay yours.

✓No credit card needed

Your agents
PAProcurement agent
SOSales outreach
Claude Code
CCCustomer care
TapPass gatewayone hop · every call
✓Who is calling · Procurement agent, for Pieter Vosidentity
✓Sensitive data · IBAN redacted before it leavesdata
!Your rules · PUR-1 holds payments over €1,000rules
✓Route · Mistral Large, hosted in the EUrouting
Models and tools
Mistral
OpenAI
Anthropic
MCP · GitHub, Slack, banking
01Setup

Two lines of config. No agent rebuilt.

  1. 1Point the base URL at TapPassAny OpenAI-compatible SDK or framework already accepts it.
  2. 2Use your TapPass keyTapPass calls the provider for you, with the model keys you added once.
  3. 3Watch firstEvery call lands on the record. Nothing is blocked until you switch a rule to enforcing.
.env
export OPENAI_BASE_URL="https://<your-tappass>/v1"
export OPENAI_API_KEY="<your TapPass key>"   # not your OpenAI key
Every OpenAI-compatible SDK and framework picks this up. Nothing else changes.
02In the request path

Enforcement, visibility and evidence. In one hop.

Transparent proxyAn OpenAI-compatible endpoint. Change the base URL and governance is live.OpenAI-compatibleno SDK
Rules on model callsPersonal data redacted and prompts routed by your rules, before a model sees a thing.redactionEU routing
Rules on tool callsPer-tool permissions on MCP traffic, and a person on the calls that matter.least privilegeapprovals
Live visibilityEvery prompt, response and tool call, in real time, per agent, person and team.per agentper team
A signed recordHash-chained, replayable, and exported to your SIEM as OpenTelemetry.OpenTelemetryreplay
Your keys, in a vaultModel keys stay yours, encrypted in a vault, never on people’s laptops.BYOKencrypted
03On the record

Nothing runs unseen. Evidence is a query.

Every decision streams to the SIEM you already run, as OpenTelemetry. Sensitive content is redacted on the way, and every record is chained to the one before it.

Every call, on the recordstreaming to Splunk
09:41:02allowCustomer care · reply to ticket 4821
09:41:44holdProcurement agent · pay €1,840.00
09:42:10blockSales outreach · export all contacts
09:42:31allowOps copilot · summarise delays
09:42:58redactInvoice clerk · IBAN removed, sent on
SplunkMicrosoft SentinelElasticOTLP
04How it compares

Not another API gateway. Not another guardrail library.

Keep the gateway you run. TapPass adds what it cannot see: which agent is acting, for whom, and whether it may.

CapabilityAPI gatewayKong, MuleSoftGuardrail libraryinside one appTapPass gatewayevery agent, one place
Knows which agent acts, and for whomNoPartly✓
Rules on model callsNo✓✓
Permissions on individual MCP toolsNoNo✓
Holds an action for a person to signNoNo✓
One rulebook across every agent and frameworkPartlyNo✓
Signed, replayable record of agent actionsAccess logsNo✓
Rather enforce inside your own code?Call the Verdict API before an agent acts. Same rules, same record.
Questions

The gateway, in plain answers.

Something else on your mind? Talk to our team.

What does the gateway do?

It sits between your agents and the models and tools they call. Every model call and every MCP tool call passes through it, is checked against your rules, and is then allowed, held for a person, or blocked. Every decision is recorded.

Do we need to change our code?

No. Point the base URL of any OpenAI-compatible SDK or framework at TapPass and use your TapPass key. Your agents keep working as before.

Will it slow our agents down?

Each check adds roughly 200 ms, against a model call that typically takes seconds.

What happens to our model keys?

They stay yours. You add them once, they are kept in an encrypted vault, and TapPass calls the provider on your behalf. Content is redacted in transit and raw data is never persisted.

Is this not just an API gateway like Kong or MuleSoft?

An API gateway routes and rate-limits HTTP. It cannot tell one agent from another, permission individual MCP tools, or hold an action for a person. Keep your API gateway; TapPass adds the agent-aware rules and record on top.

Can we enforce inside our own code instead?

Yes. Call the Verdict API before an agent acts. It runs the same rules and writes the same record.

Repoint one URL today. Govern every call by tomorrow.

Connect one agent and see every call TapPass would have held, stopped or routed elsewhere. Nothing is blocked while you learn.

✓ Free for one person✓ No credit cardBacked by Start it @KBCVLAIO✓ EU hosted✓ Built in Belgium✓ Your own model keys✓ Encrypted at rest and in transit✓ DPA on request