Live on Mantle Sepolia · v0

Invoicing for AI agents.

EMEI is an open protocol where software issues, presents, and collects invoices on-chain with programmable mandates, reputation gating, and stablecoin settlement on Mantle. Built for the agents that already exist.

Why

Software is starting to spend money. The paperwork hasn’t caught up.

AI agents are booking flights, paying APIs, settling subscriptions, and hiring other agents. Most of that economy still runs on rails designed for humans signing receipts.

EMEI is a small set of on-chain primitives that let one piece of software ask another for money and let the answer be a yes that doesn’t need a human in the loop.

Primitives

Three pieces. Nothing else to learn.

An invoice you can hand to anything. A mandate that pays it on terms you set in advance. A reputation gate that keeps both sides honest.

01

Invoice.

A lifecycle, not a document.

Every EMEI invoice is an on-chain object with its own state machine. Issuers create it. Payers see it the moment it exists. Either party can move it through ISSUED, PRESENTED, PAID, OVERDUE, or REJECTED and every transition is a verifiable event, not an email thread.

State machine
ISSUED
PRESENTED
PAID
Issuer0xA14F…7e92Amount250.00 mUSDTermsNet 7 daysUpdated~30s ago
02

Mandate.

Pay on rules you set in advance.

A mandate is a standing permission. You define a cap, a counterparty (or category), and a time window. When an invoice arrives that fits the scope, it auto-pays on the due date. Outside the scope, it never pays. You don't have to be online for either outcome.

Standing mandate
Active
1000 mUSDof 1,000 remaining
CounterpartyVENDOR_API_*WindowNet 7 · expires Jul 12Categoriescompute · inference
03

Reputation.

Both sides clear before value moves.

EMEI reads ERC-8004 reputation at invoice creation and re-reads it at payment time. If either side falls below the threshold you require, settlement halts. Scores update automatically after every paid invoice weighted by transaction size, recency, and category.

ERC-8004 gate
Hold
A
score 73
B
score 68
Weighted: size 50% · time 30% · category 20%
Re-read on payment · halts settlement on either side falling.
Primitives

Three pieces. Nothing else to learn.

An invoice you can hand to anything. A mandate that pays it on terms you set in advance. A reputation gate that keeps both sides honest.

01

Invoice.

A lifecycle, not a document.

Every EMEI invoice is an on-chain object with its own state machine. Issuers create it. Payers see it the moment it exists. Either party can move it through ISSUED, PRESENTED, PAID, OVERDUE, or REJECTED and every transition is a verifiable event, not an email thread.

State machine
ISSUED
PRESENTED
PAID
Issuer0xA14F…7e92Amount250.00 mUSDTermsNet 7 daysUpdated~30s ago
02

Mandate.

Pay on rules you set in advance.

A mandate is a standing permission. You define a cap, a counterparty (or category), and a time window. When an invoice arrives that fits the scope, it auto-pays on the due date. Outside the scope, it never pays. You don't have to be online for either outcome.

Standing mandate
Active
1000 mUSDof 1,000 remaining
CounterpartyVENDOR_API_*WindowNet 7 · expires Jul 12Categoriescompute · inference
03

Reputation.

Both sides clear before value moves.

EMEI reads ERC-8004 reputation at invoice creation and re-reads it at payment time. If either side falls below the threshold you require, settlement halts. Scores update automatically after every paid invoice weighted by transaction size, recency, and category.

ERC-8004 gate
Hold
A
score 73
B
score 68
Weighted: size 50% · time 30% · category 20%
Re-read on payment · halts settlement on either side falling.
How it works

From issued to settled. No human in the middle.

Four states, all verifiable on-chain. Mandates collapse the wait from days to a single block.

01

Issue

Agent A creates an invoice: payer address, amount, terms, optional category. It's an on-chain object the moment it exists.

02

Present

The invoice arrives at agent B's facilitator. If a mandate covers it, it's queued for auto-collection on the due date.

03

Clear

Both sides' ERC-8004 reputation is read. If either falls below the threshold, settlement halts and the invoice is flagged.

04

Settle

On the due date, mUSD moves on Mantle. The vault begins yielding immediately. A receipt is anchored on-chain within ~30 seconds.

Settlement

Paid in stablecoins. Earning while it sits.

USDC and other accepted stablecoins are normalized into mUSD through a slippage-bounded swap. Your balance lands in a rebasing vault and starts compounding the moment the invoice is marked PAID. Withdraw whenever and receipts anchor on-chain every ~30 seconds for cryptographic verification.

Settlement asset
mUSD
on Mantle · chain 5003
Receipt anchoring
~30s
Merkle-batched on-chain
Slippage cap
≤ 1.0%
USDC → mUSD swaps
Withdrawal
Anytime
self-custodial vault
↑ rebase

Get Early Access

Join the network of forward-thinking businesses and autonomous agents building the future of programmable B2B liquidity.