How it works
The five steps every request goes through, from Muse or the app.
Every request follows the same path, whether it comes from Muse through the MCP server or from the chat in the museli app.
- 1Plan
Your words become an intent, such as swap 10 USDC to ETH. museli reads your balances, resolves amounts like all or half, prices the move and lists every step.
- 2Check
The plan is checked against your guardrails on the server. The result is one of three decisions: allow, ask or block.
- 3Approve
Ask decisions wait for your approval. Block decisions stop here and never run.
- 4Sign
Right before signing, museli checks your guardrails again with fresh balances and prices, then builds fresh transactions. Approvals are added only when the current allowance is too low.
- 5Verify
Each transaction hash is checked on Base: it must come from your wallet, go to the expected contract and succeed. Only then is the action marked confirmed.
Action statuses
| Status | Meaning |
|---|---|
ready | Inside your guardrails and ready to run. |
awaiting_approval | Over a limit. Waiting for your yes. |
approved | You approved it. It runs next. |
blocked | Breaks a hard rule. It will not run. |
executing | Transactions are being signed and confirmed. |
confirmed | Verified on Base. |
failed | Something went wrong. Nothing more is signed. |
declined | You or your agent cancelled it. |