Implement real `GET /api/apis` listing backed by the Drizzle `apis` table instead of the empty placeholder

[greatest0fallt1me]

Description

The backend route src/routes/apis.ts currently returns a hard-coded { apis: [] } placeholder regardless of state. This backend task replaces it with a real listing endpoint that reads from the Drizzle apis table (src/db/schema.ts) and joins endpoint pricing so the marketplace can render registered APIs. It matters because the API marketplace cannot surface any catalog data until this endpoint is real.

Requirements and Context

• Replace the placeholder handler in src/routes/apis.ts with a query against the apis table defined in src/db/schema.ts.
• Only return APIs with status = 'active' by default; allow ?status= filtering against apiStatusEnum.
• Use parsePagination/paginatedResponse from src/lib/pagination.ts for limit/offset.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b feature/apis-listing-endpoint

2. Implement changes
   • src/routes/apis.ts — wire the route to a repository read
   • src/repositories/apiRepository.ts — add a paginated list query
   • Map DB rows to the public ApisResponse shape in src/types/index.ts
3. Test and commit
   • npm test -- src/data/apiRegistry.test.ts src/repositories/apiRepository.test.ts
   • Cover edge cases
   • Include test output and notes in the PR

Example commit message

feat: back GET /api/apis with the Drizzle apis table

Acceptance Criteria

• GET /api/apis returns active APIs from the database with pagination metadata
• ?status= filtering validates against apiStatusEnum and rejects unknown values with 400
• Endpoint pricing is included per API where available
• Unit and route tests pass

Guidelines

• Minimum 90% test coverage with Jest; validate inputs and handle errors via src/errors
• Clear documentation and inline comments
• Timeframe: 96 hours

[isaacCodes1]

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

Pls, assign this issue to me.

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

[drips-wave]

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

🧑‍💻 @isaacCodes1: 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 @isaacCodes1 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @isaacCodes1: You earned 200 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.