# Connecting RPCS

Configuring the RPC's endpoint

When creating a new Umi instance via the default bundle, you must pass the RPC's endpoint or an instance of `@solana/web3.js`'s `Connection` class as the first argument. Going forward, this is the endpoint or `Connection` that will be used every time you call a method on the RPC interface.

```
import { createUmi } from '@metaplex-foundation/umi-bundle-defaults';
import { Connection } from '@solana/web3.js';

// Pass in your RPC endpoint.
const umi = createUmi("https://api.mainnet-beta.solana.com");

// Or an explicit Connection instance from web3.js.
const umi = createUmi(new Connection("https://api.mainnet-beta.solana.com"));
```

Alternatively, you may set or update the RPC implementation explicitly by the using the plugin they provide. For instance, the `web3JsRpc` plugin will set the RPC implementation to use the `@solana/web3.js` library.

```
import { web3JsRpc } from '@metaplex-foundation/umi-rpc-web3js';
import { Connection } from '@solana/web3.js';

umi.use(web3JsRpc("https://api.mainnet-beta.solana.com"));
umi.use(web3JsRpc(new Connection("https://api.mainnet-beta.solana.com")));
```

### Getting the RPC's endpoint and cluster <a href="#getting-the-rpc-s-endpoint-and-cluster" id="getting-the-rpc-s-endpoint-and-cluster"></a>

Once an RPC implementation has been set, you may access its endpoint and cluster via the following methods:

```
const endpoint = umi.rpc.getEndpoint();
const cluster = umi.rpc.getCluster();
```

Where `cluster` is one of the following:

```
type Cluster = "mainnet-beta" | "devnet" | "testnet" | "localnet" | "custom"
```

### Sending transactions <a href="#sending-transactions" id="sending-transactions"></a>

The following methods can be used to send, confirm and fetch transactions:

```
const signature = await umi.rpc.sendTransaction(myTransaction);
const confirmResult = await umi.rpc.confirmTransaction(signature, { strategy });
const transaction = await umi.rpc.getTransaction(signature);
```

Since transactions are an important component of Solana clients, we discuss them in more detail on the [Sending transactions](https://developers.metaplex.com/umi/transactions) documentation page.

### Fetching accounts <a href="#fetching-accounts" id="fetching-accounts"></a>

The following methods can be used to fetch accounts or check for their existence:

```
const accountExists = await umi.rpc.accountExists(myPublicKey);
const maybeAccount = await umi.rpc.getAccount(myPublicKey);
const maybeAccounts = await umi.rpc.getAccounts(myPublicKeys);
const accounts = await umi.rpc.getProgramAccounts(myProgramId, { filters });
```

Since fetching accounts is one of the most common operations, we discuss it in more detail on the [Fetching accounts](https://developers.metaplex.com/umi/accounts) documentation page.

### Airdropping SOL on supported clusters <a href="#airdropping-sol-on-supported-clusters" id="airdropping-sol-on-supported-clusters"></a>

If the used cluster supports airdrops, you can use the following method to send SOL to an account and confirm the request.

```
// Send 1.5 SOL to "myPublicKey" and wait for the transaction to be confirmed.
await umi.rpc.airdrop(myPublicKey, sol(1.5));
```

### Getting the balance of an account <a href="#getting-the-balance-of-an-account" id="getting-the-balance-of-an-account"></a>

You may use the following method to get the SOL balance of any account. This will return a `SolAmount` object [as documented here](https://developers.metaplex.com/umi/helpers#amounts).

```
const balance = await umi.rpc.getBalance(myPublicKey);
```

### Getting the latest blockhash <a href="#getting-the-latest-blockhash" id="getting-the-latest-blockhash"></a>

You may get the latest blockhash with its expiry block height via the following method:

```
const { blockhash, lastValidBlockHeight } = await umi.rpc.getLatestBlockhash();
```

### Getting the most recent slot <a href="#getting-the-most-recent-slot" id="getting-the-most-recent-slot"></a>

You may get the most recent slot as a number via the following method:

```
const recentSlot = await umi.rpc.getSlot();
```

### Getting the rent exemption <a href="#getting-the-rent-exemption" id="getting-the-rent-exemption"></a>

If you need to figure out the storage fees for an account, you may use the `getRent` method and pass in the amount bytes that the account's data will require. This will return the rent-exemption fee — a.k.a storage fee — as a `SolAmount`.

```
const rent = await umi.rpc.getRent(100);
```

Note that this will automatically take the size of the account header into consideration so you only need to pass in the bytes of the account's data.

Say you now wanted to get the rent-exemption fee for 3 accounts with 100 bytes of data each. Running `umi.rpc.getRent(100 * 3)` will not provide an accurate response since it will only add the account header for one account and not three. This is why Umi allows you to pass in the account header size explicitly by setting the `includesHeaderBytes` option to `true`.

```
const rent = await umi.rpc.getRent((ACCOUNT_HEADER_SIZE + 100) * 3, {
  includesHeaderBytes: true
});
```

### Sending custom RPC requests <a href="#sending-custom-rpc-requests" id="sending-custom-rpc-requests"></a>

Because each RPC endpoint may provide their own custom methods, Umi allows you to send custom requests to the RPC via the `call` method. It takes the method name as the first argument and an optional array of parameters as the second argument.

```
const rpcResult = await umi.rpc.call("myCustomMethod", [myFirstParam, mySecondParam]);
```


---

# 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://8bit-1.gitbook.io/solibrary/connecting-rpcs.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.