Skip to content
XEVRION
Menu
How it works

Ask, decide, prove

Five steps between an agent's idea and its action.

Step 1

Your agent asks

A few lines of code send the proposed action to Xevrion before it runs.

docs.xevrion.co.uk / sdkExample data

TypeScript

npm install @xevrion/sdk
import { Xevrion } from '@xevrion/sdk';const x = new Xevrion({ key });const d = await x.review({  agent: 'refund-agent',  action: 'refund.issue',  payload: { amount: 540 },});

Signed webhook

POST /hooks/xevrionx-xevrion-signature: t=…,v1=…{ decision: 'approved' }→ 200 retry-safe

Step 2

Your rule decides who answers

Auto-approve, one reviewer, four-eyes, or reject. You write the rule.

app.xevrion.co.uk / policies / refundsExample data

Rules, top to bottom

First match wins
  • Risk is criticalNever auto-approved2 reviewers
  • Refund over £500refund.issue2 reviewers
  • Refund up to £50, confidence 0.9+refund.issue · low riskAuto-approve
  • Everything elseDefault1 reviewer

Try an action

Before it goes live
Action
refund.issue
Amount
£540
Confidence
0.82
Matched
Rule 2
Outcome
Two reviewers

The same rule as code

// policies/refunds.yamlwhen: refund.issue  amount: > 500then: require 2 reviewerswhy: Over the £500 limit

Step 3

A person answers

They see the facts and decide. The right people are nudged in Slack, Teams or email.

app.xevrion.co.uk / inboxExample data

Waiting for you

4 open
  • Refund £540 to order 88231refund-agent · 2 min1 of 2
  • Close 14 stale ticketssupport-agent · 6 min0 of 1
  • Waive £1,200 late feebilling-agent · 9 min0 of 2
  • Email draft to customersupport-agent · 14 min0 of 1

Refund £540

refund-agent
Why asked
Over the £500 limit
Rule
Two reviewers must agree
Answers
1 of 2
Order
88231 · paid in full
Keys
A approve · R reject · E edit

Decision trail

  1. Agent proposed10:41
  2. Priya approved10:43
  3. Waiting for a second reviewer
  4. Signed receipt

Step 4

Your agent gets a pass

An approved action carries a short-lived signed token that your executor checks.

docs.xevrion.co.uk / action-tokensExample data

Your agent presents the token

POST /payments/refundx-xevrion-token: xt_4c9…{ order: 88231, amount: 540 }// Change the amount to 541:→ rejected: action does not match

What the token locks

Action
refund.issue
Amount
£540
Expires
In 5 min
Uses
1 of 1

Life of a token

  1. Person approves
  2. Token issued, 5 min
  3. Used once by your agent
  4. Second use refused

Step 5

The record is sealed

The decision is signed and added to the chain. Anyone can check it, offline.

app.xevrion.co.uk / proof / logExample data

Signed checkpoints

Every hour
  • #9,40248,211 decisionsLatest
  • #9,40148,198 decisionsSaved
  • #9,37847,731 decisionsSaved by you
  • #9,10044,010 decisionsSaved by auditor

Consistency check

#9,378 → #9,402
  1. Old checkpoint is a prefix
  2. 480 new decisions only added
  3. No fork between two readers
  4. Nothing removed or rewritten

Check it yourself

$ xevrion verify log \    --from 9378 --to 9402consistent: trueadded: 480, removed: 0

Know what your agents did.

Start free. Guard your first agent in a few minutes, and keep a record anyone can check.

  • Free plan, no card
  • Signed, chained decisions
  • Checked offline, without us