# Giving agent a wallet

Wallets are the first thing, any agent will need to interact with things on-chain. There are a couple type of wallet to choose from, depending on use-case :&#x20;

1. Embedded Wallet - this would be better than an EOA, if your agent needs to perform action across chains, so with help of embedded wallet, you can essentially deposit funds from any supported chain and the agent can then swap to the desired chain it wants.&#x20;

You can use [Crossmint](https://docs.google.com/document/d/1ssBTbaOgu2dZPxfACieBHXPx8JzwdyuqbqAawDmVXks/edit?tab=t.0#heading=h.t7s6a6fxtm78) Custodial Wallet which supports Solana and 20+ evm chains.

2. PKP Wallets - these are [multisig wallets](https://github.com/LIT-Protocol/policy-AI-agent), which enable you to create non-custodial wallets for your agent, and are suitable for applications revolving around fund management. Lit Protocol provides an easy way to create/manage them.
3. EOA Wallets - these are just normal wallets, for which you’ll need to generate the private keys and keep them securely stored in your environment, this is not recommended as it’s least secure.
4. Multichain Wallets - these are non-custodial wallets for agents to interact on Solana, Ethereum, and Bitcoin (with more chains coming). [EmblemAI](https://emblemvault.ai/) enables a percentage of every transaction to be routed to agent platforms or creators, creating a built-in revenue model for human developers.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.sendai.fun/components-to-build-an-agent/giving-agent-a-wallet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
