[docs-agent] Add Agent Wallets page to Build with AI section#1290
Open
JackReacher0807 wants to merge 1 commit into
Open
[docs-agent] Add Agent Wallets page to Build with AI section#1290JackReacher0807 wants to merge 1 commit into
JackReacher0807 wants to merge 1 commit into
Conversation
New conceptual page at /docs/agent-wallets that explains agent wallets at a high level: what they are (a Privy-custodied wallet with a CLI session signer the user approves and revokes from the dashboard), why they replace pasted private keys and custom backends, how the three-party trust model works, what the agent can do once a session is live, and the three-command quickstart from the launch blog. Cross-links to the CLI page's Wallets and signing reference, the Wallet APIs product docs, and the Agent Authentication and Payment page. Sidebar entry added directly after Alchemy CLI under Build with AI. Refs DOCS-76 Requested-by: @CodesMcCabe
🔗 Preview Mode
|
🔍 Link CheckStatus: ❌ Failed Summary
Broken links (8) — click to expandErrors per inputErrors in ./content/api-reference/data/webhooks/custom-webhooks-quickstart/custom-webhooks-quickstart.mdx
Errors in ./content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx
Errors in ./content/wallets/pages/recipes/onramp-funds.mdx
Errors in ./content/tutorials/smart-wallets/learn-account-abstraction/introduction-to-account-abstraction.mdx
Errors in ./content/wallets/wallet-integrations/privy/signer-migration-overview.mdx
Errors in ./content/api-reference/arbitrum-nova/arbitrum-nova-deprecation-notice.mdx
Errors in ./content/api-reference/starknet/starknet-api-faq.mdx
|
SahilAujla
approved these changes
May 8, 2026
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
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
New conceptual page at
/docs/agent-walletsthat gives a high-level explanation of Alchemy's agent wallets and how they're used in the Alchemy CLI, drawing from the launch blog post and pairing it with the existing CLI command reference.The page covers:
.env.alchemy evm send,swap,bridge,contract call,approve, all backed by the Wallet APIs so gas sponsorship, batching, retries, and ERC-20 gas payments come along automatically.npm i,alchemy auth,alchemy wallet connect), plus an exampleevm sendand how to revoke.--json/--no-interactiveflags andalchemy agent-promptso the agent picks up the wallet commands without integration work.The page links into the CLI doc's
#wallets-and-signingsection for the full command reference rather than duplicating it, so the two pages have clean roles: agent-wallets is the conceptual intro, alchemy-cli is the command surface.Changes
content/tutorials/build-with-ai/agent-wallets.mdx(slugdocs/agent-wallets)content/docs.yml: sidebar entry added under Build with AI, immediately after Alchemy CLI — pairs the conceptual page with the CLI reference and keeps related content adjacentLinear
DOCS-76 — Add "Agent Wallets" page to Build with AI section
Requested by
@CodesMcCabe (via Slack thread)