docs(verify): fix broken cross-refs surfaced by mintlify broken-links

[rodrigopavezi]

docs(verify): fix broken cross-refs surfaced by mintlify broken-links

• api-reference/endpoints-overview.mdx: replace 4 dead /api-reference/...
  internal links with the canonical https://api.request.network/open-api/
  group anchors. Those internal anchors don't exist on this site (they
  belonged to a tag-driven generator that's no longer wired up).
• api-features/secure-payment-pages.mdx: redirect the POST /v2/secure-payments
  Card to /api-reference/secure-payments which is the actual page.

Remaining mintlify broken-links output:

• 24 references to /images/dashboard/.webp and /images/secure-payments/.webp
  — these are the screenshots that Phase D's capture pipeline will produce
  (see scripts/capture-screenshots.ts). Expected and documented.
• 5 references in AGENTS.md to /quickstart, /auth, /rate-limits and two
  /images/*.png paths — AGENTS.md is internal AI-agent guidance, not
  user-facing docs. Out of scope for this revamp.

docs(images): capture Dashboard + Secure Payment screenshots

Captured 8 screenshots from staging via the new screenshots Playwright
project in request-e2e-tests (which reuses the Synpress + DashboardHelper
setup).

Dashboard (8):

• login-evm.webp, login-tron.webp — unauthenticated /login screens
  (captured from a fresh Chromium context to defeat the fixture's
  pre-authenticated state)
• home-with-destination.webp — Receiving Route panel
• manage-destination.webp — destination + Client IDs section
• get-paid-list.webp, get-paid-new.webp, get-paid-detail.webp — incoming
  payment request flows
• pay-list.webp — outgoing payouts list

Secure Payment (1):

• connect-wallet.webp — wallet picker modal (MetaMask, Coinbase,
  WalletConnect)

Manual / not yet captured (logged by the spec):

• dashboard/home-empty, create-destination, generate-client-id,
  client-id-details — require a fresh wallet without an existing
  destination, or specific dialogs mid-flow
• secure-payments/connect-wallet-tron, payment-options,
  payment-options-crosschain, advanced-view, payment-success — require
  a connected payer wallet (Buyer account) + a paid request

The mintlify broken-links report should drop from 24 image-related
warnings to ~16 after this commit.

docs(images): capture 6 more screenshots — dialogs + payer-side payment options

Extended the screenshots Playwright project to capture wallet-gated and
mid-flow shots that the first pass marked MANUAL.

Dashboard (4):

• home-empty.webp — "No route configured" empty state with CTA
  (captured by deactivating the destination then restoring it)
• create-destination.webp — Create Payment Destination dialog mid-flow
• generate-client-id.webp — Generate New Client ID dialog with form
• client-id-details.webp — Client ID Details dialog with copy button

Secure Payment (2):

• payment-options.webp — chain × token selector with same-chain indicator
  and "Choose this currency" CTA (captured after payer wallet connects via
  Synpress)
• advanced-view.webp — same screen with the "show details" expansion
  showing recipient, reference, amount breakdown

Mintlify broken-links: 17 → 11 (5 are AGENTS.md, out of scope).

Still deferred (3 shots, intentionally MANUAL):

• secure-payments/connect-wallet-tron — needs a Tron-destination link +
  TronLink browser extension
• secure-payments/payment-options-crosschain — needs payer balance on a
  chain different from the destination
• secure-payments/payment-success — needs a real on-chain payment (gas)

docs(images): capture payment-success via on-chain Sepolia payment

Extended the screenshots Playwright project with an actual end-to-end
on-chain payment flow (Sepolia, 0.01 fUSDC, Buyer wallet). The capture
runs through PaymentHelper.connectWallet → confirmAddressVerification →
approveTokenIfNeeded → confirmPayment → waitForPaymentSuccess and snaps
the success screen.

Result: payment-success.webp shows the green checkmark, $0.01 USD paid,
recipient/reference/amount table, "via Token Transfer FUSDC on Sepolia",
the on-chain reference hash, and "View on Etherscan" / "View on
BlockScout" buttons.

Mintlify broken-links: 11 → 9 (5 AGENTS.md out-of-scope + 4 references
to the 2 deferred shots).

Still deferred (2 shots, intentionally MANUAL):

• secure-payments/connect-wallet-tron — needs TronLink installed in the
  test browser + a Tron-signed-in dashboard session + a Tron destination
• secure-payments/payment-options-crosschain — needs the payer wallet to
  hold balance on a chain different from the destination. Sepolia is the
  only supported testnet so cross-chain on testnet isn't available; this
  would need a mainnet setup.

docs(content): replace deferred shot refs with text for tron-wallet + crosschain

Drop the four blocks pointing at uncaptured screenshots and replace
them with descriptive text. The two shots — connect-wallet-tron and
payment-options-crosschain — require setups beyond the staging-wallet
auto-capture flow (TronLink + Tron-signed-in session, multi-chain payer
balance) and are deferred indefinitely.

Touched:

• tools/secure-payments.mdx: tron-wallet step now references the EVM modal
  • a sentence about Tron wallets replacing the list; crosschain step
    describes the banner-text difference instead of showing a separate shot.
• use-cases/multi-chain-checkout.mdx: same treatment, condensed.

Mintlify broken-links: 9 → 5 (all 5 remaining are AGENTS.md, out of scope).

docs(webhooks): document Auth API as the only path; drop Dashboard UI claims

There is no Dashboard UI for webhook CRUD. Webhooks are managed
programmatically via the Auth API (POST/GET/PUT/DELETE /v1/webhook with
the x-client-id header) and tested via POST /v1/webhook/test. The earlier
Phase A Portal sweep mistakenly retargeted these claims at the Dashboard
instead of the auth-api endpoints — fix that across every page that
mentions webhook setup.

Touched:

• api-reference/webhooks.mdx — replaced "Setup in Dashboard" + "Portal
  Testing" sections with the actual create/manage/test curl flows; cards
  updated; troubleshooting tips reference auth-api endpoints.
• api-features/webhooks-events.mdx — Development Tools card now points
  at the auth-api webhook endpoints instead of the Dashboard.
• api-reference/authentication.mdx — split the Dashboard (Client IDs)
  vs Auth API (webhooks) responsibilities clearly.
• api-setup/getting-started.mdx — webhook setup now uses curl against
  /v1/webhook; "ensure webhook is enabled in the Dashboard" → use
  PUT /v1/webhook/:id.
• api-setup/integration-tutorial.mdx — replaced the Dashboard
  webhook-creation walkthrough (and its two screenshots) with curl;
  test-event step uses POST /v1/webhook/test.
• api-features/secure-payment-integration-guide.mdx — prereq updated.
• use-cases/webhook-reconciliation.mdx — ngrok comment fixed.

Also removed the now-orphaned Dashboard webhook UI screenshots
(webhook-step-1.webp, webhook-step-2.webp).

docs(audit): align with current source in all four repos

Audited the docs against /Users/rodrigopavezi/Workspace/{request-api,
request-auth-api,request-dashboard,request-secure-payment} and corrected
every claim that no longer matches reality.

tools/dashboard.mdx

• Sign-in: Tron tab is feature-flagged (VITE_TRON_ENABLED), not
  unconditionally co-equal — clarified
• Token table now matches the Dashboard's actual TOKENS_PER_CHAIN: Tron
  exposes USDT only (not USDC), Arbitrum exposes USDT0 (not USDT). Added
  a note that the underlying API supports a wider set
• Client ID dialog: only label + allowedDomains are collectable from the
  UI; advanced fields (fees, operator, expiries, destination binding)
  are API-only — corrected the misleading bullet list
• Pay tab: Dashboard UI today is single-recipient only on both EVM and
  Tron. Removed the "many recipients" claim and dropped the EVM/Tron
  matrix in favour of pointing to the API for batch

tools/secure-payments.mdx + use-cases/multi-chain-checkout.mdx

• Wallet list trimmed to the actual walletConfig in
  components/wallet/ConnectWalletModal.tsx: MetaMask, Coinbase, Wallet-
  Connect, Ledger, Phantom, Rabby. Dropped the misleading "any injected
  EIP-1193 (Bitget, OKX, …)" claim — unrecognised IDs are filtered out
• Added a Smart-Accounts section to tools/secure-payments.mdx — the
  Pimlico/Account-Abstraction integration was documented in api-features/
  secure-payment-pages.mdx but missing from the tools tour

use-cases/quickstart.mdx

• Tron token table: USDT shown as native Dashboard option, USDC noted as
  API-only (since the Dashboard UI doesn't expose USDC-on-Tron today)
• Arbitrum row clarified to show the USDT entry is USDT0

use-cases/no-code-payment-links.mdx

• Reworded "7 EVM chains or Tron" → "7 EVM chains plus Tron" and
  qualified the token list (varies by chain)

api-features/recurring-payments.mdx

• Removed Gnosis (not supported), corrected list to match the actual
  PayeeDestinationNetworkName enum: Ethereum, Arbitrum, Optimism, Base,
  Polygon, BSC + Sepolia
• Added a note that recurring is EVM-only because it relies on EIP-2612
  permit signatures (which Tron doesn't support)

api-features/client-id-management.mdx

• Response example now includes operatorWalletAddress,
  defaultPreApprovalExpiry, defaultAuthorizationExpiry, payeeDestinationId
• Fixed Client ID prefix: cli_ (not ci_)

docs(content): scrub internal implementation details from customer-facing pages

Removed leaks of internal-only context that customers shouldn't need to
care about, while keeping all the customer-visible behavior accurate.

tools/dashboard.mdx

• Sign-in section no longer references the build-time Tron feature flag.
  Customers see whatever's deployed at dashboard.request.network — the
  flag is operational, not product surface.
• "auth-api" lowercase service-name reference → "Auth API" (proper noun)
• EVM/Tron sign-in copy simplified — no more personal_sign /
  tronWeb.trx.signMessageV2 jargon, just "sign the message when
  prompted"

resources/supported-chains-and-currencies.mdx

• Dropped the link into our internal request-api source tree
  (TOKENS_PER_CHAIN). Replaced with a customer-actionable note about
  using the addresses with the Auth API destination endpoint.

release-notes/request-api.mdx

• Removed the "see commit history in the request-api repository" line
  and the GitHub-issues helper link. The release-notes page itself is
  the canonical source for customers; the internal repo isn't.

docs(agents): point AGENTS.md component examples at real pages and images

The Card href examples (/quickstart, /auth, /rate-limits) and Frame img
examples (/images/dashboard.png, /images/analytics.png) were Mintlify
template placeholders that didn't resolve in this site.

Replaced with real, current pages and screenshots we ship:

• /use-cases/quickstart
• /api-reference/authentication
• /api-reference/webhooks
• /images/dashboard/home-with-destination.webp
• /images/dashboard/generate-client-id.webp

Net effect: AGENTS.md still demonstrates Mintlify components, but the
examples now reference live URLs/images, and `mintlify broken-links`
reports zero broken links across the whole site.

docs(sdk-legacy): remove SDK (Legacy) section entirely

The SDK (Legacy) tab was already unlinked from docs.json nav by an
earlier branch in this stack. Now removing the page itself plus the
remaining inbound references that were still pointing at it:

• Deleted sdk-legacy/overview.mdx and the directory.
• use-cases/welcome.mdx: dropped the "SDK (Legacy)" card; the Resources
  card now stands alone.
• resources/lifecycle-of-a-request.mdx: replaced the SDK reference with
  a pointer to the Quickstart.
• glossary.mdx: redirected three "for details see SDK (Legacy)" links
  to the relevant API-features pages (payment-detection,
  crosschain-payments).

mintlify broken-links: still zero.

[greptile-apps]

Greptile Summary

This PR is a comprehensive documentation accuracy pass that fixes broken cross-references, corrects factual claims to match the actual source code across four repos, replaces Dashboard-UI webhook instructions with Auth API curl flows, and adds 14 new screenshots for the Dashboard and Secure Payments pages.

• Broken links: Replaced 4 dead internal anchors in endpoints-overview.mdx with canonical external OpenAPI URLs; fixed one broken Card href in secure-payment-pages.mdx; updated AGENTS.md placeholder paths to real pages/images, bringing the mintlify broken-links count to zero.
• Webhook documentation: Rewrote webhook setup/test/manage instructions across 7 files to use POST /v1/webhook on the Auth API instead of a non-existent Dashboard UI; removed two orphaned webhook screenshots.
• Content accuracy: Corrected the token table (Arbitrum → USDT0, Tron Dashboard UI → USDT-only), Client ID prefix (ci_ → cli_), wallet list trimmed to actual walletConfig, recurring-payments network list updated to match the PayeeDestinationNetworkName enum with an EVM-only caveat, and removed the deleted SDK (Legacy) page along with all inbound references.

Confidence Score: 4/5

Safe to merge with one documentation inconsistency to address: the feature support matrix still marks Tron as supporting recurring payments, directly contradicting the EVM-only correction made to recurring-payments.mdx in this same PR.

The recurring payments feature matrix for Tron was not updated alongside the recurring-payments.mdx change, leaving two pages in this PR contradicting each other on whether Tron supports recurring payments. All other changes are well-scoped corrections with no functional impact beyond documentation accuracy.

resources/supported-chains-and-currencies.mdx — the Recurring payments row in the feature support matrix needs its Tron column flipped from ✓ to ✗.

Important Files Changed

Filename	Overview
resources/supported-chains-and-currencies.mdx	One line updated (link → note), but feature matrix still marks Tron as supporting recurring payments, contradicting the recurring-payments.mdx update in this same PR.
api-reference/webhooks.mdx	Large factual rewrite: removed incorrect 'Setup in Dashboard' section and replaced with Auth API curl flows for create/manage/test webhooks.
api-setup/integration-tutorial.mdx	Replaced Dashboard webhook-creation screenshots with Auth API curl commands; removed orphaned webhook-step-1/2 images.
tools/dashboard.mdx	Token table corrected (Arbitrum → USDT0, Tron → USDT-only in UI); Client ID dialog description narrowed to actual UI fields; pay tab corrected to single-recipient only.
tools/secure-payments.mdx	Wallet list trimmed to actual walletConfig; cross-chain and Tron-wallet screenshots replaced with text; Smart Accounts section added.
api-features/recurring-payments.mdx	Removed Gnosis, corrected network names to match PayeeDestinationNetworkName enum, and added EVM-only note for EIP-2612 dependency.
api-features/client-id-management.mdx	Fixed Client ID prefix cli_ (was ci_); added operatorWalletAddress, defaultPreApprovalExpiry, defaultAuthorizationExpiry, payeeDestinationId to response example.
AGENTS.md	Replaced Mintlify template placeholder hrefs and image paths with real site pages and shipped screenshots, eliminating 5 broken-link warnings.
sdk-legacy/overview.mdx	Deleted the now-unlinked SDK (Legacy) page; inbound references were updated to point at API quickstart or relevant feature pages.

Comments Outside Diff (1)

1. resources/supported-chains-and-currencies.mdx, line 44 (link)

   Feature matrix contradicts the recurring-payments update in this same PR

   api-features/recurring-payments.mdx — also changed in this PR — now explicitly states recurring payments are EVM-only because they rely on EIP-2612 permit signatures, and adds a <Note> saying "Tron does not support ERC-20 permit semantics, so recurring payments are not available on Tron." The feature matrix here still shows a ✓ for Tron in the "Recurring payments" row, which directly contradicts that. A developer consulting this table would conclude Tron supports recurring payments and then hit a confusing failure or misleading documentation further down.

_{Reviews (2): Last reviewed commit: "docs(sdk-legacy): remove SDK (Legacy) se..." | Re-trigger Greptile}

[rodrigopavezi]

Merge activity

• May 12, 4:02 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 12, 5:14 PM UTC: Graphite rebased this pull request as part of a merge.
• May 12, 5:14 PM UTC: @rodrigopavezi merged this pull request with Graphite.