Feed Address API

The Feed Address API provides programmatic access to Chainlink feed contract addresses across all supported networks. It returns the same data shown in the interactive address tables, in plain text or JSON format suitable for tooling, agents, and automated workflows.

For Data Streams feed IDs, see the Stream ID API.

Endpoints

Get feed addresses

GET https://docs.chain.link/api/feeds/addresses

Returns feed addresses for the requested type. Optionally scoped to a single network.

Query parameters

Example requests

# All standard price feeds across all chains (markdown)
curl "https://docs.chain.link/api/feeds/addresses?type=default"

# Mainnet-only standard price feeds — JSON (recommended for most integrations)
curl "https://docs.chain.link/api/feeds/addresses?type=default&networkType=mainnet&format=json"

# Price feeds on Ethereum Mainnet only — JSON
curl "https://docs.chain.link/api/feeds/addresses?type=default&network=ethereum-mainnet&format=json"

# Price feeds on Arbitrum — JSON
curl "https://docs.chain.link/api/feeds/addresses?type=default&network=arbitrum-mainnet-arbitrum-1&format=json"

# SmartData feeds — mainnet only
curl "https://docs.chain.link/api/feeds/addresses?type=smartdata&networkType=mainnet"

Markdown response (truncated)

# Chainlink Feed Addresses: Standard Price Feeds
...

## Ethereum — Ethereum Mainnet
- Network type: mainnet
- Query string: `ethereum-mainnet`

| Feed Name | Proxy Address | Deviation | Heartbeat |
|-----------|--------------|-----------|-----------|
| BTC / USD | `0xF4030086522a5bEEa4988F8cA5B36dbC97BeE88` | 0.5% | 1h |
| ETH / USD | `0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419` | 0.5% | 1h |
...

JSON response (truncated)

{
  "type": "default",
  "label": "Standard Price Feeds",
  "network": "ethereum-mainnet",
  "networkType": null,
  "count": 150,
  "feeds": [
    {
      "name": "BTC / USD",
      "proxyAddress": "0xF4030086522a5bEEa4988F8cA5B36dbC97BeE88",
      "deviation": "0.5%",
      "heartbeat": "1h",
      "network": "ethereum-mainnet",
      "networkName": "Ethereum Mainnet",
      "networkType": "mainnet",
      "chain": "Ethereum"
    },
    ...
  ]
}

Smart Value Recapture (SVR) variants include an additional "svr": "shared" or "svr": "aave" field to distinguish them from the standard feed on the same network.

Get networks

GET https://docs.chain.link/api/feeds/networks

Returns all supported network queryString values, separated by mainnet and testnet. Use these values with the network parameter above.

Query parameters

Example requests

# All networks that carry standard price feeds
curl "https://docs.chain.link/api/feeds/networks?type=default"

# JSON — useful for programmatic iteration
curl "https://docs.chain.link/api/feeds/networks?type=default&format=json"

# All networks that carry SmartData feeds
curl "https://docs.chain.link/api/feeds/networks?type=smartdata&format=json"

JSON response (truncated)

{
  "type": "default",
  "mainnet": [
    { "queryString": "ethereum-mainnet", "networkName": "Ethereum Mainnet", "chain": "Ethereum" },
    { "queryString": "arbitrum-mainnet", "networkName": "Arbitrum Mainnet", "chain": "Arbitrum" }
  ],
  "testnet": [{ "queryString": "ethereum-sepolia", "networkName": "Ethereum Sepolia", "chain": "Ethereum" }]
}

Feed types

Each type value corresponds to a category of Chainlink feed. See feed types for a full overview.

Static snapshots

Pre-rendered snapshots of each feed type are available as static files, baked at deploy time. Useful for offline tooling, RAG indexing, or any context where a live API call is not practical.

https://docs.chain.link/data-feeds/feed-addresses/{type}.txt

Examples

curl "https://docs.chain.link/data-feeds/feed-addresses/default.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/smartdata.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/rates.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/tokenizedEquity.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/usGovernmentMacroeconomicData.txt"

Snapshots reflect data as of the last site deployment. For always-current data, use the live endpoint.

Notes

• Responses match exactly what is shown in the interactive address tables.
• The default type across all networks is large (~2,500+ feeds). Use &network={queryString} to scope requests where possible.
• Data is sourced from the same backend used by the interactive address tables in the docs, cached daily.
• To use a feed address in your contracts, see Using Data Feeds.
• For guidance on selecting the right feed, see Selecting Quality Data Feeds.