docs(supported-chains): streamline supported chains and currencies documentation

[aimensahnoun]

TL;DR

Streamlined the supported chains and currencies documentation to focus on API-specific coverage and removed AI-generated content warnings.

What changed?

• Removed the AI-generated content warning banner
• Simplified the overview to highlight 500+ currencies across major EVM chains
• Replaced detailed network cards with a concise list of supported chains for ERC20, Native, and Conversion payments
• Condensed currency information to focus on API-relevant details rather than comprehensive token listings
• Added specific sections for different payment types (Conversion, Crosschain, Crypto-to-fiat) with links to detailed documentation
• Introduced Currencies API endpoints section with practical integration information
• Removed extensive tables, tabs, and accordions in favor of focused card-based navigation
• Updated the description from general blockchain coverage to API-specific payment type coverage

How to test?

• Verify all internal links to payment type documentation pages work correctly
• Test the API endpoint links to ensure they point to the correct OpenAPI documentation
• Confirm the token list link provides the expected comprehensive token catalog
• Check that the crosschain and crypto-to-fiat payment links contain the detailed chain/currency matrices

Why make this change?

The original documentation was overly comprehensive and included AI-generated warnings that may have reduced user confidence. This revision creates a more focused, API-centric resource that directs users to specific payment type documentation while maintaining essential currency and chain information needed for integration decisions.

[aimensahnoun]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Remove AI-generated content warnings and update internal links #77
• docs(lifecycle): replace external image with local asset and remove AI-generated warning #76
• docs: remove AI-generated content warnings and simplify Request Scan page #75
• docs(resources): remove community page from navigation #74
• docs(supported-chains): add Tron network support and enhance currency documentation #73
• docs(supported-chains): streamline supported chains and currencies documentation #72 👈 (View in Graphite)
• docs(api-reference): add v2 endpoints overview and switch docs OpenAPI to v2-only spec Improve API Reference navigation by introducing a dedicated Endpoints Overview page in docs and wiring Mintlify OpenAPI rendering to a local v2-only spec. - add `api-re #71
• docs(authentication): simplify auth guide with API key vs Client ID methods and remove AI-generated content #70
• docs(fee-breakdowns): rewrite to focus on API response locations and reconciliation usage #69
• docs(protocol-fees): add protocol fees documentation and navigation #68
• docs(platform-fees): simplify configuration guide and remove AI-generated content warning #67
• docs(query-payments): rewrite with practical implementation focus and remove AI warning #66
• docs(query-requests): simplify and refactor query requests documentation for practical implementation #65
• docs(payment-detection): simplify content and remove AI warning #64
• docs(partial-payments): rewrite with step-by-step implementation guide and clarify API usage #63
• docs(standard-payments): remove AI warning, restructure content with step-by-step flow, and update API references #62
• docs(conversion-payments): rewrite with step-by-step implementation guide and remove AI-generated warning #61
• docs(payment-types): simplify overview and add payment type selection guidance #60
• docs(crypto-to-fiat): expand comprehensive guide with sandbox access, compliance flows, and implementation details #59
• docs(recurring-payments): rewrite with comprehensive workflow, security details, and practical implementation guide #58
• docs(batch-payments): add comprehensive implementation guide with examples, workflow diagrams, and demo videos #57
• docs(crosschain-payments): replace AI-generated content with comprehensive implementation guide #56
• docs(create-requests): rewrite with workflows, examples, and remove AI warning #55
• feat: add complete integration tutorial with Node.js backend and React frontend #54
• docs(getting-started): remove AI warning and refactor to focus on practical payment integration #53
• docs(api-portal): remove AI warning, add local screenshot, and update .gitignore #52
• docs: remove release notes section and streamline use cases to core features #51
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Summary

This PR streamlines resources/supported-chains-and-currencies.mdx from a 425-line overview with broad tables and accordions into a focused 122-line API reference that links out to payment-type-specific pages. The reduction in scope is intentional and appropriate — all referenced internal anchors and external API links are valid.

Key observations:

• All internal anchor links (#token-list-structure, #crosschain-payments-supported-chains-and-currencies, #crypto-to-fiat-supported-chains-and-currencies, #payment-types) were verified against target files and are valid
• External OpenAPI links for /v2/currencies endpoints are correctly formatted
• The ## Endpoints heading (line 96) is structurally misplaced at the same ## level as ## Currencies API Endpoints (line 72); it should be ### Endpoints to properly nest within that section
• Documentation-only change with no broken references

Confidence Score: 4/5

• Safe to merge — documentation-only change with one minor structural heading hierarchy issue worth addressing.
• This is a documentation-only PR with no functional code changes. All internal and external links have been verified and are correct. The score is 4 rather than 5 due to one structural issue: the ## Endpoints heading should be ### Endpoints to properly nest under the ## Currencies API Endpoints section. This is a quick fix that improves document outline consistency.
• resources/supported-chains-and-currencies.mdx — heading hierarchy issue on line 96

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Supported Chains and Currencies Page] --> B[ERC20 / Native / Conversion<br/>Supported Chains]
    A --> C[ERC20 and Native Payments<br/>Supported Currencies]
    A --> D[Conversion Payments<br/>Supported Currencies]
    A --> E[Crosschain Payments<br/>Supported Currencies]
    A --> F[Crypto-to-fiat Payments<br/>Supported Currencies]
    A --> G[Currencies API Endpoints]

    C --> C1[Token List Page<br/>/resources/token-list#token-list-structure]
    D --> D1[GET /v2/currencies/currencyId/conversion-routes]
    E --> E1[Crosschain Payments Page<br/>#crosschain-payments-supported-chains-and-currencies]
    F --> F1[Crypto-to-fiat Page<br/>#crypto-to-fiat-supported-chains-and-currencies]
    G --> G1[GET /v2/currencies]
    G --> G2[GET /v2/currencies/currencyId/conversion-routes]

Loading

_{Last reviewed commit: 599e467}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

The ## Endpoints heading (line 96) is at the same hierarchy level as ## Currencies API Endpoints (line 72), but it logically belongs as a subsection containing those endpoint cards. This should be demoted to ### to maintain proper document structure.

Suggested change

	## Endpoints
	### Endpoints

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}