Generate OpenAPI spec for Lens REST endpoints

[Miracle656]

Background

Lens exposes GET /price/:assetA/:assetB, GET /status, GET /pools, and a GraphQL endpoint. Developers integrating Lens need to know the exact request format, the x402 payment header format, and the response schema. An OpenAPI spec makes this discoverable and enables auto-generated clients.

What to build

Author or generate an OpenAPI 3.0 spec covering all Lens REST endpoints, including the x402 payment header requirement.

Key files

• src/routes/ — all route handlers
• openapi.yaml — create at repo root
• README.md — link to spec

Suggested execution

git checkout -b docs/openapi-spec

1. Document GET /price/{assetA}/{assetB} — include x402 header in security scheme, describe all response fields
2. Document GET /status, GET /pools
3. Add a custom x402 security scheme describing the X-PAYMENT header format
4. Validate with npx @redocly/cli lint openapi.yaml

Example commit message:
docs: add OpenAPI 3.0 spec for all Lens REST endpoints including x402 auth

Acceptance criteria

• All REST endpoints covered
• x402 payment header documented as a security requirement
• Response schemas include all fields with types
• Spec passes Redocly lint

---

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

[snakefood3232]

You need an OpenAPI spec documenting the x402 payment header and all REST endpoints. I'd handle this by analyzing the route handlers to extract exact schemas and defining a custom security scheme for X-PAYMENT. Can have a PR up in a few hours—I've built similar OpenAPI integrations for TypeScript/Next.js projects.

[snakefood3232]

You need an OpenAPI spec documenting all REST endpoints including the x402 payment header. I'd handle this by analyzing the route handlers in src/routes/ to generate accurate schemas and define the custom security scheme. I can have a validated PR up within a few hours—I've built similar OpenAPI specs for TypeScript/Next.js projects.

[Viv-90]

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

Good day maintainer, I’ve worked expressly with open ai and would love to work on this in order to generate OpenAI spec

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

[drips-wave]

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

🧑‍💻 @Viv-90: 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 completed by @Viv-90 as part of the Stellar Wave Program's 4th Wave 🥳

😎 @Viv-90: You earned 150 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. You can also Leave a review to share your experience working on this issue.

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