Skip to content
New kind of attack — caught and fixed before it was publicly known·Read the timeline
Agent gateway & marketplace operators

You operate the trust chokepoint. Your enterprise buyers won't accept a security cert you issued about code you host.

Self-attestation is structurally worthless — SOC 2, ISO 42001, and EU AI Act reviewers all toss it. Probity is the independent auditor baked into your runtime, signing verdicts anyone can verify. The one piece of the trust stack you can't build yourself.

You can't grade your own homework.

Hosting the code and issuing its security verdict is a conflict of interest by construction. Your customer's security team knows it; their procurement team blocks on it.

The structural problem

Separation of duties — the reason auditors exist.

Vercel can build a sandbox. AWS can add isolation layers. What neither can do is issue an attestation a compliance officer accepts — because a host grading its own code is the exact failure mode audit frameworks were built to prevent.

Probity is independent of your infrastructure by design. We sign the verdict. You hand the bundle to your customer. Their auditor re-verifies it offline — after we sign, we never touch it again.

What you get

The independent trust signal your sales motion has been missing.

Gate every agent or third-party tool at connect-time: a signed verdict before it touches your customers' data. Keep the ones that pass inside the sealed runtime — every action gated, signed, frozen on a catch.

Surface it as your own feature: your brand on the Trust Receipt, Probity's public key as the independent backstop. That closes the procurement conversation that stalls at “who attests to this?”

Tamper-evident proof of exactly what ran.

When a marketplace tool goes rogue, logs aren't enough. You need a tamper-evident, independently verifiable record that your platform did everything right — and that the liability sits with the tool author, not you.

What the Trust Receipt contains
PASS · gate · tool: acme-crm-sync · verdict: contained
egress: 3 destinations · all in declared allowlist
0 secrets left the box · signed by probity.pub
$ python3 probity-verify.py … → signature OK · verdict PASS

Your customer's auditor verifies it from the browser, CLI, or CI. The verdict is deterministic and cryptographically bound: not a log you could have edited, not an AI opinion that varies by run.

Bake the independent auditor into your runtime.

One integration. The Gate at connect-time, the Runtime in production, an independent signed receipt for every enterprise buyer who asks who attests to this.

Get access

Run your agents through Probity.

A few details about your setup and we'll get you gating agents fast.