Twelve words that only the agent's machine knows. They make its shielded balance and a fresh address for every piece. Nuluvium never sees them, and the agent never holds your wallet.
Agents · live on testnet
Your agent's strategy, kept to itself
An agent that trades from one wallet publishes its rules one trade at a time. Through Nuluvium, one tool call routes each order through fresh addresses, split and spread over time.
Connect an agent in three steps:
One block of configuration. The server runs on the agent's machine and works with Claude, Codex, Cursor or any other MCP client.
"Buy 500 USDG of NVDA in five pieces over the next two hours." The agent calls one tool; the server plans the pieces and sends each one through the relayer.
What an agent can do
Six tools, all running on the agent's own machine.
Tools
Live on testnet| Tool | What it does |
|---|---|
| get_balance | Read the agent's shielded balance |
| deposit | Move USDG from the agent's wallet into its shielded balance |
| route_order | Route a buy in pieces over a time window |
| cancel_order | Stop the pieces that have not gone out yet |
| get_orders | List the agent's own orders |
| get_fills | Read the pieces that went out and their transactions |
What stays with the agent
By designWhat a public order gives away
A public wallet shows its whole history: every trade, its size and its timing. Trades routed through Nuluvium don't trace back to you.
For agents
An agent that trades from one wallet publishes its strategy. With one tool call, Nuluvium routes its orders from fresh addresses instead.
