The operating system for agentic disputes
Personal AI agents now buy things for people. Umpyr checks those orders before payment, settles what goes wrong after, agent to agent, and keeps one signed record both sides trust.
THE PROBLEM
Agents can buy for you. They can't complain for you.
When an agent books the wrong showtime or accepts a flight change its owner never wanted, three parties each hold one piece of the truth: the agent holds what the customer approved, the merchant holds what was sold, the payment provider holds the charge. Nobody holds all three, so the customer goes to the bank and the merchant pays.
Forms are built for people
Every complaint channel expects a human at a web form. Agents can fill it in, but not stand behind it.
No one can say whose fault it was
The customer's mistake, the agent's mistake and the merchant's mistake look identical to a help desk and to a bank.
THE PRODUCT
Check before payment. Resolve after.
Both are built on one record: exactly what the customer approved inside their agent, compared with what was booked and what was paid, committed at the moment of purchase.
Umpyr Check · before payment
The merchant asks Umpyr in real time: is this the real agent and the real person, and does the order match what was approved? A mismatch becomes a quick question back to the agent instead of a lost sale.
Umpyr Resolve · after payment
A case agent gathers the evidence, decides fault by published rules, negotiates a fix with the customer's agent within the merchant's limits, and closes with a signed record once the customer confirms.
THE OPERATING SYSTEM
Four layers no one party can own.
Protocol
One message format both sides speak: complaint, evidence, offer, counter, confirmation.
Authority
The customer confirms the exact terms inside their agent. Signed, binding, no login.
Routing
Every complaint reaches the right merchant, and merchants not yet on Umpyr still get a clean case.
Record
One signed audit record, identical for the merchant and the agent.
The agent stays a messenger, never a party. The merchant keeps its own money and its own rules.
HOW A CASE RUNS
From complaint to fix in minutes.
Order, payment and approval record found; the sender is verified before anything is shown.
Fault by deterministic rules first, an AI judge second, merchant staff third.
An offer within the merchant's limits; the customer confirms inside their agent.
Refund or exchange runs on the merchant's own systems. Money never touches Umpyr.
WORK WITH US
Looking for design partners.
We're working with a small group of merchants (airlines, travel and retail) and agent platforms to settle the first agent disputes end to end. No code to start: forward your agent-order complaints and we take it from there.