Add reviewer-safe JSON export for usage and spend analytics

[emrekayat]

Why this matters

SCF reviewers and investors often ask for proof of usage and spend. A safe JSON export makes it easy to share analytics without leaking raw payment headers, wallet secrets, or provider credentials.

Scope

Add a read-only JSON export path for sanitized usage and spend analytics:

• total query count;
• spend by mode/provider;
• demo-vs-real counts if tracked;
• payment evidence presence count;
• generated timestamp;
• no raw payment header blobs or secrets.

Suggested files:

• apps/api/src/routes/public.ts
• apps/api/src/lib/persistence.ts
• apps/web/src/App.tsx if adding a small download/copy button.

Acceptance criteria

• Export endpoint returns sanitized JSON only.
• Empty analytics returns a valid export with zero totals.
• Tests assert that secret-like fields and raw payment headers are excluded.
• Optional dashboard button copies/downloads the export without changing query flow.
• Existing API tests pass.

Wave complexity

High - gives reviewer/investor diligence a clean evidence artifact.

[TheWeirdDee]

@TheWeirdDee has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to work on this issue because transparent, reviewer-friendly analytics are valuable for demonstrating product usage while maintaining strong security and privacy practices. A sanitized export provides useful evidence for stakeholders without exposing sensitive payment or credential data.

I have experience building TypeScript APIs, analytics/reporting features, data sanitization, and secure export workflows. I'm comfortable implementing read-only JSON endpoints, designing safe serialization layers, adding validation tests for sensitive data exclusion, and optionally integrating lightweight frontend actions for downloading or copying exports. I can ensure the export remains useful for reporting while preventing leakage of payment headers, secrets, or provider credentials.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheWeirdDee to this issue.

[VeronicDev]

@VeronicDev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Pls assign thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @VeronicDev to this issue.

[CollinsKRO]

@CollinsKRO has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Pls assign me this. Thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CollinsKRO to this issue.

[Bojest001]

@Bojest001 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I will to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bojest001 to this issue.

[drips-wave]

Congratulations, @CollinsKRO! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @CollinsKRO: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