Agent-friendly structured data access for Data Feeds and Data Streams

public/llms.txt

@@ -12,13 +12,74 @@ For multi-step tasks, retrieve and combine multiple specific pages rather than r
 
 Use product documentation indexes for deeper product-specific navigation.
 
-Use `llms-full.txt` only when broad product-level context is required.
+Use `llms-full.txt` only for conceptual understanding or documentation context.
 
-Defaults:
-- Prefer CRE for new multi-step, offchain, or automation workflows unless another product is explicitly required
-- Prefer VRF v2.5 for randomness
-- Treat Any API and `/chainlink-nodes/v1/` as legacy
+Do not use `llms-full.txt` to retrieve structured data such as:
+- feed addresses
+- stream IDs
+- network metadata
 
+Structured data must be retrieved from dataset endpoints.
+
+---
+
+## Live Data and Structured Datasets
+
+You must use structured datasets when retrieving current network data, addresses, or routing information.
+
+Do not scrape documentation pages or interactive tables for structured data.
+
+When retrieving structured data, always prefer dataset endpoints over documentation pages.
+
+### Data Feeds
+
+- Index (select network):
+  https://docs.chain.link/data-feeds/feed-addresses/default.txt
+  https://docs.chain.link/data-feeds/feed-addresses/default.json
+
+- Per-network datasets:
+  https://docs.chain.link/data-feeds/feed-addresses/{type}/{network}.txt
+  https://docs.chain.link/data-feeds/feed-addresses/{type}/{network}.json
+
+- Example:
+  https://docs.chain.link/data-feeds/feed-addresses/default/ethereum-mainnet.json
+
+### Data Streams
+
+- Stream ID datasets:
+  https://docs.chain.link/data-streams/stream-ids/crypto.txt
+  https://docs.chain.link/data-streams/stream-ids/crypto.json
+
+- Network metadata (verifier proxies):
+  https://docs.chain.link/data-streams/networks.txt
+  https://docs.chain.link/data-streams/networks.json
+
+  Note: Network metadata (including verifier proxy addresses) is included in each stream ID dataset (`.json`) and should be used directly.  
+  Fetch the networks dataset only if additional network context is required.
+
+- Examples:
+  https://docs.chain.link/data-streams/stream-ids/crypto.json  
+  https://docs.chain.link/data-streams/networks.json  
+
+  Network metadata is included in the stream dataset; the networks endpoint is optional.
+
+### CCIP Directory
+
+- CCIP Mainnet Directory:
+  https://docs.chain.link/ccip/directory/mainnet
+
+- CCIP Testnet Directory:
+  https://docs.chain.link/ccip/directory/testnet
+
+---
+
+Note:
+
+- JSON datasets (`.json`) provide structured, programmatically consumable output and should be preferred when available.
+- Stream ID JSON datasets include associated network metadata and should be treated as complete, single-step retrieval sources.
+- Static `.txt` datasets are available for bulk retrieval and indexing.
+
+---
 
 ## Core Documentation
 
