Agents propose changes to your routing and operations, prove them against your own history, and wait for a person. On your infrastructure, over your rails.
In that order, every time.
Agents read your settlement history and open a change with the evidence attached.
Replay it against your own payments. Each change alone, then in combination.
Shadow, canary, live. Live needs a second approver.
Production systems our team built and ran. None is a Switchboard deployment, and we will not pretend otherwise.
Figures as of August 2026. Client names available on request, under NDA.
Each one shows what it can read, and what it can never do without a person.
You say what to optimise in a sentence. The agent repeats it on every proposal.
Every finding carries its observation count. Too few, and it says so.
Backtest, then shadow, then canary. Then a person.
Promotion needs measured agreement with your team, not confidence.
The bottom two need your ledger. That is why this runs inside your walls.
Limits, cutoffs, jurisdiction and screening are rules with named reasons. A model never decides whether a payment is allowed, only which allowed rail to use.
Every rail considered, the rule that excluded each one, and one sentence a person can read. Hash-chained, so an altered record is caught at the exact entry.
Bedrock in your account, a local model on your hardware, or no model at all. One config line, same product.
Routing is the money. The other three are the hours. One engine, one audit trail.
A price list gives you the fee. Not the slippage, the latency tail, the repair rate, or the hours your team spends on the ones that go wrong.
Where the data goes, in writing, before you ask.
Runs in your cloud account. Inference goes to Bedrock in your region, over a VPC endpoint.
No payload leaves your account. Nothing retained for training.
For institutions that will not send a payment instruction to any cloud.
Nothing leaves the building. The provider is one config line.
The agentic layer over the same ledger and connectors. No integration work.
One deployment, one audit trail, connectors already in place.
Routing systems decide on published terms: the fee schedule, the quoted time, the stated success rate. Those are a partner's marketing, and they are optimistic in exactly the places that cost you money.
The difference between quoted and realised is visible in one place: your ledger. A product outside your walls cannot see it. One that can has to run inside them.
In the reference book, the rail with the best price list is the worst rail to use, by 31 basis points. An operator choosing on price picks it. So does the engine, for the first few payments, and then it stops.
Bring ninety days of history for two corridors. We will show you the gap in your own numbers.