Your assets.
Your address.
Receive ETH and tokens at your smart-account address. Send ETH or any ERC-20 with a fresh approval.
A smart wallet for your assets.
Your dapps. Your agents. Your say.
Connect, trade, send, or sign. Review each request on your phone and approve it with a biometric scan. No seed phrase to store.
Review it. Then make the call.
The familiar things you want to do.
A different way to authorize them.
Receive ETH and tokens at your smart-account address. Send ETH or any ERC-20 with a fresh approval.
Pair compatible dapps through WalletConnect. Review transactions and signatures on your phone—even with the wallet tab closed.
Use MCP to request payments and contract calls. Your agent gets a way to ask. Your biometric signature authorizes the action.
Two connections. The same approval flow.
Choose how you want to get started.
Sign in to Wallet with your Yanez credential and a scan first. Add the hosted MCP connection to your client, using your own credential.
wallet_statusRead your accountwallet_request_transferRequest ETH or tokenswallet_request_actionRequest contract callswallet_wait_authorizationWait for your decisionwallet_activityRead recent activity{
"mcpServers": {
"exogenic-wallet": {
"type": "http",
"url": "https://exogenic.io/wallet/mcp",
"headers": {
"Authorization": "Bearer yak_..."
}
}
}
}Replace yak_... with your own Yanez credential.
Every action still needs your approval.
Pair a compatible dapp in Wallet. Requests arrive on your phone, with transactions decoded and simulated before you approve.
Open Wallet ↗Use your Yanez credential and approve the sign-in scan.
Choose WalletConnect in the dapp and pair its connection from Wallet.
You can close the wallet tab. The connection still forwards requests for approval.
An agent requested 0.0001 ETH through MCP. A biometric approval authorized the transfer. The receipt is public.
View the agent transfer ↗Requested by an agent. Approved by a person.
0x57635972…e1e4eClear expectations are part of good security.
Wallet is a smart account with its own address and assets. Gate adds approval rules to an allowance from a wallet you already have. Both support MCP and require a fresh approval for every action.
Account control depends on your registered approval devices. Adding a device requires a high-tier scan from an existing one. If you lose every registered device, you lose control of the account; there is no seed phrase recovery.
It can submit requests, but each action needs your approval. Scan-free budgets and standing session permissions are not enabled.
Sign in to see your account address. It can receive assets before deployment; your first approved operation deploys the account. Keep some ETH there to cover network gas.
Keep ETH in the account for network gas. A relayer submits the approved operation and is reimbursed from the account. Gas is not sponsored.
Review the decoded request and simulated balance changes carefully. The account verifies a signature bound to the operation; the readable preview comes from the decoder. A simulation is an estimate, not a guaranteed result. Token approvals and permits can give another contract permission to spend later. Review their spender and limits carefully.
Each approval depends on the YID app and Yanez service. An outage can delay actions. The service cannot create your biometric approval on your behalf.
The service stores your Yanez request credential encrypted and maintains your dapp connections. That credential can request an approval; it is separate from your biometric signing key. Signed-in browser sessions are listed in Wallet and can be revoked individually.
Use compatible dapps through WalletConnect. Dapps that require signatures must support smart-account signatures (ERC-1271). Compatibility can vary.