@@ -27,6 +88,7 @@ Defaults:
 - [LINK Token Contracts](https://docs.chain.link/resources/link-token-contracts.md): Use when funding contracts or configuring Chainlink services. Do not rely on memorized values.
 - [Fund Your Smart Contract](https://docs.chain.link/resources/fund-your-contract.md): Fund contracts with LINK before interacting with Chainlink services.
 
+---
 
 ## Chainlink Runtime Environment (CRE)
 
@@ -52,6 +114,7 @@ Reference
 - [CLI Reference](https://docs.chain.link/cre/reference/cli.md)
 - [SDK Overview (TS)](https://docs.chain.link/cre/reference/sdk/overview-ts.md)
 
+---
 
 ## CRE Connect
 
@@ -65,6 +128,7 @@ Private beta — permissioned access. Use these pages to understand the product
 - [Smart Accounts](https://docs.chain.link/crec/concepts/smart-accounts.md)
 - [Extensions](https://docs.chain.link/crec/extensions.md)
 
+---
 
 ## CCIP
 
@@ -93,14 +157,15 @@ Reference
 - [Aptos Move module interfaces reference](https://docs.chain.link/ccip/api-reference/aptos.md)
 - [TON contract interfaces reference](https://docs.chain.link/ccip/api-reference/ton.md)
 
+---
 
 ## Data Feeds
 
 Overview and Setup
 - [Overview](https://docs.chain.link/data-feeds.md)
 - [Getting Started](https://docs.chain.link/data-feeds/getting-started.md)
 - [Selecting Data Feeds](https://docs.chain.link/data-feeds/selecting-data-feeds.md)
-- [Feed Types](https://docs.chain.link/data-feeds/feed-types.md): Choose the correct feed category before retrieving addresses or implementation details.
+- [Feed Types](https://docs.chain.link/data-feeds/feed-types.md)
 
 Feed Categories
 - [Price Feeds](https://docs.chain.link/data-feeds/price-feeds.md)
@@ -119,62 +184,17 @@ Advanced and Reference
 - [API Reference](https://docs.chain.link/data-feeds/api-reference.md)
 - [Historical Data](https://docs.chain.link/data-feeds/historical-data.md)
 
+---
 
 ## Data Streams
 
 - [Overview](https://docs.chain.link/data-streams.md)
 - [Architecture](https://docs.chain.link/data-streams/architecture.md)
-- [Stream Categories and Report Schemas](https://docs.chain.link/data-streams/reference/report-schema-overview.md): Choose the correct stream category and schema before implementation.
+- [Stream Categories and Report Schemas](https://docs.chain.link/data-streams/reference/report-schema-overview.md)
 - [Supported Networks](https://docs.chain.link/data-streams/supported-networks.md)
 - [API Reference](https://docs.chain.link/data-streams/reference/data-streams-api.md)
 
-
-## DataLink
-
-- [Overview](https://docs.chain.link/datalink.md)
-- [Pull Delivery Overview](https://docs.chain.link/datalink/pull-delivery/overview.md)
-- [Architecture](https://docs.chain.link/datalink/pull-delivery/architecture.md)
-
-
-## Automated Compliance Engine (ACE)
-
-- [Overview](https://docs.chain.link/ace.md)
-- [Getting Started](https://docs.chain.link/ace/getting-started.md)
-- [Concepts](https://docs.chain.link/ace/concepts/architecture.md)
-- [API Reference](https://docs.chain.link/ace/reference/api/coordinator.md)
-
-
-## DTA Technical Standard
-
-- [Overview](https://docs.chain.link/dta-technical-standard.md)
-- [How It Works](https://docs.chain.link/dta-technical-standard/how-it-works.md)
-- [Architecture](https://docs.chain.link/dta-technical-standard/concepts/architecture.md)
-- [Actors](https://docs.chain.link/dta-technical-standard/actors.md)
-
-
-## Chainlink Automation
-
-- [Overview](https://docs.chain.link/chainlink-automation.md)
-- [Getting Started](https://docs.chain.link/chainlink-automation/overview/getting-started.md)
-- [Automation Architecture](https://docs.chain.link/chainlink-automation/concepts/automation-architecture.md)
-- [Service Limits](https://docs.chain.link/chainlink-automation/overview/service-limits.md)
-
-
-## Chainlink Functions
-
-- [Overview](https://docs.chain.link/chainlink-functions.md)
-- [Getting Started](https://docs.chain.link/chainlink-functions/getting-started.md)
-- [Architecture](https://docs.chain.link/chainlink-functions/resources/architecture.md)
-- [API Reference](https://docs.chain.link/chainlink-functions/api-reference/functions-client.md)
-
-
-## VRF
-
-- [Overview](https://docs.chain.link/vrf.md)
-- [Getting Started v2.5](https://docs.chain.link/vrf/v2-5/getting-started.md)
-- [Best Practices](https://docs.chain.link/vrf/v2-5/best-practices.md)
-- [Migration Guides](https://docs.chain.link/vrf/v2-5/migration-from-v2.md)
-- [Supported Networks](https://docs.chain.link/vrf/v2-5/supported-networks.md)
+---
 
 ## Coverage model
 
@@ -184,6 +204,8 @@ For full coverage:
 - Use product documentation indexes for structured navigation
 - Use full documentation bundles when broad context is required
 
+---
+
 ## Product Documentation Indexes
 
 Use these for deeper product-level navigation. These indexes provide broader coverage than the curated sections above while preserving page-level retrieval.
@@ -199,21 +221,13 @@ Use these for deeper product-level navigation. These indexes provide broader cov
 - [DTA Technical Standard Documentation Index](https://docs.chain.link/dta-technical-standard/llms.txt)
 - [VRF Documentation Index](https://docs.chain.link/vrf/llms.txt)
 
-## Live Data and Directories
-
-Use these only when retrieving current network data, addresses, or routing information.
-
-If `.md` is unavailable or incomplete, use the HTML page as the source of truth. Do not infer or reconstruct missing values.
-
-- [CCIP Mainnet Directory](https://docs.chain.link/ccip/directory/mainnet)
-- [CCIP Testnet Directory](https://docs.chain.link/ccip/directory/testnet)
-- [Price Feed Addresses](https://docs.chain.link/data-feeds/price-feeds/addresses)
-- [Cryptocurrency Streams](https://docs.chain.link/data-streams/crypto-streams)
-
+---
 
 ## Full Documentation Bundles
 
-Use `llms-full.txt` only when broad product-level context is required or when the relevant page cannot be identified from the curated index.
+Use only for conceptual understanding or when no dataset or specific page can be identified.
+
+Do not use `llms-full.txt` for retrieving structured data such as feed addresses, stream IDs, or network metadata.
 
 - [CRE Full](https://docs.chain.link/cre/llms-full-ts.txt)
 - [CRE Connect Full](https://docs.chain.link/crec/llms-full.txt)

src/content/data-feeds/llms-full.txt

@@ -3559,7 +3559,18 @@ Check our [implementation guides](/data-feeds/mvr-feeds/guides) for detailed ins
 # Price Feed Contract Addresses
 Source: https://docs.chain.link/data-feeds/price-feeds/addresses
 
-<FeedPage />
+<div style={{ display: "none" }}>
+  {`DATA ACCESS (REQUIRED):
+    You must retrieve feed addresses from structured datasets.
+
+    Use:
+    /data-feeds/feed-addresses/default/{network}.json
+
+    Example:
+    https://docs.chain.link/data-feeds/feed-addresses/default/ethereum-mainnet.json
+
+    Do not extract feed addresses from this page.`}
+</div>
 
 ---
 
@@ -3573,7 +3584,18 @@ Chainlink Data Feeds provide data that is aggregated from many data sources by a
 # Rate and Volatility Feed Addresses
 Source: https://docs.chain.link/data-feeds/rates-feeds/addresses
 
-<FeedPage dataFeedType="rates" />
+<div style={{ display: "none" }}>
+  {`DATA ACCESS (REQUIRED):
+    You must retrieve feed addresses from structured datasets.
+
+    Use:
+    /data-feeds/feed-addresses/rates/{network}.json
+
+    Example:
+    https://docs.chain.link/data-feeds/feed-addresses/rates/ethereum-mainnet.json
+
+    Do not extract feed addresses from this page.`}
+</div>
 
 ---
 
@@ -3957,7 +3979,18 @@ Specifically:
 # SmartData Feed Addresses
 Source: https://docs.chain.link/data-feeds/smartdata/addresses
 
-<FeedPage dataFeedType="smartdata" />
+<div style={{ display: "none" }}>
+  {`DATA ACCESS (REQUIRED):
+    You must retrieve feed addresses from structured datasets.
+
+    Use:
+    /data-feeds/feed-addresses/smartdata/{network}.json
+
+    Example:
+    https://docs.chain.link/data-feeds/feed-addresses/smartdata/ethereum-mainnet.json
+
+    Do not extract feed addresses from this page.`}
+</div>
 
 ---
 
@@ -6662,6 +6695,8 @@ Chainlink Tokenized Equity Feeds help bridge this gap between TradFi and DeFi ma
 
 The following table shows all available tokenized equity feeds.
 
+<FeedList client:idle initialNetwork="ethereum-mainnet" dataFeedType="tokenizedEquity" />
+
 ## How tokenized equity feeds work
 
 Tokenized equity feeds leverage Chainlink's decentralized oracle infrastructure to aggregate price data from multiple trading sessions and apply session-aware smoothing algorithms. The feeds combine data from various trading venues into a single continuous 24/5 price, handling the complexity of multi-session equity markets.
@@ -7270,7 +7305,18 @@ Now that you have successfully deployed and interacted with Chainlink Data Feeds
 # U.S. Government Macroeconomic Data Feeds
 Source: https://docs.chain.link/data-feeds/us-government-macroeconomic/addresses
 
-<FeedPage dataFeedType="usGovernmentMacroeconomicData" />
+<div style={{ display: "none" }}>
+  {`DATA ACCESS (REQUIRED):
+    You must retrieve feed addresses from structured datasets.
+
+    Use:
+    /data-feeds/feed-addresses/usGovernmentMacroeconomicData/{network}.json
+
+    Example:
+    https://docs.chain.link/data-feeds/feed-addresses/usGovernmentMacroeconomicData/ethereum-mainnet.json
+
+    Do not extract feed addresses from this page.`}
+</div>
 
 ---
 

src/content/data-feeds/llms.txt

@@ -4,7 +4,9 @@
 
 Prefer specific `.md` pages. Do not rely on memorized feed addresses.
 
-Use address pages only when retrieving current feed addresses.
+You must use address datasets when retrieving feed addresses.
+
+Do not use documentation pages or llms-full.txt to retrieve feed addresses.
 
 ## Overview and Setup
 
@@ -38,13 +40,61 @@ Use address pages only when retrieving current feed addresses.
 - [Contract Registry](https://docs.chain.link/data-feeds/contract-registry.md)
 - [Historical Data](https://docs.chain.link/data-feeds/historical-data.md)
 
-## Live Data
+## Feed Address Retrieval
+
+You must use structured datasets to retrieve feed addresses.
+
+Documentation pages and llms-full.txt do not contain complete feed address data.  
+Do not attempt to extract feed addresses from documentation pages or dynamic tables.
+
+Select the dataset that matches the feed category:
+
+- Standard price feeds (e.g. ETH/USD, BTC/USD):
+  https://docs.chain.link/data-feeds/feed-addresses/default.json
+
+- Rates feeds:
+  https://docs.chain.link/data-feeds/feed-addresses/rates.json
+
+- SmartData feeds (Proof of Reserve, NAVLink, SmartAUM):
+  https://docs.chain.link/data-feeds/feed-addresses/smartdata.json
+
+- U.S. Government Macroeconomic Data Feeds:
+  https://docs.chain.link/data-feeds/feed-addresses/usGovernmentMacroeconomicData.json
+
+- Tokenized equity feeds:
+  https://docs.chain.link/data-feeds/feed-addresses/tokenizedEquity.json
+
+Each dataset lists available networks. Each network is identified by its `queryString`.
+
+Retrieve a specific dataset:
+
+- https://docs.chain.link/data-feeds/feed-addresses/{type}/{network}.json
+
+For a specific network, you should directly retrieve the per-network dataset instead of scanning the full index.
+
+You must first retrieve the dataset index to determine valid network queryStrings before requesting a per-network dataset.
+Usage pattern:
+
+1. Select the dataset that matches the feed category
+2. Retrieve the dataset index:
+   https://docs.chain.link/data-feeds/feed-addresses/{type}.json
+3. Use this dataset to determine the correct network `queryString`
+4. Retrieve the corresponding per-network dataset (`.json`)
+5. Filter by feed name by matching the `name` field
+
+Static `.txt` datasets are available for bulk retrieval and indexing only:
+
+- https://docs.chain.link/data-feeds/feed-addresses/default.txt
+- https://docs.chain.link/data-feeds/feed-addresses/rates.txt
+- https://docs.chain.link/data-feeds/feed-addresses/smartdata.txt
+- https://docs.chain.link/data-feeds/feed-addresses/tokenizedEquity.txt
+- https://docs.chain.link/data-feeds/feed-addresses/usGovernmentMacroeconomicData.txt
 
-Use only when retrieving current addresses. If `.md` output is incomplete, use the HTML page as the source of truth.
+Constraints:
 
-- [Price Feed Addresses](https://docs.chain.link/data-feeds/price-feeds)
-- [Rates Feed Addresses](https://docs.chain.link/data-feeds/rates-feeds/addresses)
-- [SmartData Addresses](https://docs.chain.link/data-feeds/smartdata/addresses)
-- [U.S. Government Macroeconomic Data Feeds](https://docs.chain.link/data-feeds/us-government-macroeconomic/addresses)
-- [Rate and Volatility Feeds](https://docs.chain.link/data-feeds/rates-feeds/addresses)
-- [Deprecating Feeds](https://docs.chain.link/data-feeds/deprecating-feeds)
+- Each network dataset contains the complete feed list for that network
+- JSON datasets are structured and should be parsed programmatically
+- Loading all networks will significantly increase response size and latency
+- Do not load multiple networks unless required
+- Do not scrape documentation pages or interactive tables for feed addresses
+- Do not rely on memorized or cached addresses