Update Capsule Access Links

[nityas]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR updates the API Key acquisition link for Capsule signers and provides clearer integration steps in the documentation.

Detailed summary

• Updated API Key acquisition link to https://usecapsule.com/api
• Clarified integration steps in the documentation for Capsule signers

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 7, 2024 11:29pm

[vercel]

@nityas is attempting to deploy a commit to the Alchemy Team on Vercel.

A member of the Team first needs to authorize it.

[moldy530]

Hey @nityas, a quick heads up for y'all: we're going to be dropping support for aa-signers going forward with the v4 release of the SDK. This is largely due to it being hard to maintain when we don't have context and it's not a standard practice for most SDKs. We recommend instead publishing an aa package that y'all maintain that uses aa-sdk under the hood. We will be keeping a part of the site where 3rd party signers can link to their docs + packages when we release the v4 package