Skip to content

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

Open
gfletcher-cll wants to merge 28 commits into
mainfrom
data-products-markdown
Open

Agent-friendly structured data access for Data Feeds and Data Streams#3780
gfletcher-cll wants to merge 28 commits into
mainfrom
data-products-markdown

Conversation

@gfletcher-cll
Copy link
Copy Markdown
Collaborator

@gfletcher-cll gfletcher-cll commented May 13, 2026

Summary

Adds agent-friendly, structured data access for Data Feeds and Data Streams, and improves dataset discoverability for correct programmatic usage.

Replaces large, component-rendered tables with deterministic .txt dataset endpoints, enabling scoped retrieval (per-network for feeds, per-category for streams) while aligning with how agents select and query data.


Key changes

  • Structured dataset endpoints (docs-native):

    • Data Feeds:

      • /data-feeds/feed-addresses/{type}.txt (per-type index)
      • /data-feeds/feed-addresses/{type}/{network}.txt (per-network datasets)
    • Data Streams:

      • /data-streams/stream-ids/{type}.txt (category-scoped stream IDs)
      • /data-streams/networks.txt (verifier proxy metadata)
  • Docs rendering (.md.ts):

    • Replaced full data tables with:

      • dataset links
      • small, deterministic examples
    • Prevents large payloads and HTML scraping

  • Output normalization:

    • Streams: added schema-aware outputs with direct schema doc links
  • llms.txt updates (feeds + streams):

    • Introduced explicit category/type → dataset mapping

    • Encodes canonical retrieval pattern:

      discover → select type → scope → fetch
      
    • Ensures agents choose the correct dataset (e.g. smartdata vs default, rwa vs crypto) instead of defaulting to broad datasets


How to validate

Data Feeds

  • Type-specific datasets:

    /data-feeds/feed-addresses/default.txt
    /data-feeds/feed-addresses/smartdata.txt
    /data-feeds/feed-addresses/rates.txt
    
  • Per-network dataset:

    /data-feeds/feed-addresses/default/ethereum-mainnet.txt
    
  • Docs page (should show link + small example only):

    /data-feeds/price-feeds/addresses.md
    

Data Streams

  • Category datasets:

    /data-streams/stream-ids/crypto.txt
    /data-streams/stream-ids/rwa.txt
    
  • Network metadata:

    /data-streams/networks.txt
    
  • Docs page (should show link + example only):

    /data-streams/crypto-streams
    

Result

  • Deterministic, low-token data access for agents

  • Clear separation:

    • docs → guidance
    • datasets → data
    • llms.txt → decision + behavior
  • Agents reliably select the correct dataset based on feed type or stream category

@gfletcher-cll gfletcher-cll requested a review from a team as a code owner May 13, 2026 20:31
@vercel
Copy link
Copy Markdown

vercel Bot commented May 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview May 14, 2026 4:36am

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

👋 gfletcher-cll, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant