Show HN: APIRank.dev – we crawled and ranked 5651 public APIs from the Internet

Re:Show HN: APIRank.dev – we crawled and ranked 5651 public ... by ozten on Thursday March 09, 2023 @01:25PM (#35084743)

A terribly designed API with a complete and orderly OpenAPI 3.0.0 spec will get 5/5.

A well designed API with no OpenAPI support or 3.1.x spec support will get a poor design score.

I think user generated content might be the way to go for Design. Let people score and review the design quality.

[ Parent | on HN ]

Re:Show HN: APIRank.dev – we crawled and ranked 5651 public ... by iCarossio on Thursday March 09, 2023 @03:28PM (#35086229)

Hey coauthor here.

Thanks for your feedback! APIRank is new, and we are here to improve it and make it useful to the community.

APIRank only considers APIs with an OpenAPI or Swagger specification. It supports any version of Swagger v2+ or OpenAPI v3+.

However, I agree in practice for people, the "design criterium" is not only the compliance to the spec ;)

Antoine

[ Parent | on HN ]

Re:Show HN: APIRank.dev – we crawled and ranked 5651 public ... by lazyasciiart on Thursday March 09, 2023 @03:33PM (#35086284)

A well designed API with no OpenApi spec support will not show up on this list.

[ Parent | on HN ]

Re:Show HN: APIRank.dev – we crawled and ranked 5651 public ... by glimow on Thursday March 09, 2023 @03:49PM (#35086485)

I agree with your point, yet we thought the data we gathered could be interesting, for instance we observe that ~60% of routes have human readable comments, but less than 10% have actual examples.

[ Parent | on HN ]

Re:Show HN: APIRank.dev – we crawled and ranked 5651 public ... by drunkenmagician on Thursday March 09, 2023 @07:25PM (#35088875)

I would suggest renaming the Design category to Documentation. Design is subjective, so user generated content might be an option, but ultimately docs and examples as (non subjective) a measure are probably more useful to most developers.

[ Parent | on HN ]