Endpoint Discovery
Discover and search Dwellir's 150+ blockchain endpoints from the command line.
Use dwellir endpoints to browse and search all available blockchain networks on Dwellir.
List all endpoints
dwellir endpoints listThis returns every supported chain and network with connection details.
Search by name
Find endpoints matching a keyword:
dwellir endpoints search ethereumdwellir endpoints search polkadotThe search matches against chain names and network identifiers.
Get a specific chain
Retrieve details for a single chain:
dwellir endpoints get baseIf no match is found, the CLI returns a helpful error:
dwellir endpoints get nonexistent --json{
"ok": false,
"error": {
"code": "not_found",
"message": "No endpoints found for 'nonexistent'.",
"help": "Run 'dwellir endpoints list' to see all available chains."
}
}Filtering
Narrow results using filter flags. These work with list, search, and get:
| Flag | Example values | Description |
|---|---|---|
--ecosystem | evm, substrate, cosmos, move, hyperliquid, other | Filter by blockchain ecosystem |
--network | mainnet, testnet, or a specific network name | Filter by network name (case-insensitive substring match) |
--node-type | full, archive | Filter by node type (case-insensitive match) |
--protocol | https, wss | Filter by connection protocol |
Examples
List all EVM chains:
dwellir endpoints list --ecosystem evmShow only mainnet endpoints for Ethereum:
dwellir endpoints search ethereum --network mainnetList archive nodes in the Substrate ecosystem:
dwellir endpoints list --ecosystem substrate --node-type archiveCombine multiple filters:
dwellir endpoints list --ecosystem evm --network mainnet --node-type archiveJSON output
Use --json to get structured data for scripting:
dwellir endpoints search ethereum --protocol https --json{
"ok": true,
"data": [
{
"id": 41,
"name": "Ethereum",
"ecosystem": "evm",
"networks": [
{
"id": 43,
"name": "Mainnet",
"nodes": [
{
"id": 404,
"https": "https://api-ethereum-mainnet.n.dwellir.com/<key>",
"wss": "wss://api-ethereum-mainnet.n.dwellir.com/<key>",
"node_type": { "name": "Archive" }
}
]
}
]
}
],
"meta": {
"command": "endpoints.search",
"timestamp": "2026-02-26T12:00:00Z"
}
}The response is organized as chains containing networks, each with one or more nodes. Each node includes https and wss URLs with a <key> placeholder.
Use an endpoint URL with your key
Endpoint output never contains an API key. Replace the <key> placeholder at runtime with the key from your environment:
# Write the key to .env as DWELLIR_API_KEY
dwellir keys env my-key
# Load it and build the URL
set -a; . ./.env; set +a
URL="https://api-ethereum-mainnet.n.dwellir.com/<key>"
curl -s "${URL/<key>/$DWELLIR_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'To write the key and full endpoint URLs to .env in one step, run dwellir project setup --chain ethereum --network mainnet --key-name my-key. It writes DWELLIR_API_KEY, DWELLIR_RPC_URL, and DWELLIR_WSS_URL.
Next steps
- Create an API key to use with discovered endpoints
- Monitor usage across your endpoints
- See the full Supported Chains list for network-specific documentation
- Run
dwellir endpoints --helpfor the full list of flags