> ## Documentation Index > Fetch the complete documentation index at: https://docs.cosmos.network/llms.txt > Use this file to discover all available pages before exploring further. # Service Providers > 'Service Providers' are defined as entities that provide services for end-users that involve some form of interaction with the Cosmos Hub. More specifically, this document is focused on interactions with tokens. 'Service Providers' are defined as entities that provide services for end-users that involve some form of interaction with the Cosmos Hub. More specifically, this document is focused on interactions with tokens. Service Providers are expected to act as trusted points of contact to the blockchain for their end-users. This Service Providers section does not apply to wallet builders that want to provide Light Client functionalities. This document describes: * [Connection Options](#connection-options) * [Running a Full Node](#running-a-full-node) * [What is a Full Node?](#what-is-a-full-node) * [Installation and Configuration](#installation-and-configuration) * [Command-Line Interface](#command-line-interface) * [Available Commands](#available-commands) * [Remote Access to gaiad](#remote-access-to-gaiad) * [Create a Key Pair](#create-a-key-pair) * [Check your Account](#check-your-account) * [Check your Balance](#check-your-balance) * [Send Coins Using the CLI](#send-coins-using-the-cli) * [REST API](#rest-api) * [Listen for Incoming Transactions](#listen-for-incoming-transactions) ## Connection Options There are four main technologies to consider to connect to the Cosmos Hub: * Full Nodes: Interact with the blockchain. * REST Server: Serves for HTTP calls. * REST API: Use available endpoints for the REST Server. * GRPC: Connect to the Cosmos Hub using gRPC. ## Running a Full Node ### What is a Full Node? A Full Node is a network node that syncs up with the state of the blockchain. It provides blockchain data to others by using RESTful APIs, a replica of the database by exposing data with interfaces. A Full Node keeps in syncs with the rest of the blockchain nodes and stores the state on disk. If the full node does not have the queried block on disk the full node can go find the blockchain where the queried data lives. ### Installation and Configuration This section describes the steps to run and interact with a full node for the Cosmos Hub. First, you need to [install the software](/hub/v25/getting-started/installation). Consider running your own [Cosmos Hub Full Node](/hub/v25/hub-tutorials/join-mainnet). ## Command-Line Interface The command-line interface (CLI) is the most powerful tool to access the Cosmos Hub and use gaia. To use the CLI, you must install the latest version of `gaia` on your machine. Compare your version with the [latest release version](https://github.com/cosmos/gaia/releases) ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad version --long ``` ### Available Commands All available CLI commands are shown when you run the `gaiad` command: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad ``` ```bash expandable theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} Stargate Cosmos Hub App Usage: gaiad [command] Available Commands: add-genesis-account Add a genesis account to genesis.json collect-gentxs Collect genesis txs and output a genesis.json file debug Tool for helping with debugging your application export Export state to JSON gentx Generate a genesis tx carrying a self delegation help Help about any command init Initialize private validator, p2p, genesis, and application configuration files keys Manage your application's keys migrate Migrate genesis to a specified target version query Querying subcommands start Run the full node status Query remote node for status tendermint Tendermint subcommands testnet Initialize files for a gaia testnet tx Transactions subcommands unsafe-reset-all Resets the blockchain database, removes address book files, and resets data/priv_validator_state.json to the genesis state validate-genesis validates the genesis file at the default location or at the location passed as an arg version Print the application binary version information Flags: -h, --help help for gaiad --home string directory for config and data (default "/Users/tobias/.gaia") --log_format string The logging format (json|plain) (default "plain") --log_level string The logging level (trace|debug|info|warn|error|fatal|panic) (default "info") --trace print out full stack trace on errors Use "gaiad [command] --help" for more information about a command. ``` For each displayed command, you can use the `--help` flag to get further information. ```bash expandable theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad query --help Usage: gaiad query [flags] gaiad query [command] Aliases: query, q Available Commands: account Query for account by address auth Querying commands for the auth module bank Querying commands for the bank module block Get verified data for a the block at given height distribution Querying commands for the distribution module evidence Query for evidence by hash or for all (paginated) submitted evidence gov Querying commands for the governance module ibc Querying commands for the IBC module ibc-transfer IBC fungible token transfer query subcommands mint Querying commands for the minting module params Querying commands for the params module slashing Querying commands for the slashing module staking Querying commands for the staking module tendermint-validator-set Get the full tendermint validator set at given height tx Query for a transaction by hash in a committed block txs Query for paginated transactions that match a set of events upgrade Querying commands for the upgrade module Flags: --chain-id string The network chain ID -h, --help help for query Global Flags: --home string directory for config and data (default "/Users/tobias/.gaia") --log_format string The logging format (json|plain) (default "plain") --log_level string The logging level (trace|debug|info|warn|error|fatal|panic) (default "info") --trace print out full stack trace on errors Use "gaiad query [command] --help" for more information about a command. ``` ### Remote Access to gaiad When choosing to remote access a Full Node and gaiad, you need a Full Node running and gaia installed on your local machine. `gaiad` is the tool that enables you to interact with the node that runs on the Cosmos Hub network, whether you run it yourself or not. To set up `gaiad` on a local machine and connect to an existing full node, use the following command: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad config ``` First, set up the address of the full node you want to connect to: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad config node : ``` You will be asked to create a password (at least 8 characters) for this key-pair. This will return the information listed below: * `NAME`: Name of your key * `TYPE`: Type of your key, always `local`. * `ADDRESS`: Your address. Used to receive funds. * `PUBKEY`: Your public key. Useful for validators. * `MNEMONIC`: 24-word phrase. **Save this mnemonic somewhere safe**. This phrase is required to recover your private key in case you forget the password. The mnemonic is displayed at the end of the output. You can see all available keys by typing: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad keys list ``` Use the `--recover` flag to add a key that imports a mnemonic to your keyring. ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad keys add --recover ``` #### Check your Account You can view your account by using the `query account` command. ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad query account ``` It will display your account type, account number, public key and current account sequence. ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} '@type': /cosmos.auth.v1beta1.BaseAccount account_number: "xxxx" address: cosmosxxxx pub_key: '@type': /cosmos.crypto.secp256k1.PubKey key: xxx sequence: "x" ``` ### Check your Balance Query the account balance with the command: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad query bank balances ``` The response contains keys `balances` and `pagination`. Each `balances` entry contains an `amount` held, connected to a `denom` identifier. The typical \$ATOM token is identified by the denom `uatom`. Where 1 `uatom` is 0.000001 ATOM. ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} balances: - amount: "12345678" denom: uatom pagination: next_key: null total: "0" ``` When you query an account that has not received any token yet, the `balances` entry is shown as an empty array. ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} balances: [] pagination: next_key: null total: "0" ``` #### Send Coins Using the CLI To send coins using the CLI: ```bash theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}} gaiad tx bank send [from_key_or_address] [to_address] [amount] [flags] ``` Parameters: * ``: Key name or address of sending account. * ``: Address of the recipient. * ``: This parameter accepts the format ``, such as `1000000uatom`. Flags: * `--chain-id`: This flag allows you to specify the id of the chain. There are different ids for different testnet chains and mainnet chains. * `--gas-prices`: This flag allows you to specify the gas prices you pay for the transaction. The format is used as `0.0025uatom` ## REST API The REST API documents list all the available endpoints that you can use to interact with your full node. Learn [how to enable the REST API](/hub/v25/hub-tutorials/join-mainnet#rest-api) on your full node. ### Listen for Incoming Transactions The recommended way to listen for incoming transactions is to periodically query the blockchain by using the following HTTP endpoint: `/cosmos/bank/v1beta1/balances/{address}`