From 4dfc0e0966179415fe7a36e96e86b4ab8b81a146 Mon Sep 17 00:00:00 2001 From: Sahil Aujla Date: Tue, 7 Jul 2026 03:56:51 +0000 Subject: [PATCH 1/9] docs: seed the Feature Support by Chain page for the interactive matrix Rewrites the stub page (same slug) with the FeatureSupportMatrix widget embed and the feature-support:auto marker block that UpdateFeatureSupportFromDaikonWorkflow maintains (AX-545). Prose outside the markers stays human-owned, exactly like the CU costs page. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_0152TGB1HprVNykx38Er8dwW --- .prettierignore | 5 +++++ .../resources/feature-support-by-chain.mdx | 13 +++++++++++-- 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/.prettierignore b/.prettierignore index 32acf1b2e..304c757ee 100644 --- a/.prettierignore +++ b/.prettierignore @@ -4,3 +4,8 @@ **/*.md content/api-specs/ pnpm-lock.yaml + +# Generated by UpdateFeatureSupportFromDaikonWorkflow; the generator owns its +# one-entity-per-line format (prettier reflowing it would make every daily bot +# write a diff) +content/feature-support.json diff --git a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx index a761592c3..d30df9d5e 100644 --- a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx +++ b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx @@ -5,8 +5,17 @@ subtitle: Alchemy's current feature availability for each of its supported chain slug: reference/feature-support-by-chain --- +Search any JSON-RPC method, REST endpoint, or Alchemy product to see exactly which chains and networks support it — or pick a chain and network to browse everything available on it. Support data is regenerated daily from Alchemy's internal chain configuration, so what you see here is what the platform serves. + + + +## Product support by chain + +Every Alchemy product and the chains it supports, at a glance. A product counts as supported on a chain when at least one of its networks supports at least one of the product's methods — use the interactive matrix above for method-level and network-level (mainnet/testnet) detail. + +{/* feature-support:auto */} +{/* feature-support:auto end */} + Check the [Chains](https://dashboard.alchemy.com/chains) page for details about product and chain support! - - ![](https://alchemyapi-res.cloudinary.com/image/upload/v1764179964/docs/api-reference/alchemy-transact/transaction-simulation/523fb8a9a9d899921ee1046d0ff1b389967a9976d1c6112ebbbe071ddd1ef374-image.png) From 41175112f2a49e6849fd2932b6a8d6038fa15462 Mon Sep 17 00:00:00 2001 From: Sahil Aujla Date: Tue, 7 Jul 2026 08:03:33 -0400 Subject: [PATCH 2/9] docs: keep the widget embed out of the seed page until its data ships Codex review: the seed commit rendered with no data file in the tree. The embed and its intro paragraph move to the stacked data PR so this commit is safe to deploy on its own. Co-Authored-By: Claude Fable 5 --- .../pricing-resources/resources/feature-support-by-chain.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx index d30df9d5e..0b24d76b0 100644 --- a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx +++ b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx @@ -5,10 +5,6 @@ subtitle: Alchemy's current feature availability for each of its supported chain slug: reference/feature-support-by-chain --- -Search any JSON-RPC method, REST endpoint, or Alchemy product to see exactly which chains and networks support it — or pick a chain and network to browse everything available on it. Support data is regenerated daily from Alchemy's internal chain configuration, so what you see here is what the platform serves. - - - ## Product support by chain Every Alchemy product and the chains it supports, at a glance. A product counts as supported on a chain when at least one of its networks supports at least one of the product's methods — use the interactive matrix above for method-level and network-level (mainnet/testnet) detail. From 74b6a2719e940a9acc3cf90100adcfc132925329 Mon Sep 17 00:00:00 2001 From: Sahil Aujla Date: Tue, 7 Jul 2026 12:17:45 +0000 Subject: [PATCH 3/9] docs: make the seed page prose self-contained without the widget --- .../pricing-resources/resources/feature-support-by-chain.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx index 0b24d76b0..d337dd140 100644 --- a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx +++ b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx @@ -7,7 +7,7 @@ slug: reference/feature-support-by-chain ## Product support by chain -Every Alchemy product and the chains it supports, at a glance. A product counts as supported on a chain when at least one of its networks supports at least one of the product's methods — use the interactive matrix above for method-level and network-level (mainnet/testnet) detail. +Every Alchemy product and the chains it supports, at a glance. A product counts as supported on a chain when at least one of its networks supports at least one of the product's methods. {/* feature-support:auto */} {/* feature-support:auto end */} From 4e5cc73cab4171927bcce368333c5f8e66a7cb4b Mon Sep 17 00:00:00 2001 From: Sahil Aujla Date: Tue, 7 Jul 2026 11:49:43 -0400 Subject: [PATCH 4/9] docs: hide the seeded summary block from readers Matches the data branch: the block exists for search engines, LLMs, and markdown consumers, so the seed ships it inside the same hidden div and the section never renders visibly between the two merges. Co-Authored-By: Claude Fable 5 --- .../resources/feature-support-by-chain.mdx | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx index d337dd140..5c7abe7fb 100644 --- a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx +++ b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx @@ -5,13 +5,24 @@ subtitle: Alchemy's current feature availability for each of its supported chain slug: reference/feature-support-by-chain --- -## Product support by chain +{/* + The summary block below is intentionally wrapped in a hidden div: it + exists for search engines, LLMs, and markdown consumers, while the + interactive widget (added with the generated data) is the human-facing + view. The h4 keeps it out of the page table of contents. +*/} + + + Check the [Chains](https://dashboard.alchemy.com/chains) page for details about product and chain support! From 8bdbf00f4bbe3884d769bb0748771e4aa5519f65 Mon Sep 17 00:00:00 2001 From: Sahil Aujla Date: Tue, 7 Jul 2026 11:51:25 -0400 Subject: [PATCH 5/9] docs: drop the dashboard chains callout from the seed page Matches the data branch, which removes the closing pointer to the dashboard Chains page. Co-Authored-By: Claude Fable 5 --- .../pricing-resources/resources/feature-support-by-chain.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx index 5c7abe7fb..dab44f5d0 100644 --- a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx +++ b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx @@ -22,7 +22,3 @@ Every Alchemy product and the chains it supports, at a glance. A product counts {/* feature-support:auto end */} - - - Check the [Chains](https://dashboard.alchemy.com/chains) page for details about product and chain support! - From da083c37dca40259d19075be093570790ecc35d4 Mon Sep 17 00:00:00 2001 From: Sahil Aujla Date: Thu, 9 Jul 2026 18:47:15 -0400 Subject: [PATCH 6/9] docs: describe the server-rendered feature-support data flow in the page comment The docs-site widget now server-renders the matrix data with on-demand revalidation (OMGWINNING/docs-site#345); the seed page's comment adopts the same freshness text as the generated-data branch so the stacked diffs stay conflict-free. Co-Authored-By: Claude Fable 5 Co-authored-by: Cursor --- .../resources/feature-support-by-chain.mdx | 25 ++++++++++++++++--- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx index dab44f5d0..5284a4931 100644 --- a/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx +++ b/content/api-reference/pricing-resources/resources/feature-support-by-chain.mdx @@ -6,10 +6,27 @@ slug: reference/feature-support-by-chain --- {/* - The summary block below is intentionally wrapped in a hidden div: it - exists for search engines, LLMs, and markdown consumers, while the - interactive widget (added with the generated data) is the human-facing - view. The h4 keeps it out of the page table of contents. + Data freshness: the widget's data is server-rendered, not fetched by the + browser and not baked into this MDX. The docs-site renders + on the server from content/feature-support.json + in this repo, cached under the "feature-support" Next.js cache tag. When + that file changes on main — the daily Daikon bot PR merge — the + revalidate-content workflow calls the docs-site + /api/revalidate/feature-support endpoint to invalidate the tag, so the + statically generated page re-renders with fresh data (an hourly TTL + backstops a missed webhook). JSON-only daily updates therefore reach + readers without this MDX being edited. + + The summary table below cannot drift from the JSON: the daily workflow + regenerates both from the same resolved data and commits them together, + so any change that affects the table is itself an MDX edit and + revalidates through the markdown path. A JSON-only commit means the + table's coarser product-by-chain view genuinely did not change. + + The summary block is intentionally wrapped in a hidden div: it exists for + search engines, LLMs, and markdown consumers, while the interactive + widget is the human-facing view. The h4 keeps it + out of the page table of contents. */}