orqrailRun a demo ↗

POLICY-FIRST AGENT PAYMENTS

Autonomy.
Within
bounds.

Your agent has a job to do.
Give it a route to pay.
Keep the right to say no.

Set the boundaries ↓
01 — AUTHORIZATIONLOCAL PROTOTYPE / 2026
ROUTE / A–001 SIMULATION
⌘
REQUEST ORIGINresearch-agent
01
Authorization terminal●
PAYMENT REQUESTREQ–001
$USD
PER REQUEST $100REMAINING $500
READY · Your policy decides.
↳
DECISION RECEIPTWaiting for a request
AGENT → POLICY → DECISIONNo real money moves.

02 / THE ROUTE

A request isn't
a blank cheque.

Agents should carry authority that is specific, limited and explainable. Orqrail puts a policy checkpoint between an intention and a payment.

01

Define the job.

Set a budget and name the places the agent is allowed to spend.

02

Check the request.

Evaluate the merchant, the amount and the remaining allowance.

03

Keep the receipt.

Record the decision and its reason. A decline is part of the story, too.

03 / YOUR BOUNDARIES

Give it room.
Keep a hand
on the switch.

Change the policy here, then send a request through the terminal. Every control below changes the local demo.

Back to the terminal ↗
FLEET CONTROLAgent is active
POLICY / RESEARCH–01LOCAL STATE
$100
$10$250
Session allowance$500.00
Available in demo$500.00

Where it can spend

2 allowed

    Only listed merchants can pass the policy.

    04 / DECISION TRAIL

    Every yes.
    Every no. Visible.

    REQUESTMERCHANTAMOUNTDECISIONREASON
    No requests yet. Run an authorization in the terminal to create your first decision receipt.
    Local session only · Refresh starts a new demo.

    05 / BEFORE YOU BEGIN

    Clear by
    design.

    No mysterious permissions.
    No promises hidden in the small print.

    Is this a live payment service?+

    No. This is a working frontend prototype. Budgets, merchants, transactions and decisions are local demonstration data. It does not issue cards or move money.

    What can I actually try?+

    Add or remove merchants, switch to categories, change a per-request cap, freeze the agent, and run an authorization. The demo evaluates your current rules and writes a decision to the local audit log.

    What happens when a request is denied?+

    The budget stays unchanged. The audit log records the attempted amount and a reason: frozen agent, merchant restriction, request cap or exhausted budget.

    What is still planned?+

    Card issuing, funding, real payment processing, durable audit storage, identity and MCP integration require future backend services. None are connected in this prototype.

    Is there a token or a registered account?+

    No verified token utility or live token is part of this concept. Brand handles and domains are candidates until checked and registered separately.

    LET THE AGENT DO THE WORK.

    Keep the authority. ↗
    orqrail↳