Tripwire
Connect an agent
Checking dashboard mode…

Agent payments,
under control.

See what your agents want to pay, which checks ran, and why each request was approved, blocked, or held for review.

View activity

Code rules · SERV · Reppo · your passkey · a receipt for every decisionSee how checks work ↓
01Payment activity

Payment decisions

See the outcome, reasons, and cost of each check. Open a receipt for the full trail.

Decision feed

Connecting…
Loading payment activity…
03How a payment is checked

Four rungs. Each one only runs when the one below can't settle it.

Any rung can block. Any failure, whether a timeout, malformed output or missing verdict, escalates instead of approving. Nothing is paid until the receipt says approved.

01 / 04

Code rules

Free, instant, on every payment.

Allow and deny lists, caps, your plain-English rules, lookalike payees, duplicate and split payments, unusual amounts, hidden instructions, and payees missing from Kite's directory.

Runs on every paymentCost ~$0
02 / 04

SERV reasoning

Does it fit the agent's task?

Does this purchase follow from the agent's task? A strict JSON schema validated in code, with SERV's PromptGuard and Shadow Agent on every call.

Runs at ≥ $1 or new payeeCost ~$0.0008
03 / 04

Reppo verdict

An independent second opinion.

An independent network evaluation: accept proceeds, revise goes to you, reject blocks. Low-confidence accepts also go to you.

Runs at ≥ $20 or a serious flagCost $0.22
04 / 04

Your passkey

The last word is yours.

A one-shot Kite session scoped to exactly this payment. You approve it with your passkey, and the payment goes through that session only.

Runs when Reppo says re-evaluate, or the price can't be confirmedCost one tap

Autonomous, inside hard limits. Agents pay on their own up to the limits you set. Anything bigger, stranger or off-task waits for an independent verdict or your passkey, and nothing is paid until the receipt says approved.

Go live with Kite Security model
05Integrations

Built on SERV, Reppo and Kite.

In the demo, a tier without credentials runs an offline stand-in. With real payments, it hands the decision to you instead. Every receipt says which mode answered.

06Connect an agent

One config entry. Every payment goes through Tripwire.

Tripwire ships as an MCP server. Any MCP-capable agent gets a tripwire_pay tool and pays through it instead of calling Kite directly.

Claude Code

one line
shell

          
Any MCP client
mcp.json

          
json

        

        

          
Tools the agent gets

          
    
            
  • tripwire_pay
    Request a payment. Returns approved, blocked or pending with the receipt. Blocked means stop: the agent is told not to work around it.
    • 
            
  • tripwire_receipt
    Look up a decision: every check, its cost and reasons.
    • 
            
  • tripwire_policy
    Allowance left, caps, thresholds and rules, so the agent can plan within them.
    •