OmniArx

Prove your customer said yes to each action your assistant takes.

Each action your assistant takes gets its own signed approval from the customer's phone. Proof from outside the assistant.

Book a session See the actions we protect
What the person sees in your appExample
Send money to a contactNeeds approval
$500.00
To
Matt Lee
Account
Ending 2290
Refused if the lookup picks a different Matt
OmniArx checks the request
Only the approved request runs

Anything different is refused before it reaches your API.

Where a yes has to be proven.

The banks you sell to ask how an action by your assistant gets authorized. A confirmation inside the chat is a record the assistant keeps about itself. OmniArx adds proof from outside the assistant: a signature from the customer's phone for each action.

Send money to a contactNeeds approval
$500.00
To
Matt Lee
Account
Ending 2290
Refused if the lookup picks a different Matt
Pay a card billNeeds approval
$1,240.00
Card
Ending 0917
From
Checking
Refused if the amount changes
Hold a billNeeds approval
Hold
Payee
Internet bill
Until
Next statement
Refused if a different bill is held
Move to savingsNeeds approval
$3,000.00
From
Checking
To
Savings
Refused if the destination changes

How it works.

01

The agent asks

Your assistant calls two tools: one to request approval and one to check it. One chat sentence can hold many actions. Each one is approved on its own.

02

The person answers

Your customer slides to approve each action, in the words they read, then confirms with a fingerprint or face. We never approve a whole chat sentence at once.

03

The API checks

The check in front of the banking API verifies each request. An assistant that skips the tools arrives with no approval and is refused.

Answer the question once for every bank.

Ship OmniArx with your platform and give every bank the same answer to how an action is authorized. Priced per protected action. We show it live in a working session.

  • It works alongside your confirmation step. It adds proof from outside the assistant.
  • Your assistant and your model stay the same. The check sits in front of the API that runs the action.
  • Each approval works once and expires within minutes.

Bring the action
you want to protect.

Tell us what your agent does and which system it calls. We will map the route, the approval screen and where the check goes.

Book a session