DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to map every API endpoint from an OpenAPI document with Vibex

Generate an endpoints diagram grouped by resource, with methods, auth, and status codes.

Who it is forA backend or frontend developer who needs a quick reference to the REST routes or GraphQL operations in a service.

The problemAPI docs are scattered or out of date, and reading a long OpenAPI file to find routes is slow.

The outcomeAn endpoints spec and HTML viewer grouped by resource with method badges, auth, params, and response codes.

What you need first

  • Node.js and npx, for the npx commands in the README
  • A Prisma schema, OpenAPI document, or GraphQL SDL file in the project, or source code the tool can read
  • Claude Code or Codex if you want to use vibeX as an agent skill

Steps

  1. vibex import openapi openapi.yaml docs/api.endpoints.json (inferred, check the README)
  2. vibex render docs/api.endpoints.json --open (inferred, check the README)

Prompt for your agent

In the repo <repo path>, import the OpenAPI file at <openapi file> into docs/api.endpoints.json with vibeX and render docs/api.endpoints.html. Report the number of endpoints per resource. Verify that the count matches the number of paths and methods in the OpenAPI document.

Caveat. The README notes YAML OpenAPI needs npm install inside the skill folder when vibeX is installed by skills add or the plugin.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page