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

public/llms.txt

@@ -12,13 +12,79 @@ 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
+
+- Step 1 — retrieve networks:
+
+  /data-feeds/networks.json
+
+- Step 2 — retrieve feed addresses:
+
+  /data-feeds/search.json?type={type}&network={queryString}
+
+- Example:
+
+  https://docs.chain.link/data-feeds/search.json?type=default&network=ethereum-mainnet
+
+Filter results by feed name.
+
+Do not construct alternative dataset paths.
+
+### 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 +93,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 +119,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 +133,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 +162,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 +189,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 +209,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 +226,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/config/sidebar.ts

@@ -972,6 +972,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
     {
       section: "Resources",
       contents: [
+        {
+          title: "Feed Address Datasets",
+          url: "data-feeds/datasets",
+        },
         {
           title: "Smart Contract Overview",
           url: "getting-started/conceptual-overview?parent=dataFeeds",
@@ -1326,6 +1330,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
     {
       section: "Resources",
       contents: [
+        {
+          title: "Data Streams Datasets",
+          url: "data-streams/datasets",
+        },
         {
           title: "Smart Contract Overview",
           url: "getting-started/conceptual-overview?parent=dataStreams",

src/content/data-feeds/datasets.mdx

@@ -0,0 +1,68 @@
+---
+section: dataFeeds
+title: "Feed Address Datasets"
+---
+
+This page provides structured datasets of Chainlink feed contract addresses across supported networks.
+
+These datasets contain the same information shown in the interactive address tables, but in a format designed for direct retrieval and processing.
+
+When you need to retrieve feed addresses systematically, use the datasets below instead of parsing documentation pages.
+
+## Networks
+
+This dataset lists all supported networks and their query identifiers.
+
+/data-feeds/networks.json
+
+## Price Feeds
+
+Retrieve all price feeds for a given network:
+
+/data-feeds/search.json?type=default&network=ethereum-mainnet
+
+Example:
+
+/data-feeds/search.json?type=default&network=ink-mainnet
+
+## Rates Feeds
+
+/data-feeds/search.json?type=rates&network=ethereum-mainnet
+
+## SmartData Feeds
+
+/data-feeds/search.json?type=smartdata&network=ethereum-mainnet
+
+## Tokenized Equity Feeds
+
+/data-feeds/search.json?type=tokenizedEquity&network=ethereum-mainnet
+
+## U.S. Government Macroeconomic Data Feeds
+
+/data-feeds/search.json?type=usGovernmentMacroeconomicData&network=ethereum-mainnet
+
+## How to Retrieve Feed Addresses
+
+To retrieve feed addresses reliably:
+
+1. Retrieve the list of supported networks:
+
+/data-feeds/networks.json
+
+2. Select the appropriate `queryString` value for your target network.
+
+3. Retrieve feed data for that network:
+
+/data-feeds/search.json?type=default&network={queryString}
+
+4. Filter the returned dataset by feed name to locate the desired address.
+
+This is the recommended retrieval path.
+
+## Notes
+
+- These datasets are read-only
+- Responses match the data shown in the documentation tables
+- Each dataset contains the complete set of feeds for the specified network
+- Filtering is typically performed client-side
+- Do not attempt to extract feed addresses from rendered documentation tables