About this tool
Name a collection and an optional sub-collection, choose which methods you will offer, and the tool expands the real path and method pairs into a table. Seeing which methods the collection path and the item path each accept, and what every method does, in one view makes a missing combination obvious while drafting a routing table or a documentation outline. The identifier placeholder can follow the OpenAPI form or the router form.
This tool gives no score and no grade. Instead it separates what the URI specification sets, as of October 2026, from what is industry convention. Paths being case-sensitive and a trailing slash marking a different address are specification; writing collection names in the plural and using only lowercase and hyphens are convention. Departures from convention are counted and listed without any verdict on which choice is correct.
Choosing a versioning scheme, picking a status code per situation and choosing a pagination style are each handled by separate tools. This tool also leaves out authentication design, request and response body schemas and rate limit design.
Frequently asked questions
No specification requires it; it is a widespread convention. Plural names put the list and the single member naturally under one name and read more easily. Being consistent within the team matters more than which form you pick.
There is no fixed limit. That said, when a child is uniquely addressable without its parent identifier, exposing it as its own collection shortens paths and simplifies cache keys. Keep nesting only for relationships where the child has no meaning without the parent.
It does not score or grade, choose a versioning scheme, pick status codes or choose a pagination style. It expands path and method pairs and separates specification from convention.