OmniArx

Make sure your AI only pays what you approved.

Security for AI actions. You approve each action on your phone. Only that exact action runs. Anything changed is refused.

For any team whose AI takes real actions: moving money, sharing data, granting access or changing systems.

An action, checked against the approval

“Pay Alex $250 for the repair.”

Payment approvalReady to review
$250.00 USD
Recipient
Alex Morgan
For
Home repair
Review the details before approving
OmniArx checks the request
Request readyWaiting for approval

$250.00 to Alex Morgan

Nothing runs before approval

The API waits for a signed approval.

From the moment a person says yes
to the moment your API acts.

01 The agent asks
02 The person answers
03 The API checks

Your agent can read instructions
nobody gave it.

A webpage, document or message can hide instructions planted by someone else. If the agent follows them, its next action changes.

supplier-update.pdf External content
SUPPLIER UPDATE

Your next invoice

Thank you for your business. Your account details and payment schedule are attached below.

What else is in this document?

The customer asked it
to pay a supplier.

A familiar task becomes a different action: the hidden instructions change who gets paid. The agent may still call the task “paying the invoice.”

OmniArx builds the approval screen from the request itself, never from text the agent wrote. The person sees the real payee. A request that differs from what they signed is refused at your API.

See what happens when details change

See what happens when
the details change.

A person approved a $250 payment to Alex. Send the original request, then change the recipient or the amount.

The signed approval

$250.00 USD

To Alex Morgan

Approved on their phone
Purpose
Home repair
Use
Once
These details are signed.
The request about to run
OmniArx comparison

Does it match
the approval?

Check the request to see whether your API would accept it.

Illustration only. Nothing is paid, sent or signed on this page. The real check is shown live in a working session.

The approval has to survive the trip to your API.

  1. 01

    The agent asks

    Your agent proposes an action. Nothing runs yet. OmniArx builds the approval screen from the request itself, never from text the agent wrote.

  2. 02

    The person answers

    The screen is drawn on their phone, in a frame that refuses to sign if anything covers it. Sliding to approve opens a fingerprint or face check. Only then does a key held in the phone's hardware sign the text on screen and the request it describes.

  3. 03

    The API checks

    The OmniArx proxy in front of your API checks the signature and spends it once. The request that was read is the request that runs. Anything else is refused by name. If anything is missing, it refuses. It never guesses.

A hand holding a phone that shows an approval screen with an Approve button

Industries: pick the action you need protected.

The same check works wherever an agent acts. Each page shows the actions it protects in that industry.

A hand holding a phone that shows an approval screen with an Approve button

One SDK in your app.
One check in front of your API.

You build OmniArx into the app your customers already use, and put the check in front of the API that runs the action.

  1. In your appThe OmniArx SDK for Android and iOS, which Flutter apps use too. It sets up the phone, shows the approval screen, asks for a fingerprint or face, and signs with the phone's hardware key. Your app keeps its own look around it.
  2. In front of your APIThe OmniArx proxy checks the token, spends it once and forwards the request unchanged. Your API is not modified.
  3. For your agentsAn MCP server lets an agent ask for approval and wait until it verifies.
Read the agent reference

Submitted to the IETF as individual Internet-Drafts. An Internet-Draft is not an IETF standard.

Know what
you’re trusting.

Clear boundaries are part of the protection.

Where it runs, where data goes and how to verify us

Does OmniArx stop prompt injection?

No. An agent can still read and follow planted instructions. OmniArx makes sure the result cannot run without a matching approval. The approval screen is built from the request, so the person sees the real details. A request that differs from what they signed is refused. Protection covers only the routes behind the OmniArx check.

What if the person approves the wrong thing?

The signature proves what was shown and approved. It does not prove the person understood it. If the screen shows the wrong payee and they approve, the approval is valid. That is why the screen is built from the request itself, and why it refuses to sign when anything covers it.

Does my API need to change?

No. The check runs in a proxy in front of your API, which forwards the request unchanged. You run the OmniArx proxy in your own infrastructure, point the route at it, declare the lowest assurance the route accepts, and map the route to the action the person approves. The person approves in your own mobile app, with the OmniArx SDK for Android or iOS inside. Flutter apps use the same SDK. Coverage for customers without the app is in design.

What happens when a check fails?

The request is refused and never reaches your API. On the wire the answer is a plain 403 that names nothing. Your operator log records the cause by name, for example a changed request, a reused approval or a key that is not enrolled. A new cause gets a new name. We never widen an old one to cover it.

What if something is missing or set up wrong?

The check says no. It never guesses and never falls back to a weaker check. Each protected route must state how strong an approval it needs. A route that states nothing will not start. If the proof from the phone is missing or weaker than the route needs, the request is refused.

Does a match guarantee the right outcome?

A match proves the request is the one that was approved. It does not prove that outside conditions are unchanged, such as an account balance, or that the action will succeed. An approval lasts minutes at most and works once.

Can I use the SDK in my own app?

Yes. The SDK goes into your existing Android or iOS app. Flutter apps use the same Android and iOS builds, so no extra plugin is needed. It shows the approval screen inside a protected frame, runs the fingerprint or face check and signs with a key held in the phone's hardware. It also checks the phone for signs of tampering, such as rooting or hooking tools. Contact us for access to the SDK.

Can I see it working?

Yes, in a live working session. We drive it and you name the case. There is no public download of the verifier or the test kit.

What can an AI agent find on this website?

The machine-readable reference gives a product description, specification links, integration requirements and limits. It is an evaluation resource. It is not a live approval API or an integration credential.

Priced per protected action,
not per seat.

The value is the action, so that is what we price. Every deal starts with a conversation, because every deal starts with a route map.

All prices in USD · Proposal, subject to the design-partner round and final agreement.

By invitation

Design partner

$0 USD

Up to 50,000 protected actions / month. Named reference, witnessed evidence session and joint measurement of one route.

Book a session
To prove one route

Pilot

$30,000 USD fixed · 90 days

One route
one enforcement point

  • Test replay first, then read-only live traffic
  • Witnessed evidence session on your own results
  • Fee credits in full against Entry if signed within 90 days of pilot close
Book a session
For a focused integration

Entry

$150,000 USD / year

Up to 500,000
protected actions / month

  • One channel
  • One enforcement point
  • Standard refusal set
Book a session
For growing deployments

Scale

$250,000 USD / year

Up to 3 million
protected actions / month

  • Multiple enforcement points
  • One confirmation covers a plan and its alternatives
  • Assurance floor per route
Book a session
For platforms and vendors

Platform

Custom pricing in USD

Above 3 million
protected actions / month

  • Embed in your platform
  • Per-action rate, negotiated
  • Channel and vendor partnerships
Book a session

Proposal. Scope is confirmed in the contract. Overage is priced per thousand protected actions. There is no self-serve checkout.

Bring the route
you want to protect.

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

hello@omniarx.ai

What a session covers

  1. The details a person sees and approves
  2. What happens when a request changes
  3. Where the check sits in front of your API

Book a session

Share a few details to start the conversation.

We use these details only to reply to you. See our privacy policy. The form is protected against spam.