Source code in. Routes out.
Scan supported route patterns in a repository to discover endpoints and build an OpenAPI document. Review the result before publishing.
API CATALOG
Bring routes, schemas, and quality signals into one searchable catalog. Start with your source code or the specification you already have.
No matching endpoints. Try “payments”.
Returns a payment by its unique identifier.
01 / DISCOVER
A useful catalog begins with the API you actually ship.
Scan supported route patterns in a repository to discover endpoints and build an OpenAPI document. Review the result before publishing.
Import an OpenAPI document by pasting it, uploading a file, or providing a URL. Keep the same workflow for documented and newly discovered APIs.
Group related endpoints into collections and use their methods, paths, and schemas to find the right operation for the job.
02 / UNDERSTAND
Inspect design, developer experience, AI readiness, security, and performance checks. Follow the findings to the fields that need attention.
Catalog checks inspect available metadata. A good score is not a security audit or a load test.
No. You can scan supported source patterns or import an existing specification. Discovery coverage depends on your framework and how routes are defined; inspect the catalog for gaps.
Use the catalog to define a contract, export an API artifact, or configure an MCP server. The catalog gives each of those workflows a common starting point.