Platform · Verdict API

You ask. TapPass decides. Your code enforces.

Rather keep enforcement in your own code than route through a gateway? Ask TapPass before an agent acts. You get allow, hold or block in milliseconds, with the reason, and the same record as the gateway.

✓No credit card needed

Your agent asks
POST /v1/govern
Authorization: Bearer <your TapPass key>

{
  "type": "TOOL_CALL",
  "agent_id": "procurement-agent",
  "session_id": "s_8f21",
  "payload": {
    "tool": "kbc.create_payment",
    "args": { "amount": 1840.00, "currency": "EUR",
              "to": "Verpakking Gent NV" }
  }
}
Procurement agent wants to pay invoice INV-2026-0912.
TapPass answers · 212 ms
{
  "outcome": "needs_approval",
  "reason": "PUR-1",
  "message": "Payments over €1,000 need a person to approve.",
  "decision_id": "dec_7Hq2Lm",
  "approval": {
    "approver": "Lies Peeters",
    "status": "pending"
  }
}
Your code waits. Lies checks the amount, signs with Touch ID, then it runs.
01What comes back

More than yes or no. Everything your code needs to act.

outcomeThe decision

Allow, block or needs approval. A closed set your code can switch on.

messageWords for people

Your rule’s own text, in English, Dutch, French or German, ready to show the user.

modified_payloadAlready fixed for you

When TapPass redacts or reroutes, it hands back the cleaned request to send instead.

mandateProof it was allowed

Every allow carries a signed mandate your downstream systems can verify.

decision_idOne thread, end to end

Report what happened after you acted, so the record shows the outcome too.

02Gateway or Verdict?

Pick per team. Mix them freely.

Both run the exact same rules and write to the same record. Many teams start with the gateway and move one product to the Verdict API.

GatewayGovernance live in minutes
  • ✓No code changes, just a base URL
  • ✓Redaction and routing applied for you
  • ✓Best for agents you did not build yourself
See the gateway
Verdict APIEnforcement in your own code
  • ✓You already run Kong or your own API layer
  • ✓Governance shipped inside your product
  • ✓Your traffic never leaves your path
Get an API key
Built for the hot pathA latency budget per stage keeps each check around 200 ms, against model calls that take seconds.
You choose the failure modeIf TapPass cannot be reached, fail closed and block, or fail open and log. Your call, per integration.
The same signed recordEvery verdict is chained and replayable, exactly like calls through the gateway.
Questions

The Verdict API, in plain answers.

Something else on your mind? Talk to our team.

When should we use the Verdict API instead of the gateway?

When you would rather keep enforcement in your own code: you already run an API gateway such as Kong, you ship governance inside your own product, or your traffic must stay on its current path.

What does a verdict contain?

The outcome, a message written for people, any changes TapPass already applied such as redaction, a signed mandate when the action is allowed, and a decision id to report what happened next.

How fast is it?

Each verdict takes around 200 ms, with a latency budget per stage.

What if TapPass cannot be reached?

You choose per integration: fail closed and block, or fail open and log.

Do the gateway and the Verdict API share rules?

Yes. They run exactly the same rules and write to the same signed, replayable record, so you can mix them team by team.

Ask before your agents act. Your first verdict in minutes.

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