@vincentbiret Ha! @kevinswiber had literally just shared that with me. I am investigating and playing with. Y'all are building some cool things over there.

@kin
Ah perfect then! @kevinswiber Thanks for sharing it!

Another thing we're experimenting with is https://app.kiota.dev/
This is leveraging the apisjson format and a GitHub topic to index the API descriptions. Search , explore and generate clients for APIs all from the browser. :)

@vincentbiret @kevinswiber Interesting. We should chat and share more. We have a project harvesting all swagger + openapi from Github. Indexing. Running spectral rules against. Then going to widen it against search using Bing. Would love to index your work.

@kin @kevinswiber we'd love to collaborate! Cc @darrel_miller the mastermind, I just write the code

@kin @vincentbiret @kevinswiber Any chance you can project an apis.json of that index to some GitHub repo then Kiota can search over it?

@darrel_miller @vincentbiret I think @kin and @plgah are using a different dataset than I was, a fresh harvest. In either case, it’s fairly large, several thousand at this point. How would you want to consume that? Ideally, it would be de-duped, but even determining parameters for what makes a duplicate is an interesting exercise.

@kevinswiber We already search apis.guru which has thousands of entries. We provide a list of matches and then generate a key based on registry+api baseUrl+version and allow people to query the details of that. #kiota

@kevinswiber You can see searching for a generic term like "graph" brings results from different registries. #kiota

@kevinswiber Searching by a specific key will return more details on the API #kiota

@darrel_miller When you ingested APIs.guru data, did you crawl the API or did you use the GitHub repo? I think we’re collecting different metadata than APIs.guru, but it might be possible to use their API conventions as a de facto registry API we can mimic.

@kevinswiber I believe @vincentbiret called APIGurus API that returns everything as one big JSON file that we cache locally. We're not fussy about what metadata you have. We would like to standardize on the APIs.json format. All we need really is the link to the OpenAPI. #kiota

@darrel_miller @kevinswiber @vincentbiret "We would like to standardize on the APIs.json format. " <3 <3 ;-) ;-)

@kin @kevinswiber @vincentbiret That's what we are telling people to use if they want their API to show up in the #kiota search so people can generate API client code. https://microsoft.github.io/kiota/add-api.html You can even use APIs.yaml 🙂

@darrel_miller @kevinswiber @vincentbiret Thank you. I'll publish an API.json API operation that you can search on our OpenAPI / Swagger index. I don't have any rating system yet -- that will come. They are validated, but not ded-uped or anything.

@kin @kevinswiber @vincentbiret If you implement a rating system that can be exposed by apis.json, we'll implement filter on our #Kiota search

@darrel_miller @kevinswiber @vincentbiret Yes. The rating system has been in roadmap for a while -- just need to do it.

@kin @kevinswiber @vincentbiret We will be doing additional validation of the OpenAPI descriptions to detect issues that #Kiota codegen can't yet handle.

@darrel_miller @kevinswiber @vincentbiret Would love to learn from your learnings. We are going to publish a blog series on common mistakes we see.

@kin @darrel_miller @kevinswiber the validation is already implemented, not released yet. Navigating to the issue you can see which things kiota validates for pre generation https://github.com/microsoft/kiota/pull/2029

@darrel_miller @vincentbiret @kevinswiber Yes sir. I can. Will add to the queue. ;-)

@kin LOL. I'm pretty sure I have a good idea what that queue looks like.

@darrel_miller @kin Ha! “I’ll add it to the stack,” would be more promising.

@kevinswiber @darrel_miller This should be pretty light lift to add -- we'll see. ;-)