Runtime as featured inForbesRead the article

Applied AI for payment operations

Runtime Lab

We build the harness payment teams run mission-critical work on, and study what makes agents reliable enough to touch money: evals, routing, failover, and memory, tested on real payment operations.

What we work on

Frontier models are general. Payment operations are not. Our work is the layer between them that makes an agent safe to put on a live queue.

eval · merchant-re-reviewv7
#4821root cause found✓ pass
#4822evidence cited✓ pass
#4823stopped for approval✓ pass
#4824missing evidence✗ blocked
#4825reply matches policy✓ pass
#4826reserve within limits✓ pass
#4827sibling MIDs checked✓ pass
#4828sources linked✓ pass
Evals

Graded on real cases

Every skill is tested against resolved cases from your own queue. Did the agent find the root cause, cite the evidence, and stop at the approval point? A new model or prompt ships only if it passes.

router · evals decidelive
Routine enrichmentOpen 8B model
62% of runs$0.02 / run
Hard investigationsFrontier model
11% of runs$0.40 / run
−86%cost on routine work
Routing

The smallest model that passes

Each task is routed to the model and harness that still pass its evals. Routine enrichment moves to small open models, and hard investigations stay on frontier models.

failover drilllive
aws us-east-1
gcp us-west1
model primary
model fallback
09:41:02aws us-east-1 degraded
09:41:03failover → gcp us-west1
09:41:05run #8812 resumed
09:41:063 runs moved · 0 dropped
Reliability

Agents that stay up

We test recovery paths for sandbox and provider failures the way payment teams test disaster recovery, because a missed bank deadline costs real money.

memory · one paymentlive
Support
Payment ops
Finance
Compliance
MID 4410 · memory
✓Account changed Sep 18
✓Release approved
✓Sibling MIDs clean
Memory

Compounding organizational memory

Governed infrastructure that turns every investigation into memory the next case can use, with permissions, provenance, and an audit trail on everything an agent learns.

Visuals are illustrative.

Payments is a domain, not a prompt

Processor error codes, bank file formats, network reason codes, and sponsor bank quirks repeat across the industry. Our agents start out knowing them, so your team teaches them your business, not the basics. Your data, cases, and memory stay yours.

NACHA R01 · insufficient fundsNOC C01 · incorrect account numberVisa 10.4 · card-absent fraudMastercard 4837 · no cardholder authorizationISO 20022 pacs.008camt.053 bank statementBAI2 prior-day fileNACHA R10 · unauthorized debitFedwire IMAD/OMADRTP and FedNow returnsX9.37 image cash letterVisa 13.1 · merchandise not received

Engineers who have built payment infrastructure

The team behind the lab built payments, risk, and reconciliation systems at fintechs and Fortune 500s, and works with customers as forward-deployed AI engineers.

Gus Trigos

Gus Trigos

Co-founder and CEO

AI engineer and second-time YC founder. Former quant in BlackRock’s AI Quantitative Investment Group. Built Mentum (YC S21, acquired) for Latin America’s largest asset and wealth managers: $20B+ in AUM data, 120k transactions a month.

Carlos Volante

Carlos Volante

Co-founder and CTO

Scaled financial infrastructure at Modern Treasury, Finix, and Hulu’s payments team (Disney): billions in volume, near-perfect uptime, and billing for tens of millions of users.

Modern Treasury
Finix
Marqeta
Adyen
BlackRock
Meta
Hulu
Disney
Yahoo
Y Combinator
Berkeley
University of Michigan
Backed by Y Combinator and fintech leaders San FranciscoRuntime on Y Combinator LinkedIn

Bring us your hardest queue

We’ll build the first agent with your team and measure it against the cases you already resolved.