docs(fee-breakdowns): rewrite to focus on API response locations and reconciliation usage

[aimensahnoun]

TL;DR

Rewrote the fee breakdowns documentation to focus on practical API usage patterns rather than conceptual explanations.

What changed?

• Removed AI-generated content warning and conceptual diagrams
• Restructured content around specific API endpoints where fee data appears (routes, payments, request status)
• Added concrete JSON examples showing actual API response shapes
• Replaced theoretical fee calculation flows with practical reconciliation steps
• Updated related pages section to link to platform and protocol fee documentation

How to test?

• Review the three main endpoints mentioned (GET /v2/request/{requestId}/routes, GET /v2/payments, GET /v2/request/{requestId}) to verify fee data appears as documented
• Test the reconciliation workflow described in the "How to Use in Reconciliation" section
• Validate that the JSON examples match actual API response formats

Why make this change?

The previous version was AI-generated conceptual content that didn't provide actionable guidance for developers. This rewrite focuses on where developers can find fee information in API responses and how to process it for accounting and reconciliation purposes.

[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

• 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 👈 (View in Graphite)
• 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 transforms the fee-breakdowns documentation from AI-generated conceptual content into a practical API reference guide. The rewrite focuses on three key improvements:

• Endpoint-specific documentation: Clearly identifies where fee data appears (GET /v2/request/{requestId}/routes, GET /v2/payments, GET /v2/request/{requestId}) with OpenAPI links
• Concrete examples: Replaces theoretical diagrams with actual JSON response shapes showing feeBreakdown[] and fees[] structures
• Reconciliation guidance: Adds practical Steps component with idempotent processing patterns for accounting workflows

The page now follows Mintlify best practices with proper component usage (Steps, CardGroup) and maintains consistency with related platform-fees and protocol-fees documentation. The cross-references are properly linked and the content is structured for developer consumption.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk - it's a documentation rewrite that improves clarity and accuracy
• Score reflects high confidence in a well-structured documentation improvement. Minor uncertainty around two specific details: (1) some fee types (crypto-to-fiat, offramp) and (2) route fee stages (sending, receiving, proxying, refunding, overall) are not documented elsewhere in the codebase, so their accuracy cannot be fully verified from available sources. The overall structure, Mintlify component usage, and cross-references are correct.
• No files require special attention - this is a single-file documentation update

Important Files Changed

Filename	Overview
api-features/fee-breakdowns.mdx	Rewrote from conceptual AI-generated content to practical API reference focused on endpoint locations and reconciliation workflows

_{Last reviewed commit: 6e538d9}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}