Signo
Any AI can create a persistent agent for your wallet. It never holds your keys.
An AI agent that touches money has one unsolved problem: how does it act without acting wrongly? Signo's answer is to separate understanding from authority. The AI, any AI, works out what you want and drafts it. Signo owns the agent: it watches the chain around the clock, prepares the transaction when the moment comes, and delivers it to you. You decide, and you sign. When you want it to act on its own, you sign a bounded on-chain permission once, and the contract enforces the limits, not a prompt.
Three ways in, three audiences:
| You are | Start at | Needs |
|---|---|---|
| A person with a wallet | For Users — the app: chat, agents, Telegram | A wallet |
| Someone with an AI assistant (Claude Code, Cursor, a bot) | For AI assistants — point it at Signo's MCP server | Nothing. No key, no sign-up |
| A protocol or app building on Signo | For Partners — the API, SDK and hosted MCP with a partner key | A partner key |
Three levels of trust
Every agent sits at one of three levels, and nothing moves it up without you:
- Notify. It watches a condition and tells you on Telegram when it fires.
- Prepare. When it fires, it builds a fresh, unsigned transaction and hands it to you to review and sign.
- Execute. It acts on its own, inside a Shield permission you signed on-chain: one action, one asset, a cap per firing, a lifetime budget, an expiry. The contract cancels anything outside those lines. Live on X Layer and Arbitrum.
An AI assistant can draft an agent at any of the three. A draft is not an agent until you claim it with your wallet, and a permission is not authority until you sign it.
What is underneath
The same deterministic boundary powers every path: tested transaction encoding, asset resolution that fails closed rather than guesses, simulation before signing, and quotes refreshed at sign time. The AI proposes intent; it cannot widen what gets signed.
Where to go next
- Get Started — the 30-second tour of the app.
- For AI assistants — one command to add Signo to Claude Code or Cursor, three tools, no key.
- For Partners — API, SDK, hosted MCP, webhooks, in-page agents.
- Protocol Coverage — every chain and protocol Signo routes through.
- Security — the execution-correctness boundary in detail.
These docs are early. If something is missing or wrong, use Send feedback on an Action Plan or email support@signo.fi.