Crypto Wallet

Active

An AI agent for Crypto Wallet. It works in a scene with a live connection to Crypto Wallet. It asks before it writes, and every run is traced.

Link any wallet by its public address. Scenes read balances and transactions on Base and Arbitrum, and agents can draft payments that you approve in your own wallet, with a passkey or a browser wallet. Daslab stores the address and nothing else: no keys, no funds, no fees on payments.

Finance API Key 2 asset types

What you can connect

Add these to your scene and AI gets access.

Wallet Wallets

A linked wallet address — read-only; Daslab stores only the public address, never keys

Guide Guides

Crypto Wallet setup guides, troubleshooting, and reference — pin one to read it in-scene, or ask the agent.

TitleSummary

Connect Crypto Wallet over MCP

Daslab is itself an MCP server.

Connect Crypto Wallet in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Crypto Wallet tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold Crypto Wallet and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Render a live balance view inside a scene
Watch for incoming USDC payments to a project wallet
Let an agent draft a payment and hand you the signing link
Verify a drafted payment landed, from the chain itself

Knowledge base

Linking a wallet linking-a-wallet
Why the connection is just a public address, which wallets work (all of them), what the read tools see, and what Daslab structurally cannot do with it.
Payment links: the agent drafts, you sign payment-links
The draft-and-sign flow end to end: what a payment link contains, passkey vs browser-wallet signing, why links are server-signed and expiring, and how completion is verified on-chain.

Ships with the integration — agents read these with docs_read, before the account is connected. Knowledge bases →