How it works
Ask, decide, prove
Five steps between an agent's idea and its action.
Review queueWaiting 2All agents
- refund.issuerefund-agent · Order 88231 · £540.00Needs two6mWaiting
- invoice.voidbilling-agent · Invoice 5512 · £1,240.00Needs one21mWaiting
- email.sendsupport-agent · Customer 4410One answered1mApproved
- payout.createpayout-agent · Vendor 207 · £12,000.00RulenowRefused
- db.updatebilling-agent · Plan changeRule12msLet through
- ticket.closesupport-agent · Case 9121Rule7msLet through
Request #4822
refund.issue for order 88231
- Agent asked14:01
- Rule matchedRefunds, rule 2 of 5
- Priya, FinanceApproved 14:02
- Sam, Support leadWaiting · asked in Slack
- Record sealedAfter the second answer
- Agent
- refund-agent 2.4
- Action
- refund.issue
- Amount
- £540.00
- Customer
- Order 88231
- Rule
- Refunds · over £500: two must agree
- Deadline
- Today 16:00 (business hours)
Median wait today3 min
Step 1
Your agent asks
A few lines of code send the proposed action to Xevrion before it runs.
TypeScript
npm install @xevrion/sdkimport { 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-safeStep 2
Your rule decides who answers
Auto-approve, one reviewer, four-eyes, or reject. You write the rule.
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 limitStep 3
A person answers
They see the facts and decide. The right people are nudged in Slack, Teams or email.
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
- Agent proposed10:41
- Priya approved10:43
- Waiting for a second reviewer
- Signed receipt
Step 4
Your agent gets a pass
An approved action carries a short-lived signed token that your executor checks.
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 matchWhat the token locks
- Action
- refund.issue
- Amount
- £540
- Expires
- In 5 min
- Uses
- 1 of 1
Life of a token
- Person approves
- Token issued, 5 min
- Used once by your agent
- Second use refused
Step 5
The record is sealed
The decision is signed and added to the chain. Anyone can check it, offline.
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- Old checkpoint is a prefix
- 480 new decisions only added
- No fork between two readers
- Nothing removed or rewritten
Check it yourself
$ xevrion verify log \ --from 9378 --to 9402consistent: trueadded: 480, removed: 0Know 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
Signed decision
- Decision
- Approved, 2 of 2
- Action
- refund.issue, £540
- Rule
- Two reviewers must agree
- Sealed
- 14:09, key 7f2c
- Hash
- 5be2…7c44
Checked on your own machine
- Signature matches the public key
- Decision is in the log
- Every link before it adds up