Add example client snippets (curl, fetch, axios, x402)

[Miracle656]

Background

Lens is designed to be consumed by external developers — but the README does not show how to make a paid request with the x402 header. Without examples, developers do not know how to structure the payment or what response to expect.

What to build

A "Usage Examples" section in the README with curl, fetch, and a Node.js example showing the full x402 payment flow.

Key files

• README.md — add examples here

Suggested execution

git checkout -b docs/usage-examples

1. curl example showing the 402 response (no payment header)
2. curl example with X-PAYMENT header showing 200 + price JSON
3. Node.js example using @x402/client for auto-payment
4. GET /status unauthenticated health check
5. GraphQL price query example

Example commit message:
docs: add curl, fetch, and Node.js usage examples with x402 payment flow

Acceptance criteria

• The 402 → payment → 200 flow illustrated
• @x402/client Node.js example shown
• All code examples are syntactically valid

---

Drips Wave · Complexity: Trivial · 100 points
Comment below to request assignment. PR must include Closes #[this issue].

[snakefood3232]

The README lacks examples for the x402 payment flow, making it unclear how to structure paid requests. I'd handle this by adding the curl, fetch, and Node.js snippets as outlined, clearly illustrating the 402 → payment → 200 sequence. I can have a PR up within a few hours. I regularly write production TypeScript/Next.js docs and integration examples.

[laxjovial]

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

Hi

Please assign me this task. I’ll add clear usage examples to the README, including curl, fetch, and Node.js flows demonstrating the full 402 → payment → 200 cycle, along with a GraphQL query and health check example.

ETA: 1–2 hours

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

[drips-wave]

Congratulations, @laxjovial! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @laxjovial: 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 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @laxjovial as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The PR was created more than 24 hours ago and comprehensively addresses all the requirements specified in the issue, including multiple code examples for different environments. There are no maintainer objections, and the contribution significantly improves the project's documentation.

😎 @laxjovial: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.