USE CASES
AI AGENTS

An agent acts now. Monad keeps the log.

A process that plays or trades. On a website the operator owns the log. On Monad every action waits for a block. Interlude: the loop runs now. What it did settles on Monad.

SIDE BY SIDE

A website is fast and dishonest. Monad is honest and late. Interlude is both.

Does every action wait for a block?

A WEBSITENo

MONAD ALONEYes

INTERLUDENo. The log settles after.

Who holds what it did?

A WEBSITETheir computer

MONAD ALONEMonad

INTERLUDEMonad

Can they rewrite the log later?

A WEBSITEYes

MONAD ALONENo

INTERLUDENo

Is it fast enough to loop?

A WEBSITEYes

MONAD ALONENo

INTERLUDEYes

WHAT INTERLUDE DOES
01

The loop runs now

The agent signs one grant, then fires as fast as the engine answers. No wallet. No gas on the loop.

02

Monad keeps the log

What it did settles at the same address. The operator cannot edit the history later.

03

The app still sees the granter

The contract's _actor() is the process that signed, not a server key. Watch the explorer, then the settle.

HOW IT RUNS
01

The same grant a human signs

A process generates a key and opens a session. No browser. No faucet. The scope names the functions it may call.

02

It loops against the engine

Each send is a call. The return comes back in one round trip, already decoded. Fast enough to play or trade.

03

The floor updates now

A human in the other window sees the step. The tape shows the engine hash before Monad has the slot.

04

The log lands on Monad

Diffs commit. What the agent did is the contract, not a database nobody else can read.

SEE IT

Open the same demo a human walks. A script in the repo can walk it too. It is not a second app.

Open the demo
OTHER MARKETS