docs: add FAQ about self-custodial wallet connection limits

[devin-ai-integration]

Description

Adds a new FAQ entry to the AppKit FAQ page under the Features section:

Q: Is there a limit on self-custodial wallet connections?

The answer clarifies that there is no fixed limit on self-custodial connections, explains the fair-use clause in the ToS, and references the Community Licence thresholds (500 MAUs/month, 2.5M RPC calls/month). It also addresses the case where developers use their own RPC provider.

Updates since last revision

• Removed the Community Licence hyperlink (previously pointed to appkit-react-native repo) per reviewer feedback. The text now references "Community Licence" without a link.

Reviewer checklist

• Confirm whether "Community Licence" should remain unlinked or if a different canonical URL should be added
• Confirm the stated thresholds (500 MAUs, 2.5M RPC) are accurate and up to date
• Check that the ToS/fair-use language aligns with current legal terms

Tests

• Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
• Ran a grammar check on the updated/created content using ChatGPT.

Direct link to the deployed preview files

• AppKit FAQ page

Link to Devin session: https://app.devin.ai/sessions/da0deb4eba3a4bb1a15ae7edf6cf8f5a

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[claude]

Claude finished @devin-ai-integration[bot]'s task in 1m 18s —— View job

---

PR Review

• Read tone of voice guidelines
• Read changed file
• Analyze content for issues
• Post review

---

Found 3 issue(s)

Issue 1: Community Licence link points to React Native–specific repo

ID: faq-licence-link-scope-a3f1
File: appkit/faq.mdx:161
Severity: HIGH
Category: code_quality

Context:

• Pattern: The link https://github.com/reown-com/appkit-react-native?tab=License-1-ov-file#readme targets a React Native–specific repository as the canonical licence source for general AppKit limits.
• Risk: Developers using React, Vue, Flutter, iOS, Android, or any other AppKit platform may be confused or misled — the thresholds stated in one SDK's licence may not apply to all SDKs.
• Impact: Incorrect guidance for the majority of AppKit users; potential support escalations if limits differ across SDKs.
• Trigger: Any non-React-Native developer reading the FAQ.

Note: The PR author explicitly flagged this for reviewer verification: "Verify the Community Licence link (appkit-react-native repo) is the correct canonical source for licence thresholds." This should be confirmed before merge.

Recommendation: Link to the main appkit repo licence or a dedicated licence/pricing page if one exists, e.g.:

See our [Community Licence](https://github.com/reown-com/appkit?tab=License-1-ov-file#readme) for the clearest thresholds…

---

Issue 2: External domain URL (github.com) — verify intentional

ID: faq-external-github-url-b2e7
File: appkit/faq.mdx:161
Severity: LOW
Category: code_quality

Context:

• Pattern: Link points to github.com, which is outside the approved domains (reown.com, walletconnect.com, walletconnect.org).
• Risk: If licence terms move or the repo is renamed/archived, this deep-link will break silently.
• Impact: Broken link; potential confusion for developers.
• Trigger: Any reader clicking the Community Licence link.

Recommendation: If a stable, canonical licence page exists on reown.com, prefer that. Otherwise, ensure the GitHub link is monitored for validity.

---

Issue 3: Tone of voice — informal/fear-adjacent phrasing in developer docs

ID: faq-tov-spike-attack-phrasing-c9d4
File: appkit/faq.mdx:166
Severity: LOW
Category: code_quality

Context:

• Pattern: The phrase "If your usage could reasonably be described as a spike attack or sustained automated abuse, that is when it becomes a concern." mixes informal conversational tone with a fear-adjacent concept.
• Risk: Per Reown's tone guidelines: developer docs should be "informative, professional, straightforward, helpful and respectful of developers' time" — and the brand avoids messaging that makes its platform sound potentially unsafe or punitive. "Spike attack" is also a non-standard term that may be unclear.
• Impact: Could create unnecessary anxiety for developers with legitimate high-traffic apps.
• Trigger: Any developer reading this FAQ entry.

Recommendation: Rewrite to be factual and reassuring rather than punitive:

The only limit that could apply is the general fair-use clause in our ToS.
This is aimed at clearly abusive patterns — such as traffic flooding or automated
spam — and does not affect normal application usage.

Additional note: The PR description flags three unresolved factual questions that require human verification before merge:

1. Is the appkit-react-native repo the correct canonical licence source?
2. Are the 500 MAU / 2.5M RPC thresholds accurate and current?
3. Does the ToS/fair-use language match current legal terms?

These are content-accuracy concerns that tooling cannot verify — a team member with access to legal/product context should sign off.