Uh oh!
There was an error while loading. Please reload this page.
Remove AI-generated content warnings and update internal links - #77
Conversation
This was referenced Mar 3, 2026
Merged
Merged
Merged
Merged
Merged
ContributorAuthor
rodrigopavezi
changed the base branch from
03-03-docs_resources_align_lifecycle-of-a-request_with_legacy_content_and_local_assets_update_resources_lifecycle-of-a-request.mdx_to_match_legacy_lifecycle_documentation_while_removing_legacy-hosted_dependencies._-_removed_ai-generat
to
graphite-base/77March 30, 2026 18:15
rodrigopaveziforce-pushed
the
graphite-base/77
branch
from
March 30, 2026 18:15
6f231b0 to
8f88beeComparerodrigopavezi
changed the base branch from
main
to
03-03-docs_resources_align_lifecycle-of-a-request_with_legacy_content_and_local_assets_update_resources_lifecycle-of-a-request.mdx_to_match_legacy_lifecycle_documentation_while_removing_legacy-hosted_dependencies._-_removed_ai-generatMarch 30, 2026 18:20
rodrigopavezi
changed the base branch from
03-03-docs_resources_align_lifecycle-of-a-request_with_legacy_content_and_local_assets_update_resources_lifecycle-of-a-request.mdx_to_match_legacy_lifecycle_documentation_while_removing_legacy-hosted_dependencies._-_removed_ai-generat
to
graphite-base/77March 30, 2026 18:27
rodrigopavezi
changed the base branch from
graphite-base/77
to
03-03-docs_resources_align_lifecycle-of-a-request_with_legacy_content_and_local_assets_update_resources_lifecycle-of-a-request.mdx_to_match_legacy_lifecycle_documentation_while_removing_legacy-hosted_dependencies._-_removed_ai-generatMarch 30, 2026 18:27
This was referenced Mar 30, 2026
This was referenced May 8, 2026
rodrigopavezi added a commit
that referenced
this pull request
May 11, 2026
Bundles two passes of Greptile feedback: (A) PR #96 follow-up — the fixes PR itself attracted two new comments: - use-cases/programmatic-payment-links.mdx: cURL language tag bash → curl - RN_API_KEY → RN_CLIENT_ID and X-Api-Key → x-client-id renamed across api-setup/integration-tutorial.mdx, api-setup/getting-started.mdx, api-features/create-requests.mdx for stack-wide consistency. Zero RN_API_KEY / X-Api-Key references remain. (B) Older PRs (51-87) — 23 still-applicable comments out of 51 total. The other 28 are stale (resolved by the revamp rewriting or removing the relevant sections/files); those will be resolved on GitHub with a note explaining staleness. PR #53 — getting-started.mdx - Added Express setup (express + app.use(express.json())) before the webhook handler example so the snippet is runnable. PR #54 — integration-tutorial.mdx - Added missing `import { eq } from 'drizzle-orm';`. - Fixed spelling "succesfully" → "successfully". PR #55 — create-requests.mdx - v2 pay endpoint takes requestId, not paymentReference (mermaid + code sample updated to `${requestId}/pay`). PR #56 + #87 — crosschain-payments.mdx - Boundary wording: "under \$1" → "of \$1 or less" to align with the "greater than 1 USD" half of the sentence. - viem snippet now imports createPublicClient + http and instantiates publicClient so `publicClient.waitForTransactionReceipt(...)` works. PR #57 — batch-payments.mdx - Code samples now use x-client-id (consistent with rest of docs), dropped legacy x-platform-id, added `if (!response.ok)` error handling on both examples. PR #59 — crypto-to-fiat-payments.mdx - "I**mportant:" → "**Important:" - mermaid: {payerId} → {clientUserId} (twice). - Endpoint paths: /payer → /v2/payer for consistency. - mermaid: declared "Payee Bank" as a participant (was used but never declared, breaking the diagram). PR #66 — query-payments.mdx - Frontmatter description: /payments → /v2/payments. PR #67 — platform-fees.mdx - Clarified query- vs body-param scope: GET /v2/request/{id}/pay uses query params; POST /v2/payouts and /payouts/batch use body params. PR #68 — protocol-fees.mdx - Grammar: "protocol fees applies" → "protocol fee applies". - Typo: "simple reduce" → "simply reduce". - Math: payee receives 999.50 USDC (not 999.95). Added intermediate invoice/fee lines for transparency. PR #77 — faq.mdx - On-ramp question now explicitly answered: "Fiat-to-crypto (on-ramp) payments are not currently supported by the API." PR #86 — payouts.mdx - "ERC-712" → "EIP-712" (correct EIP designation). PR #86 — api-reference/secure-payments.mdx - expiresAt example: 15 minutes → 7 days, matching the documented default expiry. PR #87 — payouts.mdx - Added "500" row to error-handling table. mintlify broken-links: zero.
Contributor
Merge activity
|
rodrigopavezi
changed the base branch from
03-03-docs_resources_align_lifecycle-of-a-request_with_legacy_content_and_local_assets_update_resources_lifecycle-of-a-request.mdx_to_match_legacy_lifecycle_documentation_while_removing_legacy-hosted_dependencies._-_removed_ai-generat
to
graphite-base/77May 12, 2026 16:52
…and accurate links Refine `faq.mdx` and `glossary.mdx` to keep legacy structure/content while removing migration artifacts and fixing outdated references. - removed AI-generated warning banners from both pages - preserved legacy FAQ/Glossary layout and core definitions - updated FAQ answers that were no longer accurate (notably crypto-to-fiat support) - replaced generic or confusing references with feature-specific links where appropriate - cleaned old `docs.request.network` dependencies and moved to current internal/docs links where possible - fixed inconsistent link behavior in FAQ responses to improve readability and navigation
rodrigopaveziforce-pushed
the
03-03-docs_resources_update_faq_and_glossary_with_legacy-aligned_content_and_accurate_links_refine_faq.mdx_and_glossary.mdx_to_keep_legacy_structure_content_while_removing_migration_artifacts_and_fixing_outdated_references._-_removed_
branch
from
May 12, 2026 16:54
0ef3c12 to
1bfc1c6CompareUh oh!
There was an error while loading. Please reload this page.
rodrigopavezi
deleted the
03-03-docs_resources_update_faq_and_glossary_with_legacy-aligned_content_and_accurate_links_refine_faq.mdx_and_glossary.mdx_to_keep_legacy_structure_content_while_removing_migration_artifacts_and_fixing_outdated_references._-_removed_
branch
May 12, 2026 16:55
rodrigopavezi added a commit
that referenced
this pull request
May 12, 2026
Bundles two passes of Greptile feedback: (A) PR #96 follow-up — the fixes PR itself attracted two new comments: - use-cases/programmatic-payment-links.mdx: cURL language tag bash → curl - RN_API_KEY → RN_CLIENT_ID and X-Api-Key → x-client-id renamed across api-setup/integration-tutorial.mdx, api-setup/getting-started.mdx, api-features/create-requests.mdx for stack-wide consistency. Zero RN_API_KEY / X-Api-Key references remain. (B) Older PRs (51-87) — 23 still-applicable comments out of 51 total. The other 28 are stale (resolved by the revamp rewriting or removing the relevant sections/files); those will be resolved on GitHub with a note explaining staleness. PR #53 — getting-started.mdx - Added Express setup (express + app.use(express.json())) before the webhook handler example so the snippet is runnable. PR #54 — integration-tutorial.mdx - Added missing `import { eq } from 'drizzle-orm';`. - Fixed spelling "succesfully" → "successfully". PR #55 — create-requests.mdx - v2 pay endpoint takes requestId, not paymentReference (mermaid + code sample updated to `${requestId}/pay`). PR #56 + #87 — crosschain-payments.mdx - Boundary wording: "under \$1" → "of \$1 or less" to align with the "greater than 1 USD" half of the sentence. - viem snippet now imports createPublicClient + http and instantiates publicClient so `publicClient.waitForTransactionReceipt(...)` works. PR #57 — batch-payments.mdx - Code samples now use x-client-id (consistent with rest of docs), dropped legacy x-platform-id, added `if (!response.ok)` error handling on both examples. PR #59 — crypto-to-fiat-payments.mdx - "I**mportant:" → "**Important:" - mermaid: {payerId} → {clientUserId} (twice). - Endpoint paths: /payer → /v2/payer for consistency. - mermaid: declared "Payee Bank" as a participant (was used but never declared, breaking the diagram). PR #66 — query-payments.mdx - Frontmatter description: /payments → /v2/payments. PR #67 — platform-fees.mdx - Clarified query- vs body-param scope: GET /v2/request/{id}/pay uses query params; POST /v2/payouts and /payouts/batch use body params. PR #68 — protocol-fees.mdx - Grammar: "protocol fees applies" → "protocol fee applies". - Typo: "simple reduce" → "simply reduce". - Math: payee receives 999.50 USDC (not 999.95). Added intermediate invoice/fee lines for transparency. PR #77 — faq.mdx - On-ramp question now explicitly answered: "Fiat-to-crypto (on-ramp) payments are not currently supported by the API." PR #86 — payouts.mdx - "ERC-712" → "EIP-712" (correct EIP designation). PR #86 — api-reference/secure-payments.mdx - expiresAt example: 15 minutes → 7 days, matching the documented default expiry. PR #87 — payouts.mdx - Added "500" row to error-handling table. mintlify broken-links: zero.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
TL;DR
Removed AI-generated content warnings and updated internal documentation links to use relative paths instead of absolute URLs.
What changed?
/resources/supported-chains-and-currenciesinstead ofhttps://docs.request.network/get-started/supported-chains)How to test?
Why make this change?
The AI-generated content warnings were no longer needed as the content has been reviewed and validated. Using relative paths for internal links improves maintainability and ensures links work correctly across different deployment environments. The changes also reflect current product capabilities, such as crypto-to-fiat payment support via the API.