From d428a978009f0292fadbbe28594f6f616836d2b4 Mon Sep 17 00:00:00 2001 From: alchemy-bot <80712764+alchemy-bot@users.noreply.github.com> Date: Fri, 2 Oct 2026 21:36:47 +0000 Subject: [PATCH 1/4] [docs-agent] Portfolio transfers-by-address: drop beta access-request line, add CU cost Removes the "To request access, email data_apis@alchemy.com." sentence from the Transfers By Wallet (Beta) endpoint description now that access is open. Adds a row for transfers/by-address to the Portfolio API table on the Compute Unit Costs page with a footnote documenting that it uses dynamic pricing of 480 CUs per network specified in the request. Requested-by: @brianluong --- .../pricing/compute-unit-costs.mdx | 27 ++++++++++--------- .../portfolio/transfers/by-address.yaml | 2 +- 2 files changed, 16 insertions(+), 13 deletions(-) diff --git a/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx b/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx index cd01b6ad1..546dda804 100644 --- a/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx +++ b/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx @@ -396,20 +396,23 @@ We want builders to be able to use as much of the NFT API as they need without w # Portfolio API {/* cu:auto product="portfolio" */} -| Method | CU | Throughput CU | -| --------------------------------- | ---- | ------------- | -| utility/blocks/by-timestamp | 10 | 1 | -| stellar/balances | 40 | | -| stellar/nfts | 40 | | -| stellar/transfers | 40 | | -| assets/tokens/balances/by-address | 200 | 1 | -| tokens/balances/by-address | 200 | 1 | -| assets/tokens/by-address | 360 | 1 | -| assets/nfts/contracts/by-address | 600 | 1 | -| assets/nfts/by-address | 1000 | 1 | -| transactions/history/by-address | 1000 | 100 | +| Method | CU | Throughput CU | +| --------------------------------- | ----- | ------------- | +| utility/blocks/by-timestamp | 10 | 1 | +| stellar/balances | 40 | | +| stellar/nfts | 40 | | +| stellar/transfers | 40 | | +| assets/tokens/balances/by-address | 200 | 1 | +| tokens/balances/by-address | 200 | 1 | +| assets/tokens/by-address | 360 | 1 | +| transfers/by-address | 480\* | 1 | +| assets/nfts/contracts/by-address | 600 | 1 | +| assets/nfts/by-address | 1000 | 1 | +| transactions/history/by-address | 1000 | 100 | {/* cu:auto end */} +\*`transfers/by-address` uses dynamic pricing: **480 CUs per network** specified in the `networks` request-body field. For example, a request specifying 3 networks costs 1,440 CUs. + # Prices API {/* cu:auto product="prices" */} diff --git a/src/openapi/portfolio/transfers/by-address.yaml b/src/openapi/portfolio/transfers/by-address.yaml index 3f37a1d11..ac9d3efdf 100644 --- a/src/openapi/portfolio/transfers/by-address.yaml +++ b/src/openapi/portfolio/transfers/by-address.yaml @@ -1,7 +1,7 @@ summary: Transfers By Wallet (Beta) description: > **Beta:** This endpoint is in beta. Do not rely on it in production. This API can change at any - time. To request access, email [data_apis@alchemy.com](mailto:data_apis@alchemy.com). + time. Fetches historical transfers (native, ERC-20, ERC-721, ERC-1155, special NFT, and internal) for From 0c022bb56490181bd0a4c7328e81781b3835483c Mon Sep 17 00:00:00 2001 From: alchemy-bot <80712764+alchemy-bot@users.noreply.github.com> Date: Fri, 2 Oct 2026 21:49:37 +0000 Subject: [PATCH 2/4] [docs-agent] Portfolio transfers-by-address: note throughput CUs scale per network too Follow-up to Brian's feedback in Slack: expand the dynamic-pricing footnote to make clear that BOTH compute units (480 per network) AND throughput CUs (1 per network) scale with the networks[].length in the request. Example updated to show both costs for a 3-network request. Also added a `*` marker to the Throughput CU cell for symmetry with the CU column so the footnote anchors both sides. Requested-by: @brianluong --- .../pricing-resources/pricing/compute-unit-costs.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx b/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx index 546dda804..6e50d4a95 100644 --- a/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx +++ b/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx @@ -405,13 +405,13 @@ We want builders to be able to use as much of the NFT API as they need without w | assets/tokens/balances/by-address | 200 | 1 | | tokens/balances/by-address | 200 | 1 | | assets/tokens/by-address | 360 | 1 | -| transfers/by-address | 480\* | 1 | +| transfers/by-address | 480\* | 1\* | | assets/nfts/contracts/by-address | 600 | 1 | | assets/nfts/by-address | 1000 | 1 | | transactions/history/by-address | 1000 | 100 | {/* cu:auto end */} -\*`transfers/by-address` uses dynamic pricing: **480 CUs per network** specified in the `networks` request-body field. For example, a request specifying 3 networks costs 1,440 CUs. +\*`transfers/by-address` uses dynamic pricing. Both the compute units (**480 per network**) and the throughput CUs (**1 per network**) scale with the number of networks specified in the `networks` request-body field. For example, a request specifying 3 networks costs 1,440 CUs and consumes 3 throughput CUs. # Prices API From da9f5c11a991aee741b04a3cd278a70835b036ed Mon Sep 17 00:00:00 2001 From: alchemy-bot <80712764+alchemy-bot@users.noreply.github.com> Date: Fri, 2 Oct 2026 22:14:33 +0000 Subject: [PATCH 3/4] [docs-agent] Portfolio transfers-by-address: drop in-table asterisks, use standalone Note callout The cu:auto block is fully regenerated by Daikon from chain-config topconfig on each daily sync, which would strip the `480*` / `1*` asterisks and leave the footnote with orphaned anchors. This commit keeps the table cells as plain `480` / `1` so the Daikon sync picks them up without churn, and lifts the dynamic-pricing explanation into a callout immediately below the auto block. The component matches the existing callout at the top of the page, is anchored by its title to the specific method, and sits outside the cu:auto markers so it is preserved across regenerations. More visible to customers than an asterisk-prefixed paragraph. Requested-by: @brianluong --- .../pricing/compute-unit-costs.mdx | 30 ++++++++++--------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx b/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx index 6e50d4a95..a5ec992df 100644 --- a/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx +++ b/content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx @@ -396,22 +396,24 @@ We want builders to be able to use as much of the NFT API as they need without w # Portfolio API {/* cu:auto product="portfolio" */} -| Method | CU | Throughput CU | -| --------------------------------- | ----- | ------------- | -| utility/blocks/by-timestamp | 10 | 1 | -| stellar/balances | 40 | | -| stellar/nfts | 40 | | -| stellar/transfers | 40 | | -| assets/tokens/balances/by-address | 200 | 1 | -| tokens/balances/by-address | 200 | 1 | -| assets/tokens/by-address | 360 | 1 | -| transfers/by-address | 480\* | 1\* | -| assets/nfts/contracts/by-address | 600 | 1 | -| assets/nfts/by-address | 1000 | 1 | -| transactions/history/by-address | 1000 | 100 | +| Method | CU | Throughput CU | +| --------------------------------- | ---- | ------------- | +| utility/blocks/by-timestamp | 10 | 1 | +| stellar/balances | 40 | | +| stellar/nfts | 40 | | +| stellar/transfers | 40 | | +| assets/tokens/balances/by-address | 200 | 1 | +| tokens/balances/by-address | 200 | 1 | +| assets/tokens/by-address | 360 | 1 | +| transfers/by-address | 480 | 1 | +| assets/nfts/contracts/by-address | 600 | 1 | +| assets/nfts/by-address | 1000 | 1 | +| transactions/history/by-address | 1000 | 100 | {/* cu:auto end */} -\*`transfers/by-address` uses dynamic pricing. Both the compute units (**480 per network**) and the throughput CUs (**1 per network**) scale with the number of networks specified in the `networks` request-body field. For example, a request specifying 3 networks costs 1,440 CUs and consumes 3 throughput CUs. + + Both the compute units (**480 per network**) and the throughput CUs (**1 per network**) scale with the number of networks specified in the `networks` request-body field. For example, a request specifying 3 networks costs 1,440 CUs and consumes 3 throughput CUs. + # Prices API From 51624b08e49b47417e7efe9f7314971fd926f884 Mon Sep 17 00:00:00 2001 From: Brian Luong Date: Tue, 6 Oct 2026 09:46:20 -0700 Subject: [PATCH 4/4] docs(portfolio): reword transfers-by-address beta notice Replace "Do not rely on it in production" with copy that says the endpoint is production-ready and supported, while still reserving the right to make breaking changes during the beta. Co-Authored-By: Claude Opus 5.5 (1M context) --- src/openapi/portfolio/transfers/by-address.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/openapi/portfolio/transfers/by-address.yaml b/src/openapi/portfolio/transfers/by-address.yaml index ac9d3efdf..507a01379 100644 --- a/src/openapi/portfolio/transfers/by-address.yaml +++ b/src/openapi/portfolio/transfers/by-address.yaml @@ -1,7 +1,7 @@ summary: Transfers By Wallet (Beta) description: > - **Beta:** This endpoint is in beta. Do not rely on it in production. This API can change at any - time. + **Beta:** This endpoint is production-ready and fully supported. While it's in beta, the API may + still change, including breaking changes. Fetches historical transfers (native, ERC-20, ERC-721, ERC-1155, special NFT, and internal) for