Skip to main content

​
Overview

We use Laso Finance agentic tooling to build Laso Finance. Setting up and running payroll is a clear case where agentic tooling made a faster and safer process than humans. Twice a month, a persistent Hermes Cloud Agent:
  1. Calculates payroll.
  2. Verifies amounts with founder.
  3. Pays on confirmation.
  4. Generates, stores and sends payment records.
  5. Updates our internal ledger.
It’s a great example of keeping Laso Finance at the core of your agentic financial workflows, while extending functionality with external services.

​
Tools Used

x402 transfer bridging bank transfers AgentMail Firebase Firestore MCP Mana Hermes Cloud Agent Harvest

​
Payroll Generation

The first step is calculating and confirming accuracy of total pay. Laso Finance employees and contractors track time in Harvest, a time-tracking software.
1

Retrieve hours

Connects to Harvest API, collect timesheet entries for all employees/contractors during the pay period.
2

Calculate pay

Pulls each recipients rate using Firebase MCP, calculating total pay with hours and timesheet records.
3

Draft the record

Generates a pending payment record email and PDF, noting total time, pay, and individual entries for the pay period.
4

Send for confirmation

Sends to founder via Telegram with draft email and PDF attachment for confirmation.
5

Founder confirmation or denial

In Telegram, founder can confirm, starting the next process. If payments need editing, they are prompted within the Telegram chat and results are re-reviewed.

The agent lists what it verified, states plainly that no funds moved yet, and waits for the founder to reply YES.

​
Sending payment

Once the founder confirms the payment records, the agent starts sending payments. It varies payment rail by recipient preference. All payments are funded by the agent’s Laso Solana wallet.

Read the pay route

The agent uses Firebase Firestore MCP to read pay route data and preferences for each recipient.

Pay by the matching rail

Based on that data, it either sends USDC on Solana, bridges from Solana USDC to an external Mana Base USDC address, or sends a bank transfer all through Laso services.
Each recipient is paid on the rail they picked, from one wallet. Adding a new rail means adding a pay route to the recipient’s record, not changing the payroll run itself.

​
Post-payment

Once that payment is complete, the agent completes the loop by notifying recipients, and updating internal records.

Extract payment confirmation

For onchain payments, constructs a block explorer link. For bank transfers, extracts the payment ID.

Attach proof of payment

Updates its draft payment record email and PDF attachment with that confirmation.

Notify the recipient

Sends email to the recipient via AgentMail confirming the change.

Update the ledger

Debits the Laso Finance internal ledger with the corresponding amount, transaction hash / ID, and link to the record of hours worked.

The closing report: transfer ID and Solscan link for the payment, the recipients and PDF of the email it sent, and confirmation that it read the sent message back to check both.

By connecting our agent to Laso Finance and a few external services, a complicated external process is brought in-house. Legible, controllable, and safe.

​
Build this yourself

Managed agent wallet

Provision the wallet the payroll run pays from.

Bank accounts

Set up the banking profile behind bank payouts.

Send a bank payment

Register a payee once, then pay them by ACH.

MCP server

Connect your own agent to these endpoints.