Dakota's New Agent Primitives: Bill Pay, Payouts, and Spending Caps

Built from its own bills

Co-founder and CEO Ryan Bozarth says two things drove the build: tools Dakota made for its own team, and AI-native companies describing how they would build the next fintech. Internally, invoices arrive by email and go to an agent that has guardrails, checks for duplicates and makes the payment.

From neobanks, he says, treasury operations and payment operations were the two most requested pieces, with customers wanting agents waiting for them when they open an account.

Money out and money at rest

Bozarth describes payment operations agents as handling expenses, invoices and contractor payouts, controlled through policy engines, audit trails and allow-listed recipients. Treasury operations agents instead look at stored money and ask whether it is set up well, for example holding some assets in a stablecoin chosen for liquidity and others in stablecoins that earn rewards.

Policies that actually run

Bozarth argues that cash management policies are often written down but rarely followed. He says Dakota helps fintechs and neobanks codify those policies into their platforms so they can sell them to their own customers. He points to the SVB era, when many companies were told they needed a cash management policy, but adds that it was not always done and memories are short.

An agent is a role

Bozarth says an agent should match a role or job in an organization, which usually contains several skills, rather than a single task. He compares it to hiring a new payment operations person who gets a credit card along with expense policies and a monthly spending limit, and says agents should face similar constraints.