feat(import): discover OpenAPI specs beyond llms.txt json links - #42
Merged
minhthanhdang merged 2 commits intoAug 24, 2026
Merged
Conversation
…-oas-discovery-for-the-docs-importer # Conflicts: # src/commands/import.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🧰 Changes
Today a spec is only found when llms.txt happens to link a
.jsonfile. This PR adds four more discovery paths, so most real docs sites get their API reference automatically:/openapi.json,/swagger.json,/v3/api-docs, …)openapifields from Mintlify docs.json / mint.json.yaml/.ymlspecs now ride through end to end, and HTML bodies are never staged as specs. Candidates are deduped, ranked by source confidence, and capped at 10 per source.🧬 QA & Testing