> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get set up with Eco

> Choose an Eco service, configure API credentials, and prepare your wallet and runtime for a CLI transfer or Routes API integration.

Choose the service for your integration, then prepare its credentials and runtime. You can explore the CLI or build directly against the API; you do not need to complete both paths.

## Prerequisites

* For the Routes CLI: Node.js 20 or later, as required by `eco-routes-cli` 1.0.5.
* For the TypeScript API guide: the Node.js version and dependencies listed in [Integrate the Routes API](/get-started/integrate-routes-api).
* For an onchain transfer: a wallet with the source token and enough native currency for any transactions it submits.
* Access to a source-chain RPC endpoint. The CLI includes defaults. For an EVM chain, set `EVM_RPC_URL_<chainId>` to use your own endpoint, such as `EVM_RPC_URL_8453` for Base.

## Choose a service

| Service | Base URL | Purpose |
| - | - | - |
| Eco API v1 | `https://api.eco.com` | Chain and token discovery, signed quotes, funding submissions, intent status, and Circle Gateway deposits. See the [API reference](/api-reference/introduction). |
| Open quoting service | `https://quotes.eco.com` | A separate, keyless service with the legacy v3 quote format. See [Open quoting service](/api-reference/public-quote). |
| Solana deposit-address service | `https://deposit-addresses.eco.com` | Address generation and lookup for [Base-to-Solana USDC deposits](/programmable-addresses/solana-deposit-addresses). |

These services have different request and response formats. Use the reference for the service you call.

## API keys and attribution

For Eco API v1, send your key in the `x-api-key` header. The `/v1/circle-gateway/*` endpoints allow requests without a key. [Request an API key](mailto:contact@eco.com?subject=Eco%20API%20key) for the other v1 endpoints and confirm that it has access to the operations you need. Keep the key in your backend environment.

Use `dappId` to identify your application in v1 quote requests. The Open quoting service uses the distinct field `dAppID`. See the [quote request example](/api-reference/v1/quotes) for the complete v1 body.

See [Errors and retries](/api-reference/errors) for authentication failures and [API conventions](/api-reference/introduction) for amount formats, identifiers, and rate limits.

## Prepare the CLI

```bash theme={null}
npm install -g eco-routes-cli@1.0.5
```

Set `EVM_PRIVATE_KEY` in your environment or in a local `.env` file for an EVM source. For Solana, use `SVM_PRIVATE_KEY`. Exclude `.env` from version control. The [first-transfer guide](/get-started/first-transfer) shows how to preview a transfer before broadcasting.

CLI 1.0.5 uses the legacy quoting service by default. Its command-line flow is separate from the v1 HTTP integration described in the API guide.

## Environments

Use [supported chains and tokens](/resources/supported-chains-tokens) and the discovery endpoints to check mainnet coverage. For Circle Gateway testing, follow the dedicated [testnet guide](/programmable-addresses/circle-gateway-testnet), which uses a different host and path scheme. Contact Eco for access to other test environments before using production credentials or funds.

## Troubleshooting

* **API key rejected:** check the header name, service hostname, and key's v1 access. Do not put the key in a query string.
* **Insufficient balance:** check the source-token balance and the gas needed for approvals and funding.
* **RPC request fails:** confirm the endpoint serves the selected chain and retry read requests before submitting transactions.

## Next steps

* [Make your first transfer](/get-started/first-transfer) from the CLI.
* [Integrate the Routes API](/get-started/integrate-routes-api) from your backend.