[docs-agent] Portfolio transfers-by-address: drop beta access-request line, add CU cost - #1672
Open
alchemy-bot wants to merge 3 commits into
Open
alchemy-bot wants to merge 3 commits into
alchemy-bot wants to merge 3 commits into
Conversation
… 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
🔗 Preview Mode
|
Contributor
Author
|
Companion |
…e 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
… 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 <Note> callout immediately below the auto block. The <Note> component matches the existing <Tip> 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
dslovinsky
approved these changes
Oct 2, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two small Portfolio-API cleanups requested in Slack:
src/openapi/portfolio/transfers/by-address.yaml— removes theTo request access, email data_apis@alchemy.com.sentence from theTransfers By Wallet (Beta)endpoint description, now that access is open.content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx— adds atransfers/by-addressrow to the Portfolio API table at 480* CU (slotted betweenassets/tokens/by-addressat 360 andassets/nfts/contracts/by-addressat 600) with a footnote documenting the dynamic pricing: 480 CUs per network specified in thenetworksrequest-body field.Notes
{/* cu:auto product="portfolio" */}block that gets regenerated daily by Daikon fromtopconfig.ymlinOMGWINNING/chain-config. Iftopconfig.ymldoes not yet carry atransfers/by-addressentry, the next Daikon run will strip this new row (the explanatory footnote below the block will persist either way). A companionchain-configedit may be needed to make the row stick long-term; flagged in Slack.\*...) sits immediately below{/* cu:auto end */}so it is not overwritten by Daikon regeneration.Throughput CUfor the new row is set to1to match the other/by-addresssibling multichain Portfolio endpoints; happy to adjust if that's wrong.Requested by
@brianluong (via Slack thread)