[docs-agent] Add Transfers By Wallet to agent-skills and Cursor tutorial cross-refs - #1673
alchemy-bot wants to merge 1 commit into
Conversation
…ial cross-refs Two cross-reference omissions from the original PR #1636 that added the Transfers By Wallet (Beta) endpoint: * content/tutorials/build-with-ai/alchemy-agent-skills.mdx: Portfolio API bullet in the "full Alchemy API surface" list now reads "Multi-chain token balances, NFT data, and transfer history" (was "Multi-chain token balances and NFT data"). * content/tutorials/build-with-ai/data-apis-with-cursor.mdx: Section #4 Portfolio API "Key Method" bullet is now plural ("Key Methods") with a parallel bullet for /data/v1/:apiKey/transfers/by-address alongside the existing /assets/tokens/by-address entry. Scoped to prose-only additions. CLI (alchemy-cli.mdx) and MCP server (alchemy-mcp-server.mdx) cross-ref additions are held pending confirmation that those tools expose a Transfers By Wallet surface. Requested-by: @brianluong
🔗 Preview Mode
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 09c8366064
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| * **Key Method**: | ||
| * **Key Methods**: | ||
| * [/data/v1/:apiKey/assets/tokens/by-address](https://www.alchemy.com/docs/data/portfolio-apis/portfolio-api-endpoints/portfolio-api-endpoints/get-tokens-by-address): fetches fungible tokens (native, ERC-20 and SPL) for multiple wallet addresses and networks. Returns a list of tokens with balances, prices, and metadata for each wallet/network combination. | ||
| * [/data/v1/:apiKey/transfers/by-address](https://www.alchemy.com/docs/data/portfolio-apis/portfolio-api-endpoints/portfolio-api-endpoints/get-transfers-by-address): fetches historical transfers (native, ERC-20, ERC-721, ERC-1155, special NFT, and internal) for a single wallet address across multiple networks. Returns a list of transfers ordered by `blockTimestamp`. |
There was a problem hiding this comment.
The linked endpoint is not generally available: its source specification labels it beta, says not to rely on it in production, and requires readers to request access. Presenting it as an unqualified peer key method in this tutorial can lead readers to build around an endpoint they cannot call or deploy; add the beta/access limitation here (and keep the capability summary consistent).
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Thanks for flagging. Context on this one:
- The parent PR docs: add beta multichain transfers endpoint #1636 established the cross-reference pattern for Transfers By Wallet across these tutorials without inline beta flags; the
(Beta)label lives in the method's OpenAPI title and on its endpoint page, which both references link to. - Sibling PR [docs-agent] Portfolio transfers-by-address: drop beta access-request line, add CU cost #1672 (approved, awaiting merge) drops the access-request language from the OpenAPI description; the
Betastatus itself is retained. - The agent-skills entry is a one-word surface mention (
transfer history) in a bulleted API catalog, and the Cursor tutorial reference is a method link in a Key Methods list — neither is an invitation to deploy to production.
Happy to add inline (beta) markers to either or both if the reviewer prefers that convention; holding as-is pending human judgment.
This branch has not been deployed
1 participant
Summary
Two cross-reference omissions from the original PR #1636 (which first added the Transfers By Wallet (Beta) endpoint). Both files under
content/tutorials/build-with-ai/were missed when the endpoint was initially documented and now reference every sibling Portfolio API endpoint except this one.Changes
content/tutorials/build-with-ai/alchemy-agent-skills.mdx(line 34): the Portfolio API bullet in the "full Alchemy API surface" list now reads Multi-chain token balances, NFT data, and transfer history (was Multi-chain token balances and NFT data).content/tutorials/build-with-ai/data-apis-with-cursor.mdx(section feat: Restructure repo to account for more API specs/markdown #4 Portfolio API): "Key Method" is now plural ("Key Methods") with a parallel bullet for/data/v1/:apiKey/transfers/by-addressalongside the existing/assets/tokens/by-addressentry.Out of scope for this PR
Two other candidate call sites found during the audit but held pending upstream confirmation:
content/tutorials/build-with-ai/alchemy-cli.mdxlines 161-164 — thealchemy evm data portfoliosubcommand table liststokens | token-balances | nfts | nft-contracts. If the CLI exposesalchemy evm data portfolio transfers, a row should be added. Not confirmed from docs-agent reach.content/tutorials/build-with-ai/alchemy-mcp-server.mdxlines 399-406 — "Portfolio / Multi-Chain Data (4 tools)" accordion listsgetTokensByAddress,getTokenBalancesByAddress,getNFTsByAddress,getNFTContractsByAddress. If the MCP server exposesgetTransfersByAddress, a row + accordion title bump to (5 tools) applies. Not confirmed.Separately: the Claude agent skills content in
alchemyplatform/skillsmay also need a Transfers By Wallet entry; that is a different repo and PR.Related
Companion to #1672 (compute-unit-costs row + OpenAPI access-request line removal) and OMGWINNING/chain-config#7571 (topconfig CU + METHOD_PRERELEASE flip). This PR is a sibling, not a stack — kept separate because the review surface is tutorial prose, not pricing or spec data.
Requested by
@brianluong (via Slack thread, same originator as #1672 and OMGWINNING/chain-config#7571)